You are talking about my changes apparently :) Right, prerm purge really does not exist according to the Policy. This makes me wondering how this change was fixing the problem for the original reporter..
The revert is attached and alternatively available at bzr branch bzr+ssh://bzr.debian.org/~mitya57-guest/public_bzr/python-defaults/revert-prerm-postrm -- Dmitry Shachnev On Thursday, 07/02/2013 at 22:18 +0100, Julien Cristau wrote: > On Sun, Feb 3, 2013 at 21:03:36 +0100, Piotr Ozarowski wrote: > > > > And as discussed on IRC the prerm/postrm changes are broken and need a > > > revert. > > > > please be more verbose for those of us who did not participate in this > > discussion (or do not remember it) > > - removing configuration in postrm remove is a no-no > - prerm purge does not exist. > > Cheers, > Julien
=== modified file 'debian/changelog' --- a/debian/changelog 2012-10-21 21:05:39 +0000 +++ b/debian/changelog 2013-02-08 05:43:10 +0000 @@ -1,3 +1,11 @@ +python-defaults (2.7.3-4) UNRELEASED; urgency=low + + * Revert my prerm/postrm changes: + - prerm is never called as `prerm purge`. + - configuration files shouldn't be deleted on package remove. + + -- Dmitry Shachnev <mity...@gmail.com> Fri, 08 Feb 2013 09:40:02 +0400 + python-defaults (2.7.3-3) unstable; urgency=low [ Piotr Ożarowski ] === modified file 'debian/python.postrm.in' --- a/debian/python.postrm.in 2012-10-08 10:31:51 +0000 +++ b/debian/python.postrm.in 2013-02-08 05:43:10 +0000 @@ -1,7 +1,8 @@ #! /bin/sh set -e -case "$1" in remove|purge) +case "$1" in + purge) rm -rf /etc/python esac === modified file 'debian/python.prerm.in' --- a/debian/python.prerm.in 2012-10-09 10:27:24 +0000 +++ b/debian/python.prerm.in 2013-02-08 05:43:10 +0000 @@ -1,7 +1,8 @@ #! /bin/sh set -e -case "$1" in remove|purge) +case "$1" in + remove) rm -f /usr/share/python/pyversions.py[co] esac
signature.asc
Description: This is a digitally signed message part
