Summary: | Installer: collision-protect: Compiled python (.pyo) files collide with portage update | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
Component: | [OLD] Core system | Assignee: | osx porters <osx> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | akos, charles, daniel.forst, dirk.schoenberger, elwood, itabtabai, sweetzombiejesus, sydbarrett74 |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 107759 | ||
Bug Blocks: |
Description
Alexander Skwar
2005-04-24 22:26:03 UTC
nothing we can do about this, disable collision-protect for the update Wouldn't it be possible to debug portage so, that collision-protect doesn't complain about compiled python files? sure that's possible, but why should we do that? The issue here was a bug in previous portage ebuilds, which was fixed now, so why should we keep and support a bug? *** Bug 99326 has been marked as a duplicate of this bug. *** *** Bug 99661 has been marked as a duplicate of this bug. *** *** Bug 100419 has been marked as a duplicate of this bug. *** *** Bug 102956 has been marked as a duplicate of this bug. *** *** Bug 103677 has been marked as a duplicate of this bug. *** And how do I disable that? I commented out the FEATURES entry in make.conf i explicitedly set FEATURES to '' emerge -u portage and I still get the same message sorry: make sure the FEATURES line is back in your make.conf then emerge portage: env FEATURES="-collision-protect" emerge --nodeps portage thanks that did the trick (In reply to comment #9) > And how do I disable that? > > I commented out the FEATURES entry in make.conf > i explicitedly set FEATURES to '' > emerge -u portage and I still get the same message FYI, Many of the variables in make.conf are cascaded, meaning they are confined from multiple files. Just removing FEATUREs from make.conf won't make the variable go away, since FEATURES are also usually set in make.globals and in your profile. In the future when you need to modify the environment you need to use FEATURES="-myfeature" or USE="-gtk" or whatnot. *** Bug 105497 has been marked as a duplicate of this bug. *** *** Bug 107054 has been marked as a duplicate of this bug. *** *** Bug 107105 has been marked as a duplicate of this bug. *** Re-Opening until next pkg installer is released. *** Bug 107624 has been marked as a duplicate of this bug. *** Why has this been changed to prodcut "Gentoo for Darwin/OS X"? It happens on "plain" Gentoo as well. Changing back to product = Gentoo Linux. (In reply to comment #18) > Why has this been changed to prodcut "Gentoo for Darwin/OS X"? It happens on > "plain" Gentoo as well. Because its fixed on current linux install media AFAICT. Its not fixed in the current OS X installer. Am I missing something? > > Changing back to product = Gentoo Linux. we should make a new bug on the installer and list all the current problems, CHOST, FETCH_COMMAND etc etc on it for that purpose. *** Bug 122210 has been marked as a duplicate of this bug. *** Don't use classic Gentoo for Mac OS X any more. Consider Gentoo Prefix instead. http://www.gentoo.org/proj/en/gentoo-alt/prefix/ |