Hi Giuseppe,
You can use the DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT variable in the
maintainer script to tell whether or not to purge the file - it requires
dpkg (= 1.17.2)[1][2].
~Niels
[1]:
dpkg/1.17.2 changelog:
* Pass the package reference count (i.e. number of present instances)
to
Package: libpaper1
Version: 1.1.24+nmu2
Severity: important
The postrm purge removes /etc/papersize. In a setting where you can
purge libpaper1:i386 while still using libpaper1:amd64 this causes
trouble. The bug is currently unreproducible due to ucf lacking
M-A:foreign. As soon as ucf gains that
Control: forcemerge 682420 695271
The postrm purge removes /etc/papersize. In a setting where you can
purge libpaper1:i386 while still using libpaper1:amd64 this causes
trouble. The bug is currently unreproducible due to ucf lacking
M-A:foreign. As soon as ucf gains that flag, this bug is RC.
Control: reassign 695271 src:libpaper
Control: forcemerge 682420 695271
Next try.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Dec 06, 2012 at 02:44:08PM +0100, Giuseppe Sacco wrote:
What is the correct action sequence? When libpaper in i386 is purged
I believe that this is sufficiently discussed in #682420. You proposed a
solution yourself. Sorry for the noise.
Helmut
--
To UNSUBSCRIBE, email to
Thanks for pointing this out.
[...]
The postrm purge removes /etc/papersize. In a setting where you can
purge libpaper1:i386 while still using libpaper1:amd64 this causes
trouble. The bug is currently unreproducible due to ucf lacking
M-A:foreign. As soon as ucf gains that flag, this bug is
6 matches
Mail list logo
