It occurs to me on analysis of apt that the debsums part of this cannot
possibly cause an upgrade failure. The reason for this is that DPkg
::Post-Invoke hooks are run in precisely three cases:
1) waitpid for dpkg failed (i.e. some kind of programming error); return code
from Post-Invoke is ig
Avoiding things like File::Find in debsums is rather difficult. There's
another possibility: we could just have debsums bail out cleanly (with
an error message) if File::Find can't be imported. apt will get round
to running it again at a more convenient time anyway, and it will catch
up with all
** Changed in: debsums (Ubuntu)
Milestone: ubuntu-12.04-beta-1 => ubuntu-12.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901741
Title:
perl-modules lucid->precise upgrade failure: deb
Sounds great. Given the large number of packages using defoma, it might
be worth a comprehensive scan across lucid to make sure the no-op prerm
is in place for all of them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
On Thu, Jan 26, 2012 at 01:49:54AM -, Thomas Bushnell, BSG wrote:
> For this to work reliably in a cross-version lucid->precise upgrade,
> however, won't you need to push a new libwmf0.2-7 package in lucid that
> fixes its prerm?
No, because dpkg will fall back to the new prerm (i.e. the one i
Thanks for looking at this Colin; I appreciate the eyes! It's in the
depths of dark magic to me sometimes.
For this to work reliably in a cross-version lucid->precise upgrade,
however, won't you need to push a new libwmf0.2-7 package in lucid that
fixes its prerm?
--
You received this bug notifi
