Earlier today, I did an emerge --sync and proceeded to update world, including portage (now 2.0.53). I have an amd64 system running mostly stable, with a bunch of ~amd64 packages listed in my package.keywords and a small portage tree overlay that is not of relevance here.
Now. For some reason, even after updating everything else, "emerge
-auDv world" still wants to pull in sys-apps/busybox-1.00-r4. I have
had sys-apps/busybox in my package.mask file ever since it getting
pulled in as a dependency to something severely crippled my system,
and I do not want to have to go through that again.
Running "emerge -auDvet world" indicates that nothing depends on
busybox, nor does it depend on anything else. It is not in my
/var/lib/portage/world. So why does portage want to install it, and
how do I get portage to *not* install it without that giving me the
"all ebuilds that could satisfy 'sys-apps/busybox' have been masked"
whenever I want to do *any* update?
If it helps, along with the above error message I also get:
!!! Problem resolving dependencies for sys-apps/busybox
!!! Depgraph creation failed.
--
Michael Kjörling, [EMAIL PROTECTED] - http://michael.kjorling.com/
* ASCII Ribbon Campaign: Against HTML Mail, Proprietary Attachments *
* ..... No bird soars too high if he soars with his own wings ..... *
pgpv59yydxjt3.pgp
Description: PGP signature
