Summary: | Some dep-clean / unmerge troubles portage-2.0.25 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Adrian Almenar <aalmenar> |
Component: | Unclassified | Assignee: | Dave Nellans <dave> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | aalmenar, carpaski, karltk, kevin |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 6020 |
Description
Adrian Almenar
2002-08-06 19:50:21 UTC
I would go along with you and say that this is a bug. Taking glibc off of your system will definately bork it up ;-) I did that once upgrading manually back in the day. I am guessing this is a portage bug? I am wondering though why you would want to remove glibc... //Davis i just wanted to remove the OLD glibc as dep-clean reported. but that just screw up my system. This is a bug in dep-clean but not in Portage; emerge search displays the most recent version installed, but it doesn't display the last version installed. dep-clean keeps the most recent version, which in your case was 2.2.5-r5, but 2.2.5-r2 was installed *after* the 2.2.5-r2 install, thus frying your system. I'm assigning this to Karl and I suggest that dep-clean is removed from the gentoolkit package that he maintains since it isn't safe. "emerge --clean" will always do the safe thing; dep-clean (just found out about this script today) does not do the right thing. It'd be really nice if you had the time to whip up at least a work-around for this one by 29th of August, so that we may in good conscience ship dep-clean with the 1.4 Gentoo release. dep-clean is now deprecated, as portage can handle this via 'emerge depclean' i'm not sure this is a mute issue, perhaps you can elaborate. according to the changelog for portage "emerge depclean" cleans out all packages which are not explicitly installed (i assume this means in world or system) and are not depended on by another explicitly installed package. depclean's current functionality (including all the bugs i haven't dealt with because with a broken wrist for the last month limits my ability to type significanly) lists packages which are are installed but no longer in portage (typically just outdated), all packages which are installed but can be upgraded including packages which aren't explicitly installed, and packages which are installed but were not installed explicitly nor are depended on by a explicitly installed package (this is what the emerge depclean takes care of). so for now i believe the best option will be to remove the 3rd function from dep-clean as it is redundant as to what is in portage, and leave the other two intact in an updated dep-clean which i'm going to get around to this week hopefully when the cast comes off... input appriciated dave this bug can be closed ?? leave this open for now... i'm trying to get a feel if its worth updating dep-clean or if we can drop it from toolkit as a whole, will decide within the next week. Dep-clean has been decomissioned and i don't hear any barking so i'm closing all dep-clean related bugs. yell if you want it back! |