Summary: | Package dev-lang/python-exec-2.4.4 NOT merged due to file collisions | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michal Jakubowski <michal.jakubowski> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bug, chicago, duncan, gentoo-bugs, kensington, kripton, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michal Jakubowski
2017-01-11 07:56:19 UTC
The same here. >>> Installing (1 of 2) dev-lang/python-exec-2.4.4::gentoo * checking 15 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * package dev-lang/python-exec-2.4.4 NOT merged * * Detected file collision(s): * * /usr/bin/python-config * /usr/bin/python3 * /usr/bin/python * /usr/bin/2to3 * /usr/bin/python2 * /usr/bin/pydoc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * Same here. Those are the packages that python-exec-2.4.4 collide with: ~ # equery b /usr/bin/pydoc * Searching for /usr/bin/pydoc ... dev-lang/python-3.4.5 (/usr/bin/pydoc3.4) ~ # equery b /usr/bin/idle * Searching for /usr/bin/idle ... dev-lang/python-3.4.5 (/usr/bin/idle3.4) ~ # equery b /usr/bin/2to3 * Searching for /usr/bin/2to3 ... dev-lang/python-3.4.5 (/usr/bin/2to3-3.4) ~ # equery b /usr/bin/python-config * Searching for /usr/bin/python-config ... ~ # equery b /usr/bin/python3 * Searching for /usr/bin/python3 ... dev-lang/python-3.4.5 (/usr/bin/python3.4m) ~ # equery b /usr/bin/python2 * Searching for /usr/bin/python2 ... dev-lang/python-2.7.12 (/usr/bin/python2.7) ~ # equery b /usr/bin/python * Searching for /usr/bin/python ... app-eselect/eselect-python-20140125-r2 (/usr/bin/python-wrapper) Those are unavoidable. We won't be adding any workarounds in ebuilds because that could cause you to end up with no 'python' executable in case or an error. Either use protect-owned, or temporarily disable collision-protect to merge this. I'm going to keep the bug open for some time to reduce duplicates. *** Bug 605382 has been marked as a duplicate of this bug. *** (In reply to Michał Górny from comment #3) > ... or temporarily disable collision-protect to merge > this. Yeap, I confirm Thanks I'm a little confused. Does this mean that these symlinks are no longer going to be provided by dev-lang/python, or is this message going to happen again when a new version of dev-lang/python is stabilised? I'm pretty sure I didn't have any message like this when I installed python-exec-2.0.2 over python-exec-2.0.1-r1 (though it's possible I'm just misremembering). In any case, this seems like a major enough thing that it should probably be a news item in "eselect news". The symlinks are being replaced to be owned by a single package rather than being unowned. It's a generic effort, though slow-going, aiming to clean up the filesystem from files outside 'writable' directories that are created outside packages. Which means you can expect further collisions in the future as we move more files into packages. You opt in to those errors by using FEATURES=collision-protect. It's a mutual agreement that you want Portage to be extra careful but you agree to investigate every case manually. If you don't want that (and just trust packages always to do the right thing), you can resort to default FEATURES=protect-owned instead. That's the thing, though. I use FEATURES=protect-owned (as my default setup), but as soon as I saw that the collisions involved Python (and knew that it would be safe to stop it), I Ctrl-C'd it. I wasn't about to risk that without investigation. I've done that now by finding this bug, but even people using the default setup will want to investigate something like this, I reckon. I think that having a news entry for something as major as this is warranted, because collisions are not part of a normal healthy Gentoo maintenance schedule, and many people up to now may not even have seen any. It's a little scary to see it come up. (In reply to Sophie Hamilton from comment #9) > That's the thing, though. I use FEATURES=protect-owned (as my default > setup), but as soon as I saw that the collisions involved Python (and knew > that it would be safe to stop it), I Ctrl-C'd it. I wasn't about to risk > that without investigation. I've done that now by finding this bug, but even > people using the default setup will want to investigate something like this, > I reckon. > > I think that having a news entry for something as major as this is > warranted, because collisions are not part of a normal healthy Gentoo > maintenance schedule, and many people up to now may not even have seen any. > It's a little scary to see it come up. YES! We definitely need a news entry for such important things. News item committed now. Let's keep this bug for a while longer so that people who didn't read it can find it. Thank you! A quick note, though: /usr/bin/idle is also a potential collision. It was on my system. |