Your message dated Mon, 03 Jul 2023 23:43:26 +0000
with message-id <[email protected]>
and subject line Bug#1040240: Removed package(s) from unstable
has caused the Debian Bug report #1035290,
regarding kismet: fails to purge - command (deluser|adduser) in postrm not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1035290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035290
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kismet
Version: 2016.07.R1-1
Severity: serious
User: [email protected]
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...):
0m15.6s DEBUG: Starting command: ['chroot',
'/srv/piuparts.debian.org/tmp/tmp6_lhwlij', 'dpkg', '--purge', 'kismet']
0m15.6s DUMP:
(Reading database ... 8069 files and directories currently installed.)
Purging configuration files for kismet (2016.07.R1-1+b1) ...
Cannot remove group kismet because delgroup command is not found
dpkg: error processing package kismet (--purge):
installed kismet package post-removal script subprocess returned error exit
status 128
Errors were encountered while processing:
kismet
0m15.6s ERROR: Command failed (status=1): ['chroot',
'/srv/piuparts.debian.org/tmp/tmp6_lhwlij', 'dpkg', '--purge', 'kismet']
cheers,
Andreas
kismet_2016.07.R1-1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 2016.07.R1-1+rm
Dear submitter,
as the package kismet has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1040240
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
