Summary: | portage version 2.1.4.4 deletes seriously needed files | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Bodo Thiesen <bothie> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | CC: | esigra |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Test script quoted in the initial post (first line is an ls which I removed in the initial post. Second line is the cd to my overlay, to you have to change that to /usr/portage/sys-apps if you're gonna try it on a system without overlay.) |
Description
Bodo Thiesen
2008-05-30 18:56:40 UTC
Created attachment 154863 [details]
Test script quoted in the initial post (first line is an ls which I removed in the initial post. Second line is the cd to my overlay, to you have to change that to /usr/portage/sys-apps if you're gonna try it on a system without overlay.)
(In reply to comment #0) > world, figure out which packages needs updating to resolve the blocking > problems and then just emerge -1O =category/package-version that package(s) > with -collision-protect. After that emerge world works fine generally. You should set FEATURES="-unmerge-orphans" if you're doing that. However, your approach is not obsolete in >=portage-2.1.5 and it should be going stable in approximately 2-3 weeks (I have a 2.1.5.3 release going in the tree today that may be the one to get marked stable). In portage-2.1.5 file collisions between blocking packages are resolved automatically as described here: http://planet.gentoo.org/developers/zmedico/2008/05/09/blocking_package_file_collisions *** This bug has been marked as a duplicate of bug 195527 *** (In reply to comment #2) > You should set FEATURES="-unmerge-orphans" if you're doing that. However, your > approach is not obsolete in >=portage-2.1.5 and it should be going stable in Should be "your approach is _now_ obsolete". |