Re: Full install/removal/upgrade test results available
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 it's run before python-xpcom's.
> >
> > What if xulrunner-1.9.1's postinst would do nothing for configure ?
> > would the trigger still kick in when one installs xulrunner-1.9.1 only?
>
> 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 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 test before my last uploads)
Unpacking python-xpcom (from
.../python-xpcom_1%3a0.0~hg20100212-3_amd64.deb) ...
Processing triggers for xulrunner-1.9.1 ...
Obtaining the module object from Python failed.
<type 'exceptions.ImportError'>: No module named xpcom.server
Obtaining the module object from Python failed.
<type 'exceptions.ImportError'>: No module named xpcom.server
Setting up libncursesw5 (5.7+20100313-4) ...
Setting up libssl0.9.8 (0.9.8o-4) ...
Setting up mime-support (3.51-1) ...
update-alternatives: using /usr/bin/see to provide /usr/bin/view (view)
in auto mode.
Setting up python2.6-minimal (2.6.6-8+b1) ...
Setting up python2.6 (2.6.6-8+b1) ...
Setting up python-minimal (2.6.6-3+squeeze4) ...
Setting up python (2.6.6-3+squeeze4) ...
Setting up python-support (1.0.11) ...
Setting up libpython2.6 (2.6.6-8+b1) ...
Setting up python-xpcom (1:0.0~hg20100212-3) ...
Processing triggers for python-support ...
Yes, the xulrunner-1.9.1 trigger happens right after unpack... before
python-xpcom's postinst grrrr. I'm starting to hate dpkg triggers.
Mike
Reply to: