Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#22407 - [exim] 4.73-1 build is totally busted
Attached to Project:
Community Packages
Opened by Dan McGee (toofishes) - Wednesday, 12 January 2011, 05:03 GMT
Last edited by Angel Velasquez (angvp) - Wednesday, 12 January 2011, 14:23 GMT
Opened by Dan McGee (toofishes) - Wednesday, 12 January 2011, 05:03 GMT
Last edited by Angel Velasquez (angvp) - Wednesday, 12 January 2011, 14:23 GMT
|
Detailsdmcgee@toofishes ~
$ exim 2011-01-11 22:58:50 cannot run initgroups(): no passwd entry for uid=70 However you built this, you did NOT ensure the exim group was 79 as it needs to be to stay compatible, as is noted in the PKGBUILD. Completely unusable now for anyone that had this installed before. To top it off, I didn't even know the service didn't start because the init script always returns stat_done and not stat_fail, it appears. I'm not sure if exim is just braindead in the return codes it spits out or what, this is unfortunate. Fix: rebuild it correctly with the right UID/GID on your system Workaround: downgrade |
This task depends upon
Closed by Angel Velasquez (angvp)
Wednesday, 12 January 2011, 14:23 GMT
Reason for closing: Fixed
Additional comments about closing: I had a typo writing 79, sorry for the inconveniences guys, shame on me.
Wednesday, 12 January 2011, 14:23 GMT
Reason for closing: Fixed
Additional comments about closing: I had a typo writing 79, sorry for the inconveniences guys, shame on me.
The way that I used to built it was:
a) make a clean chroot
b) added it manually the group and the user there (then I did my second typo on x86_64 chroot so I busted the x86_64 package)
Actually is working for me, but I have to find a way to don't hack this in that way, the problem that I'm having is with sudo ask me for a password when I create the groups temporarly.
Please test 4.73-2 release as I said is work for me, in case this still fail, I will have to downgrade this until make other way to build (not creating a particular chroot *just* for exim)