[Bug 401056] Re: package sysklogd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
steve.langasek at canonical.com
Mon Sep 21 19:18:15 BST 2009
Yes, neither of these packages should be deleting the system user on
purge. It's a bad idea in the general case, and is guaranteed to break
things when more than one package is using the user. Even if rsyslogd
were stopped at the time, that would just mean that the sysklogd purge
succeeds at the expense of rsyslogd being able to start again later!
(Note that rsyslogd is probably installed *before* sysklogd is purged.)
Also a sysklogd SRU to jaunty is insufficient because the same problem
will affect users upgrading from hardy to karmic+1; as well as missing
any users who happen to have not upgraded sysklogd before removing it.
So I think the best approach is as follows:
- fix sysklogd postrm to not call deluser.
- fix rsyslog postrm to not call deluser.
- add a one-time hack to rsyslog postinst to call sed -e'/deluser/d' /var/lib/dpkg/info/rsyslog.postrm
Michael, is this something you'd like to work on? If not, I can cook
this up quickly.
** Also affects: rsyslog (Ubuntu Jaunty)
** Also affects: sysklogd (Ubuntu Jaunty)
package sysklogd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.
More information about the Ubuntu-universe-sponsors