Re: Bug#680626: Squeeze->Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Wed, Aug 01, 2012 at 12:22:22AM +0200, Julien Cristau wrote:
> On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote:
>
> > On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote:
> >
> > > W/o having looked yet at the details I'd say this *seems* like #671711,
> > > which I'm not planning on fixing for wheezy as it would introduce
> > > regressions on other situations, and given that this behaviour has
> > > been around since the introduction of triggers, and while quite
> > > unfortunate it's something that will have to be worked around on the
> > > affected packages because older dpkg will not be able to handle this
> > > correctly anyway.
> > >
> > > Going to look now, to make sure the above is the case.
> > >
> > That seems likely. What is the recommended workaround here? Should
> > package postinsts just ignore failures when called with 'triggered', or
> > is there a better way?
> >
> Ping? Any ideas?
I can understand the reasons not to fix the trigger bug, sounds like
something not that tricky.
However, given how it actually break the upgrade process, and will like
likely in the future, it would probably be a good idea to document
somewhere for package maintainers how to work around it.
I can commit to test further during the freeze if the upgrade process goes
well, and having this kind of documentation to point maintainers at would
help. If it already exists, please share the link.
bert.
Reply to: