On Tue, Dec 21, 2010 at 09:41:54PM +0100, Jakub Wilk wrote: > * Mike Hommey <m...@glandium.org>, 2010-12-21, 20:59: > >>I think you could manually trigger xulrunner-1.9.1 in > >>python-xpcom's postinst if it's not already registered. See the > >>attached patch (well, except maybe xulrunner version shouldn't > >>be hardcoded). > > > >I'd expect that to fail as well, because of python-support trigger not > >having been run yet. > > > >Part of the problem is that the xulrunner-1.9.1's postinst or trigger can > >run with python-xpcom unpacked but not registered with python-support. > > > >Adding update-python-modules -p in python-xpcom postinst could make > >things slightly better, > > "update-python-modules -p" is already in python-xpcom's postinst and > it does exactly what python-support trigger would do.
Which I must have added in an attempt to fix the issue, so it's possibly not enough. > >but that would still leave xulrunner-1.9.1's postinst complaining > >if it's run before python-xpcom's. > > Unfortunately, this is true. But then, it's only noise, which is still better than a failure to upgrade. So in the worst case scenario where we don't find anything better, and if we are sure it doesn't break any other case, we could just remove the pre-depend and be done with it. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
