Your message dated Fri, 30 Sep 2016 12:38:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#825350: postgresql-filedump: leaves alternatives after
purge: /usr/bin/pg_filedump -> /etc/alternatives/pg_filedump
has caused the Debian Bug report #825350,
regarding postgresql-filedump: leaves alternatives after purge:
/usr/bin/pg_filedump -> /etc/alternatives/pg_filedump
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.)
--
825350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825350
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-filedump
Version: 9.5.0-2
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#s-removedetails
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...):
0m33.9s ERROR: WARN: Broken symlinks:
/usr/bin/pg_filedump -> /etc/alternatives/pg_filedump
/etc/alternatives/pg_filedump -> /usr/lib/postgresql/9.5/bin/pg_filedump
0m38.2s INFO: Warning: Package purging left files on system:
/etc/alternatives/pg_filedump -> /usr/lib/postgresql/9.5/bin/pg_filedump
not owned
/usr/bin/pg_filedump -> /etc/alternatives/pg_filedump not owned
cheers,
Andreas
postgresql-filedump_9.5.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 9.6.0-1
Re: Andreas Beckmann 2016-05-26
<[email protected]>
> 0m33.9s ERROR: WARN: Broken symlinks:
> /usr/bin/pg_filedump -> /etc/alternatives/pg_filedump
> /etc/alternatives/pg_filedump -> /usr/lib/postgresql/9.5/bin/pg_filedump
>
> 0m38.2s INFO: Warning: Package purging left files on system:
> /etc/alternatives/pg_filedump -> /usr/lib/postgresql/9.5/bin/pg_filedump
> not owned
> /usr/bin/pg_filedump -> /etc/alternatives/pg_filedump not owned
This was fixed in 9.6.0-1, but not noted in the changelog.
The problem was a mistake done when the package was updated for 9.5;
updating now for 9.6 fixed it more or less automatically.
Thanks for the report!
Christoph
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
