hi, I just damages my system real hard and I'm in a middle of solving it, here is what happed: one day someone added acl use flag as default (i'm running x86) so when I run "#emerge -uD world" I've got attr and acl installed. Since then I had updated my system few times so many system critical packages was remerged. Today I run "#emerge sync" and "#emerge -uD world", I unmerged mldonkey necouse I didn't needet it anymore, after that I had run "#emerge depclean -pv" to unmerge any mldonkey dependecies, it listed acl and attr packages as unneeded, the acl use flag was now disabled by default on my arch (x86), I let it unmerge those packages and after that I wanted to run revdep-rebuild to fix packages that were depending on acl, it listed few packages including coreutils, but the problem is that coreutils apps like install, mv, cp, ls etc. are broken, they don't work, when I run "#ls" I get: >ls: error while loading shared libraries: libacl.so.1: cannot open shared object file: No such file or >directory I can't emerge anything so I'm stuck with system that if I will shut down I won't probably boot completly anymore. My request if FEATURES="unmerge_backup_or_something_more_fancy" is set then during umerge portage should build binary package before deleting files, so if something like this happens there are files that can be used for recovery. I can set buildpkg but that's just too much, or maybe packages should be build automaticly only during depclean. I just basicly think that we should have some protection from deleting libraries that if missing can make system unusable. Łukasz Mierzwa
There's a very large, bright red, strongly marked, capital letter, counter-delayed warning on depclean.
I'm just brainstorming here, so feel free to ignore if I'm being stupid. Would it be a good idea to recommend in the warning message to run emerge --update --deep --newuse [system | world ] prior to running emerge depclean to minimize the risk of damage to the system?
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
