with spamassassin older then 3.4.5 its valid homedir in /home/spamd, but in spamassassin 3.4.5 its changed to /var/lib/spamd simple fix is usermod --home /var/lib/spamd spamd but acct-user/spamd is imho correct for new installs where spamd user is not existing on yet hope i have giving needed info to solve it
Not a regression, right?
@sam: no, I can't figure out anyway 3.4.5 itself could cause this. @benny: Two requests so I can see if I can reproduce this: 1.) Can you attach logs of your install (or a re-install) and emerge --info for reference? 2.) Was spamd running at the time of the install? Thanks.
The only way I've been able to reproduce this is by having spamd running during the upgrade. But the ebuild outputs a warning in that case: if [[ ! ~spamd -ef "${ROOT}/var/lib/spamd" ]] ; then ewarn "The spamd user's home folder has been moved to a new location." elog elog "The acct-user/spamd package should have relocated it for you," elog "but may have failed because your spamd daemon was running." elog elog "To fix this:" elog " - Stop your spamd daemon" elog " - emerge -1 acct-user/spamd" elog " - Restart your spamd daemon" elog " - Remove the old home folder if you want" elog " rm -rf \"${ROOT}/home/spamd\"" fi
confirmed that usermod --home /var/lib/spamd spamd fails when spamd is started, makes sense, is it the same acct-user/spamd does not handle well ?
Yes, acct-user/spamd is is the ebuild that attempts the home folder change. (The spamassassin ebuild just tries to inform users (A) that we "recently" switched which ebuild was responsible for the home folder, (B) the implications of that, and (C) tries to do some simple checks and warnings if it doesn't seem like it worked or if the old folder is still around.
I think, we can close here. No other reports seen? Feel free to reopen, if you disagree.
