Your message dated Mon, 08 Mar 2021 17:48:38 +0000
with message-id <[email protected]>
and subject line Bug#983892: fixed in petsc 3.14.4+dfsg1-2
has caused the Debian Bug report #983892,
regarding libpetsc64-complex3.14-dev: leaves alternatives after purge:
/etc/alternatives/*petsc64*
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.)
--
983892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983892
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpetsc64-complex3.14-dev
Version: 3.14.4+dfsg1-1
Severity: important
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-removal-and-or-configuration-purging
The leftover files are actually alternatives that were installed by the
package but have not been properly removed.
While there is ongoing discussion how to remove alternatives correctly
(see https://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).
Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove <name> <path>'.
Filing this as important as having a piuparts clean archive is a release
goal since lenny.
>From the attached log (scroll to the bottom...):
1m18.7s INFO: Warning: Package purging left files on system:
/etc/alternatives/PETSc64.pc ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex/lib/pkgconfig/PETSc.pc
not owned
/etc/alternatives/libpetsc64.so ->
/usr/lib/x86_64-linux-gnu/libpetsc64_complex.so.3.14.4 not owned
/etc/alternatives/petsc64 ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex not owned
/etc/alternatives/petsc64-3.14 ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex not owned
/etc/alternatives/petsc64-octave ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex/share/petsc/matlab
not owned
/etc/alternatives/petsc64.pc ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex/lib/pkgconfig/petsc.pc
not owned
/etc/alternatives/petsc64include ->
/usr/lib/petscdir/petsc64-3.14/x86_64-linux-gnu-complex/include not owned
/usr/include/petsc64 -> /etc/alternatives/petsc64include not owned
/usr/lib/petsc64 -> /etc/alternatives/petsc64 not owned
/usr/lib/petscdir/ owned by: libpetsc64-complex3.14-dev:amd64
/usr/lib/petscdir/64-3.14 -> /etc/alternatives/petsc64-3.14 not owned
/usr/share/octave/ owned by: libpetsc64-complex3.14-dev:amd64
/usr/share/octave/site/ owned by: libpetsc64-complex3.14-dev:amd64
/usr/share/octave/site/m/ owned by: libpetsc64-complex3.14-dev:amd64
/usr/share/octave/site/m/petsc64 -> /etc/alternatives/petsc64-octave not
owned
cheers,
Andreas
libpetsc64-complex3.14-dev_3.14.4+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: petsc
Source-Version: 3.14.4+dfsg1-2
Done: Drew Parsons <[email protected]>
We believe that the bug you reported is fixed in the latest version of
petsc, 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.
Drew Parsons <[email protected]> (supplier of updated petsc 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: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 18:27:40 +0100
Source: petsc
Architecture: source
Version: 3.14.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Drew Parsons <[email protected]>
Closes: 983892
Changes:
petsc (3.14.4+dfsg1-2) unstable; urgency=medium
.
* fix PETSC64_NAME in libpetsc64-complex3.14-dev.prerm to enable a
clean uninstall of libpetsc64-complex3.14-dev. Closes: #983892.
Checksums-Sha1:
493164d7adc81747dcb7be90cc2319aa91ac1f7a 4237 petsc_3.14.4+dfsg1-2.dsc
9d1def39b5ff1ce44dce8bbebbd99863669708d9 110076
petsc_3.14.4+dfsg1-2.debian.tar.xz
275fcbda061532084d3b3ef448a92c42cf78fab5 12452
petsc_3.14.4+dfsg1-2_source.buildinfo
Checksums-Sha256:
a05a0b2b3e4bc4152452f6ef4eddc3ca71edc83f0fd6906703d022c66a916ae5 4237
petsc_3.14.4+dfsg1-2.dsc
d3e3ed7e568ec4d3091b7f72acb213930eb651c0fe5b5dfa7defb318a0cfa0b3 110076
petsc_3.14.4+dfsg1-2.debian.tar.xz
295a5bb3f989132cdeff13eb80df9c74731e831e33f609a3faaa89b3e77880c7 12452
petsc_3.14.4+dfsg1-2_source.buildinfo
Files:
a271f9af1567351c8eaa68c4c9eb94e9 4237 devel optional petsc_3.14.4+dfsg1-2.dsc
7ef29290b0692251bf18c1a309f5ec34 110076 devel optional
petsc_3.14.4+dfsg1-2.debian.tar.xz
ca803f14f6f72d8ff244945697539801 12452 devel optional
petsc_3.14.4+dfsg1-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmBGXwMUHGRwYXJzb25z
QGRlYmlhbi5vcmcACgkQVz7x5L1aAfqMGQ/+NGVfKazwI4e6U9PWlFSMw9O2kFQz
DydUtLIuhHYIrdCJcxf6WSXd0ZYP5KtbIT0x84iK8+XWP2yX7jXZyxpgPNXpjCLi
SVPb4BM9qZSkegLpZwSYnaSeoRtCTKY26pbzw29dj3bhpSavgIHQX/KqDyrzNJOj
gciuXnD9EUroRMVFF+JlXFnuwn5bMlEwL3q73HUS9xY0UMd/IEVK1bSV2JCywwFD
3dSD3PpZvSLtFGxT8XprACgUe8T0KEEBS4O1J0Weju3YYxVX6LgFECzAqnCKeQlz
A5pfnqWpDxdDt3wN9FtFSv8w2LY7cQne2i8AUIDrDQaZPuWPFfhRU+GJpyAV1Ea+
Ra952uUcYl5CFdKSdcqCzFCRqC4gwIjcCdLu0F+S1eATkRWwyc6RZ99B3ikqMVO2
/5nyLsaadmRPwWo58L9xyQ/sRi23xP20qEOypbAY+qxYPSWBpJTXqLsMZC9mcwtz
kSCBF7yECh0x/ap1ZLsrIrWVl5eCd1Ca3wFUU1casCDcT9Cf2ZIdsZHAtse+gBy0
GwGwDEi5+BJzpUT7Q9kU0FKuDIrqcpQ/TpfB8kdDqucplNistlhnHAV+QhQKmgei
y4ZkENU0KuD+mBm6OpfXoAV2uppRxCO1KuoOzU3dNC1vMlUe+NHB8vRRufgvy/cn
NgNv4+qyXZbkJM4=
=SPeg
-----END PGP SIGNATURE-----
--- End Message ---
