Coreutils replaces textutils, fileutils and sh-utils. When "upgrading" these three independent packages they insert an empty package (as of latest releases on PPC). But, this removes ALL/MOST programs that are also in coreutils. This leaves the system in a unusable state. No other packages can be installed due to lack of uname (and many other programs). Reproducible: Always Steps to Reproduce: Update textutils, fileutils and sh-utils to empty packages with coreutils installed. Actual Results: Most (all) programs in coreutils are deleted but merging the blank placeholders for fileutils, sh-utils and textutils. Expected Results: Many options, but none of which that fall under normal operation of portage. It should not have deleted files used by two packages. Maybe build a binary package of coreutils before "upgrading" textutils, fileutils and sh-utils to empty packages. Seems like a ligistical nightmare. I guess this is a placeholder bug. I do not know how many people it effects. WORK AROUND: ------------ 1. Boot into a rescue CD. 2. CHROOT to your installed gentoo. 3. Unmerge fileutils, sh-utils and textutils. 4. Create a list of programs installed from coreutils. 5. Copy programs installed from coreutils from CD image to local HD. 6. emerge coreutils.
There's been a lot of bugs about this and I think it's been covered pretty well, so I'm just going to pick one that seems close to mark this one a duplicate. Please search for coreutils in bugzilla. Thanks. *** This bug has been marked as a duplicate of 31918 ***
I feel that the person who combinde this with bug 31918 did not read this bug carefully. My issue is not with the state of the packages. This bug deals with what happens because these packages have an incorrect relationship. When upgrading from textutils/fileutils/sh-utils to coreutils *ALL* Gentoo system with this package confusion will be left *UNUSEABLE* and *UNSTABLE*. I understand this might be my confusion but I have to reopen this bug to get it looked at again. I do not want to piss anybody off but I know there have to be 10's to 100's of users who will run into this issue.
Marking as fixed because there is not real way to fix this bug.
