Package: jabberd2
Version: 2.7.0-7
Severity: minor
Hi,
I am the main maintainer of adduser and am always interested in usage patterns of my software. jabberd2 is one of the _very_ few (<5) packages
in Debian that use adduser in their preinst.
Since this might interfere with adduser's development (preinst might and probably will run with an un-updated adduser during upgrades), I would
like to know why it was decided in jabberd2 to create the user in
preinst.
If there is no real reason, I'd love the usage of adduser being moved
too postinst like hundreds of other packages do it.
In addition, in trixie, the scaffolding you're using around your adduser calls is no longer necessary.
A single call of
adduser --system --group --home=/var/lib/jabberd2 --no-create-home jabber will already do it.
A single call of
adduser --system --group --home=/var/lib/jabberd2 --no-create-home jabber
will already do it.
Thanks -- I suspect the actual reason may be lost in time. What is the
exact patch you are thinking of, is it the one below? I'm happy to
apply it and see of Salsa is happy and then upload and see if we get any >reports.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 56:43:48 |
Calls: | 9,566 |
Files: | 13,661 |
Messages: | 6,142,956 |