Summary: | app-eselect/eselect-python-20151117-r2 file collision with python symlinks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MarisN <maris.gis> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | mmokrejs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
MarisN
2016-01-02 16:41:27 UTC
Unless you have FEATURES="protect", portage will replace the un-owned symlinks, despite the warning message. *** Bug 570850 has been marked as a duplicate of this bug. *** If the default of FEATURES=protect-owned is unsuitable, then that seems to be a separate bug. This package still fails to install, and this bug should remain open so long as that remains true. This problem does not occur with a default portage config. (In reply to Mike Gilbert from comment #4) > This problem does not occur with a default portage config. I wouldn't lie to you. :) At a minimum, it occurs on my x32 (not x86) test VM that uses a default portage config. Been broken for weeks and repeatable. (In reply to Greg Kubaryk from comment #5) > (In reply to Mike Gilbert from comment #4) > > This problem does not occur with a default portage config. > > I wouldn't lie to you. :) At a minimum, it occurs on my x32 (not x86) test > VM that uses a default portage config. Been broken for weeks and repeatable. Please paste your build log and 'emerge --info'. (In reply to Michał Górny from comment #6) > (In reply to Greg Kubaryk from comment #5) > > (In reply to Mike Gilbert from comment #4) > > > This problem does not occur with a default portage config. > > > > I wouldn't lie to you. :) At a minimum, it occurs on my x32 (not x86) test > > VM that uses a default portage config. Been broken for weeks and repeatable. > > Please paste your build log and 'emerge --info'. On my x32 test VM using a default portage config, the problem wound up being that profiles/arch/amd64/x32/make.defaults adds FEATURES=collision-protect. I have a snapshot from before understanding the problem, if you'd still like a build.log and emerge --info. I suspect the reporter of this bug probably does have that feature in their make.conf since their profile does not include FEATURES=collision-protect by default. Probably worth considering removing that entry from the x32 defaults. For my purposes, manually setting FEATURES=-collision-protect in make.conf worked well enough in the interim. (In reply to Greg Kubaryk from comment #7) Ah, that explains it. Unfortunately, there's not much I can do about a weird default setting in an arch profile. If someone has a solution that will work with collision-protect on, we will consider it. |