Your message dated Sat, 14 Jul 2012 16:48:35 +0000
with message-id <[email protected]>
and subject line Bug#678099: fixed in sogo 1.3.16-1
has caused the Debian Bug report #678099,
regarding sogo: 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.)


-- 
678099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sogo
Version: 1.3.15a-2
Severity: important
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 http://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

Filing this as important because a.) it's a clear policy violation (to
not clean up at purge) b.) having a piuparts clean archive is a release
goal since lenny and c.) this package being piuparts buggy blocks
packages depending on it from being tested by piuparts (and thus
possibly the detection of more severe problems).

>From the attached log (scroll to the bottom...):

  Removing sogo ...
  Purging configuration files for sogo ...
  /var/lib/dpkg/info/sogo.postrm: 19: /var/lib/dpkg/info/sogo.postrm: deluser: 
not found
  dpkg: error processing sogo (--purge):
   subprocess installed post-removal script returned error exit status 127
  Errors were encountered while processing:
   sogo


cheers,

Andreas

Attachment: sogo_1.3.15a-2.log.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message ---
Source: sogo
Source-Version: 1.3.16-1

We believe that the bug you reported is fixed in the latest version of
sogo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeroen Dekkers <[email protected]> (supplier of updated sogo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 30 Jun 2012 02:55:17 +0200
Source: sogo
Binary: sogo sogo-common sogo-dbg
Architecture: source amd64 all
Version: 1.3.16-1
Distribution: unstable
Urgency: low
Maintainer: Jeroen Dekkers <[email protected]>
Changed-By: Jeroen Dekkers <[email protected]>
Description: 
 sogo       - Scalable groupware server
 sogo-common - Scalable groupware server - common files
 sogo-dbg   - Scalable groupware server - debugging symbols
Closes: 677119 678047 678099
Changes: 
 sogo (1.3.16-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #677119)
     - 0004-Add-support-for-GnuTLS.patch: Updated to new hashes in 1.3.16.
     - 0007-GNUstep-1.24-fix.patch: Removed, was backported from upstream.
   * Do not assume deluser is available in postrm. (Closes: #678099)
   * Suggest postgresql or mysql-server. (Closes: #678047)
   * Build with hardening
     - 0007-Compile-daemon-as-PIE.patch: Compile the daemon as a PIE.
Checksums-Sha1: 
 77bc50f009bea7b732eef74de2aa861b09e1572c 1348 sogo_1.3.16-1.dsc
 912ad2447f33b767e75527ae492711e46126d106 4930514 sogo_1.3.16.orig.tar.gz
 893d75f71596701137b1f0ed1daf716492b5b1bd 19784 sogo_1.3.16-1.debian.tar.gz
 df7f15f43c6fabb1683dc79f481f56c2c8f7e750 1559398 sogo_1.3.16-1_amd64.deb
 50f804ab64650cfb094210e9566e4b7df194eff2 1547128 sogo-common_1.3.16-1_all.deb
 fc3e64d0b50de78f0a9ed30a34ed6cfafaab10c5 2622298 sogo-dbg_1.3.16-1_amd64.deb
Checksums-Sha256: 
 bd9e8d105ce73e7a93ffe2c271d821f6856463c2b2139e22cdb1f2851b535d86 1348 
sogo_1.3.16-1.dsc
 115be27b7f7e9e386185190950cd9b048744b90dcbb225fbde1efedd58bc6775 4930514 
sogo_1.3.16.orig.tar.gz
 55faa4d97d96c63140e88ff78c2f657a8b7f7a667ef1e698f54f783db2a28cc9 19784 
sogo_1.3.16-1.debian.tar.gz
 865abd03d0982ba92ea4611313c9b0111f62cfaeaf3118d50a842c5a140341bc 1559398 
sogo_1.3.16-1_amd64.deb
 99e5ff238efcdcc8ba54afedd51a5d6a61a1a7930c5158cb1831450eca6cc532 1547128 
sogo-common_1.3.16-1_all.deb
 2f3b9968f3e5f54c1838b5ffa0c23dacbf6b25122ac32c1173e7c51ecac2a95c 2622298 
sogo-dbg_1.3.16-1_amd64.deb
Files: 
 d2425d553fd6eb9ede7bfdb786036316 1348 mail optional sogo_1.3.16-1.dsc
 7efd660274d2b8725115cbe2fe1667e9 4930514 mail optional sogo_1.3.16.orig.tar.gz
 6a5d0820d74b7fc00ca62827282ccd29 19784 mail optional 
sogo_1.3.16-1.debian.tar.gz
 4fc7023cf618077c5dc8853bf92f3118 1559398 mail optional sogo_1.3.16-1_amd64.deb
 85fe28245de38d267933af3f4a781684 1547128 mail optional 
sogo-common_1.3.16-1_all.deb
 b07d3fe8dff3816fe5c73ffa7cc8f7c3 2622298 debug extra 
sogo-dbg_1.3.16-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlABoJwACgkQPa9Uoh7vUnb++QCghCHdrUbeOd/epzC5B93ARK8e
MLEAmgNXdhBh3Pj+mfNeoex4gap5z+be
=yhD0
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to