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 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.
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 but not configured ?
If you add a dependency from xulrunner to python-xpcom this problem
ought to go away (although if that would lead to a circular dependency
the situation is more complicated as dpkg will need to break the
cycle).
Ian.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/19737.10324.139286.394...@chiark.greenend.org.uk
