On Wed, 14 Jan 2009 09:25:53 -0500 Marvin Renich <mrvn@renich.org> wrote: > * Harald Braumann <harry@unheit.net> [090113 16:49]: > > Well, jabber-common does remove the user jabber on purge, jabberd2, > > though, doesn't. And it seems that opinions diverge on this matter. > > See e.g. > > http://lists.debian.org/debian-mentors/2004/10/msg00338.html. > > I've filed a bug against jabber-common. Though the thread started > without a consensus, it ended with a clear consensus that the user > should not be removed. Thanks. > > I think I take the easy way out. I'll use the user jabber (create > > it, if it doesn't exist) and don't delete it. I'll also add a > > conflict to jabber-common. If that's a problem for someone, a more > > sophisticated solution can still be implemented. > > Why do you need to conflict with jabber-common? Both can use the same > user, unless there is a security issue and you don't want executables > from jabber-common to be able to read your config files, in which case > you should use a different user anyway. Was there another reason > independent of the user issue? jabber-muc needs to conflict with jabber-common, until there is a version that does not remove the user on purge. Otherwise, when both are installed and jabber-common is purged, jabber-muc stops working because the user jabber is remove. Cheers, harry
Attachment:
signature.asc
Description: PGP signature