Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 456174 - File collision for dev-python/sphinx-1.1.3-r5 /usr/lib64/pythonX.X/site-packages/sphinx/pycode/GrammarX.X.pickle
Summary: File collision for dev-python/sphinx-1.1.3-r5 /usr/lib64/pythonX.X/site-packa...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
Depends on:
Reported: 2013-02-08 14:20 UTC by Chris Kerr
Modified: 2013-02-11 10:23 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Chris Kerr 2013-02-08 14:20:58 UTC
* package dev-python/sphinx-1.1.3-r5 NOT merged
 * Detected file collision(s):
 *      /usr/lib64/python2.7/site-packages/sphinx/pycode/Grammar2.7.pickle
 *      /usr/lib64/python3.2/site-packages/sphinx/pycode/Grammar3.2.pickle
 * Searching all installed packages for file collisions...
 * Press Ctrl-C to Stop
 * None of the installed packages claim the file(s).
 * Package 'dev-python/sphinx-1.1.3-r5' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

Presumably these files belong to sphinx but aren't known to portage; maybe in previous versions they were autogenerated after installation but now they are generated by the make file?
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2013-02-09 18:03:18 UTC
Yes, that's the case. It is a leftover junk from previous maintainer and there's basically no way we can avoid this. Even if we wanted to remove the files in pkg_preinst(), collision check is done earlier.

There's two things you can do:

1) remove the files by hand, then install sphinx.

If you didn't remove the files from PORTAGE_TEMPDIR, you can use 'ebuild /usr/portage/dev-python/sphinx/sphinx-1.1.3-r5.ebuild merge' to resume the install.

2) disable 'collision-protect' in favor of 'protect-owned'. The latter will only complain if files are owned by some package.
Comment 2 Chris Kerr 2013-02-11 10:23:13 UTC
Yes, in the end I just removed the files. I just thought it was worth reporting this in case it could be fixed in the ebuild.