an emerge of virtual/perl-DB_File is installing DB_File but does not provide the perl-core/DB_File in the portage dependancy tree. Since perl-cleaner is cleaning out DB_File and reemerging virtual/perl-DB_File the next emerge is installing perl-core/DB_File again.
*** Bug 127049 has been marked as a duplicate of this bug. ***
*** Bug 127050 has been marked as a duplicate of this bug. ***
*** Bug 127051 has been marked as a duplicate of this bug. ***
*** Bug 127052 has been marked as a duplicate of this bug. ***
*** Bug 127053 has been marked as a duplicate of this bug. ***
*** Bug 127054 has been marked as a duplicate of this bug. ***
Emerge the real ebuild, not the virtual...
(In reply to comment #7) > Emerge the real ebuild, not the virtual... > this would solve the problem. But than there is still the problem of perl-cleaner since perl-cleaner emerges the virtual ...
(In reply to comment #7) > Emerge the real ebuild, not the virtual... > and this clearly diff. with the other perl - packages like Time-Local. here the virtual provides the right dependancy
(In reply to comment #9) > and this clearly diff. with the other perl - packages like Time-Local. here the > virtual provides the right dependancy perl-cleaner doesn't unmerge anything, it merely re-emerges what's installed. Don't know what kind of dependency you are talking about either, Time-Local and DB_File virtuals are exactly the same wrt dependencies, just check the ebuilds. If you want to install something, then install the real thing, not virtual. It's not meant for such use.
Just seeing these bugs (sorry) - please confirm perl-cleaner version. Latest (admittedly ~arch'd still) has a 'fix' for making sure your virtuals are up to date.
(In reply to comment #11) > Just seeing these bugs (sorry) - please confirm perl-cleaner version. Latest > (admittedly ~arch'd still) has a 'fix' for making sure your virtuals are up to > date. > my perl-cleaner version is the lates (1.03).
(In reply to comment #10) > (In reply to comment #9) > perl-cleaner doesn't unmerge anything, it merely re-emerges what's installed. I'm sorry but at least on my system perl-cleaner is doing first an emerge -C and than an emerge of the virtual package. And this leaves at least mit DB-file the dependancy unresolved.