Mike Hommey writes (Re: Full install/removal/upgrade test results available):
On Mon, Dec 27, 2010 at 11:59:16PM +, Ian Jackson wrote:
So the problem is that python-xpcom does not work when it has been
previously installed, and then during an upgrade the new version has
been unpacked
Le mercredi 29 décembre 2010 à 12:50 +, Ian Jackson a écrit :
If so, that's a bug in python-xpcom. Any package which registers a
hook with another package must be prepared for its hook to be run even
when the registering package is not configured. If this is a problem,
arrangements
On Wed, Dec 29, 2010 at 01:52:13PM +0100, Josselin Mouette wrote:
Le mercredi 29 décembre 2010 à 12:50 +, Ian Jackson a écrit :
If so, that's a bug in python-xpcom. Any package which registers a
hook with another package must be prepared for its hook to be run even
when the registering
On Wed, Dec 29, 2010 at 12:50:06PM +, Ian Jackson wrote:
Mike Hommey writes (Re: Full install/removal/upgrade test results
available):
On Mon, Dec 27, 2010 at 11:59:16PM +, Ian Jackson wrote:
So the problem is that python-xpcom does not work when it has been
previously
Le mercredi 29 décembre 2010 à 14:14 +0100, Mike Hommey a écrit :
Which would also mean firing dpkg-trigger in python-xpcom.postinst, too.
This all looks like overcomplication to circumvent an imho design flaw in
python packages.
Call it a design flaw, but no package is expected to actually
Le mercredi 29 décembre 2010 à 14:19 +0100, Mike Hommey a écrit :
xulrunner has a file trigger for components in
/usr/lib/xulrunner-1.9.1/components, so that it registers them in
compreg.dat and xpti.dat. This means it has to load the components to
get their registration information. But the
On Mon, Dec 27, 2010 at 11:59:16PM +, Ian Jackson wrote:
Mike Hommey writes (Re: Full install/removal/upgrade test results
available):
Unfortunately, while some cases were fixed, the original case for which
the pre-depends was added fails again :(
(starting from xulrunner-1.9.1
On Wed, Dec 22, 2010 at 08:36:38PM +0100, Josselin Mouette wrote:
Le mardi 21 décembre 2010 à 20:59 +0100, Mike Hommey a écrit :
Adding update-python-modules -p in python-xpcom postinst could make
things slightly better, but that would still leave xulrunner-1.9.1's
postinst complaining if
Le lundi 27 décembre 2010 à 18:57 +0100, Mike Hommey a écrit :
On Wed, Dec 22, 2010 at 08:36:38PM +0100, Josselin Mouette wrote:
You could use dpkg-trigger to force the trigger to be run after
xulrunner-1.9.1 being installed.
Unfortunately, while some cases were fixed, the original case
On Mon, Dec 27, 2010 at 09:08:14PM +0100, Josselin Mouette wrote:
Le lundi 27 décembre 2010 à 18:57 +0100, Mike Hommey a écrit :
On Wed, Dec 22, 2010 at 08:36:38PM +0100, Josselin Mouette wrote:
You could use dpkg-trigger to force the trigger to be run after
xulrunner-1.9.1 being
Mike Hommey writes (Re: Full install/removal/upgrade test results available):
Unfortunately, while some cases were fixed, the original case for which
the pre-depends was added fails again :(
(starting from xulrunner-1.9.1 already installed, and installing
python-xpcom, case which I forgot to
Le mardi 21 décembre 2010 à 20:59 +0100, Mike Hommey a écrit :
Adding update-python-modules -p in python-xpcom postinst could make
things slightly better, but that would still leave xulrunner-1.9.1's
postinst complaining if it's run before python-xpcom's.
What if xulrunner-1.9.1's postinst
* Mike Hommey m...@glandium.org, 2010-11-19, 09:18:
Mike Hommey gland...@debian.org
python-xpcom (U)
I /think/ this could be solved by not using a pre-depends on
xulrunner-1.9.1.
Indeed.
OTOH, the pre-depends solves a part of another problem though not
entirely, due to triggers
On Tue, Dec 21, 2010 at 08:37:53PM +0100, Jakub Wilk wrote:
* Mike Hommey m...@glandium.org, 2010-11-19, 09:18:
Mike Hommey gland...@debian.org
python-xpcom (U)
I /think/ this could be solved by not using a pre-depends on
xulrunner-1.9.1.
Indeed.
OTOH, the pre-depends solves a part
* 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
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
16 matches
Mail list logo
