Package: libx52pro0 Version: 0.1.1-2.1 Severity: serious Tags: wheezy User: debian...@lists.debian.org Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
It can be installed and removed in wheezy.
It can neither be installed in sid (it it not in jessie), nor can
it be removed in jessie or sid (after installing it in wheezy and
distupgrading).
Since there is no package version in jessie, this is a bug in the
package in *wheezy*.
>From the attached log (scroll to the bottom...):
1m52.7s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpqBa2iF',
'apt-get', 'remove', 'libx52pro0']
1m53.1s DUMP:
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
libx52pro0
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 80.9 kB disk space will be freed.
(Reading database ... 7482 files and directories currently installed.)
Removing libx52pro0 (0.1.1-2.1) ...
dpkg: error processing package libx52pro0 (--remove):
subprocess installed post-removal script returned error exit status 2
Errors were encountered while processing:
libx52pro0
E: Sub-process /usr/bin/dpkg returned an error code (1)
1m53.1s DEBUG: Command failed (status=100), but ignoring error: ['chroot',
'/tmp/piupartss/tmpqBa2iF', 'apt-get', 'remove', 'libx52pro0']
This is probably caused by the udevadm calls in the postrm script:
case "$1" in
purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
case $(uname -s) in
Linux)
if which udevadm >/dev/null 2>&1; then
udevadm control --reload-rules
udevadm trigger
fi
;;
esac
;;
cheers,
Andreas
libx52pro0_None.log.gz
Description: application/gzip
