Bug#596459: python-xpcom: file collision: /usr/include/xulrunner-1.9.1/unstable/PyXPCOM.h provided by xulrunner-dev 1.9.1.11-1

[Mike Hommey]

On Sat, Sep 11, 2010 at 05:55:18PM +0000, Sascha Silbe wrote:
> Package: python-xpcom
> Version: 1.9.1.11-1
> Severity: grave
> Justification: renders package unusable
> 
> 
> During "aptitude safe-upgrade" an update of python-xpcom was attempted and failed due to a file collision:
> 
> (Reading database ... 117353 files and directories currently installed.)
> Preparing to replace python-xpcom 1.9.1.11-1 (using .../python-xpcom_1%3a0.0~hg20100212-2_amd64.deb) ...
> Unpacking replacement python-xpcom ...
> dpkg: error processing /var/cache/apt/archives/python-xpcom_1%3a0.0~hg20100212-2_amd64.deb (--unpack):
>  trying to overwrite '/usr/include/xulrunner-1.9.1/unstable/PyXPCOM.h', which is also in package xulrunner-dev 1.9.1.11-1
> Preparing to replace debian-archive-keyring 2010.08.15 (using .../debian-archive-keyring_2010.08.28_all.deb) ...
> Unpacking replacement debian-archive-keyring ...
> Processing triggers for python-support ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/python-xpcom_1%3a0.0~hg20100212-2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

Just a note for the release team member that would take a look at this
bug, this is only a problem for upgrades from versions that were
previously in testing, before the transition to separate packages.
Upgrading/partially upgrading from lenny doesn't exhibit this problem.

I'm tempted to downgrade severity for the reason above, though it's
trivial to fix.

Mike