Re: questions related to one piuparts (tag) case
On 18/04/2023 20.30, Patrice Duroux wrote:
Hi,
After considering https://piuparts.debian.org/sid/fail/mrtg_2.17.10-4+b1.log
and reporting #1034530, I would like to be sure that another case
like: https://piuparts.debian.org/sid/pass/pipewire_0.3.65-3.log is
more tricky due to that pipewire may be purged after both with adduser
have been already removed. Isn't it?
I'm pasting here the piuparts bug template for this specific error, that
should have sufficient information for fixing this issue:
Subject: fails to purge - command (deluser|adduser) in postrm not found
Package:
Version:
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.
The fix should be easy: your package is using adduser or deluser from
the adduser package, which is only priority important. Using useradd or
userdel from the passwd package (priority required) should fix this
problem.
There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833
Consensus seems to be not to remove system users (to avoid reusing UIDs
which could grant access to the wrong files) but to "lock" them (where
"locking"/"unlocking" is not yet precisely defined). Until that has
been decided it should be sufficient to have the postrm script ignore
any errors from deluser:
deluser ... || true
From the attached log (scroll to the bottom...):
cheers,
Reply to: