Bug#606791: Full install/removal/upgrade test results available

[Jakub Wilk]

* Mike Hommey <mh at glandium.org>, 2010-11-19, 09:18:
>> Mike Hommey <glandium at 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 ordering: the xulrunner-1.9.1 trigger can't 
>work until the python-support trigger has been run...

I don't see how pre-depends could have helped here. On the first glance 
it makes it only worse. E.g., when I install python-xpcom in a clean 
chroot I get:

| Unpacking python-xpcom (from .../python-xpcom_1%3a0.0~hg20100212-2_i386.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

When I moved ${xulrunner:Depends} from Pre-Depends to Depends, 
everything was registered just fine.

>The only fix for that issue that I can think of would be to stop using 
>python-support... If other people have ideas, I'm all ears.

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).

-- 
Jakub Wilk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 606791.diff
Type: text/x-diff
Size: 885 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20101221/43ca3f83/attachment.diff>