Package: systraq Version: 0.0.20050213-4 Severity: wishlist Tags: patch Hi,
[You might want to merge this bug with #297531, after reopening it.]
[You also might to send your reply to debian-devel, it might belong
there. Please note: I am not subscribed to debian-devel; I'd like to
get Cc's.]
After purging the systraq package, the systraq user account is not
removed. Under the current setup, that's a sane thing to do: this
useracount might be created as a local user by the local admin, _before_
the systraq package was installed; and thus not "belong" to the systraq
package. Of course, the drawback is the systraq package has no way to
complete clear its traces after being purged.
There is a solution.
What is needed is a way to distinguish useraccounts (and groups) created
by packages from those created by the local admin. OpenBSD does this by
prefixing its useraccountnames with an underscore: _fingerd _syslogd,
group _postfix are typically found on such systems. However, I am aware
of one Debian package doing such a trick: exim adds Debian-exim: another
nice way to make clear the useraccount is not locally added. Of course,
Debian admins need to be aware never to create a user named Debian-*.
My suggestion is: in postinst, change
SYSTRAQUSER=systraq
in
SYSTRAQUSER=Debian-systraq
and in postrm, change
rm -rf /var/lib/systraq
in
if getent passwd Debian-systraq > /dev/null 2>&1; then
deluser --remove-home --quiet Debian-systraq > /dev/null
fi
.
It'd be cool if the Debian-foo convention could be codified in the
Debian policy, and if the adduser tool could be changed to refuse
(unless given a --i-am-package-and-therefore-i-know-what-i-am-doing
flag) to create users named Debian-foo.
The lire as well as the albatros package is another one suffering from
this, uh, design bug. There are likely a lot more.
Thanks, Bye,
Joost
signature.asc
Description: Digital signature
