| Summary: | dev-python/logilab-constraint-0.5.0-r1 with dev-python/logilab-common-0.62.1 - file collision in /usr/lib64/python2.7/site-packages/logilab/__init__.py | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | pacho |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Toralf Förster
2014-12-10 11:46:23 UTC
with dev-python/logilab-common-0.61.0 emerged
~/cvsPortage/gentoo-x86/dev-python/logilab-constraint $ ebuild logilab-constraint-0.5.0-r1.ebuild clean install
yields success
>>> Completed installing logilab-constraint-0.5.0-r1 into /mnt/gen2/TmpDir/portage/dev-python/logilab-constraint-0.5.0-r1/image/
Did not replicate. Also
python_install() {
# Avoid collisions with dev-python/logilab-common.
rm -f "${D}$(python_get_sitedir)/logilab/__init__.py" || die
python_install
so possibly this does relate to your system being a hardened system.
While this could better be python_install_all, it works for me.
Needs replication.
+ 28 Feb 2015; Pacho Ramos <pacho@gentoo.org> + logilab-constraint-0.5.0-r1.ebuild: + The colliding file needs to be removed after distutils-r1_python_install + (#532132) + I was also reproducing it... Ian, were you running a full "emerge" run or only ebuild ... install? To get the collision detection I think that a full emerge is needed :) |