Your message dated Wed, 19 Feb 2014 23:28:17 +0100
with message-id <53053001.8000...@debian.org>
and subject line Re: Bug#736285: python-babel: leaves alternatives after purge:
/usr/bin/pybabel
has caused the Debian Bug report #736285,
regarding python-babel: leaves alternatives after purge: /usr/bin/pybabel
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 ow...@bugs.debian.org
immediately.)
--
736285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-babel
Version: 1.3-1
Severity: important
User: debian...@lists.debian.org
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:
http://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 http://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...):
1m41.9s INFO: Warning: Package purging left files on system:
/etc/alternatives/pybabel -> /usr/bin/pybabel-python2 not owned
/usr/bin/pybabel -> /etc/alternatives/pybabel not owned
This was observed after an upgrade from jessie to sid.
cheers,
Andreas
nova-common_2013.2-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
On 2014-02-19 03:25, Thomas Goirand wrote:
> Hi Andreas,
>
> What I don't understand is that the python-babel package does follow the
> advice which you are giving in this bug report. So, I would really like
> to fix the problem, but I will need help here, to know what's done
> wrong. Please advise.
Cannot reproduce this any more. This must have been a stale logfile left
over after I had rechecked (supposedly) everything after my NMU.
Andreas
--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
