Hi! On Wed, 2015-10-07 at 01:10:33 +0200, Andreas Beckmann wrote: > Package: dpkg > Version: 1.18.3 > Severity: serious
> dpkg does not always properly pass the old version number when > calling "postinst configure" on package upgrades, sometimes there > is either no or an empty argument. That's to be expected, the second argument is the last version that got configured, if no version has ever been configured then the argument is omitted. Checking now, this is documented in Debian policy ยง6.7. > I have two cases where an 'apt-get dist-upgrade' from jessie to > stretch calls 'systemd.postinst configure' differently: > * a minimal jessie chroot (incorrect behavior) > * a minimal jessie chroot + bash-completion (correct behavior) > So in these two cases completely different codepaths in the postinst are > taken. > I don't know about other packages, since this is (so far) the only one leaving > a visible trace from this mistreatment in piuparts. (Well, there are several > other systemd symlink related problems that nobody managed to debug so far.) > Attached are two logs where I did this upgrade test with piuparts, but > it should be quite easy to reproduce it manually. I've not checked the logs, but I'd assume that in the problematic case the package has never been configured before, and as such the bug here is on that specific package. Thanks, Guillem
