I tried to reproduce the bug with upgrading a2ps, but failed. What I did: Before each test, on a sarge machine, with only the base system installed, I installed the old versions of a2ps (1:4.13b-4) and emacsen-common (1.4.15). Also depdendencies of these, from current sarge.
The tests: * dist-upgrading both to the current sarge versions (1:4:13b-4.3 and 1.4.16). No problems. * Installing only the current sarge version of a2ps with the old version of emacsen-common. Again, no problems. * Unpacking the current sarge version of emacsen-common, editing its postinst to fail (exit 1 at the end), then dist-upgrading. As expected, the configure phase of emacsen-common failed. apt-get didn't even try to upgrade a2ps, so the problem was not repeated. Fixing the postinst back to working and doing a dist-upgrade again upgraded both packages properly. I played around with the system in other ways as well, but couldn't get the problem to appear. I also don't know of a situation where apt-get will run dpkg on a package before its (pre-)dependencies have been fixed, but admittedly my knowledge of the inner workings of apt-get are somewhat vague. I propose, therefore, that what happened may have been a fluke or caused by something else having slighly broken apt-get during the dist-upgrade run. This would then make the problem unreproducible and probably unfixable. (I'm not the maintainer of the package, I'm merely having a look at the release critical bugs for Debian and seeing if I can reproduce or otherwise help fix them.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
