In my case perl-cleaner was quite useless=( but it has an update since then, so maybe it will work now.
But if it will be blocking updates you can always do it in some brutal way=))) run emerge perl with "--nodeps" and after do the same for every package that uses perl.... you can find their files at /usr/lib64/perl5/vendor_perl/5.20.2/ and use something like portageq owners / /usr/lib64/perl5/vendor_perl/5.20.2/* to find all packages that need reinstall, again if perl-cleaner won't work simple emerge won't help, because it will try to compile some packages in wrong order and I have perl 5.24, using that repo /etc/portage/repos.conf/gentoo.conf [gentoo] location = /usr/portage/gentoo sync-type = git sync-uri = https://github.com/gentoo-mirror/gentoo.git auto-sync = true On Monday, June 20, 2016, lee <l...@yagibdah.de> wrote: > > Hi, > > how do you do an update despite perl blocking it? > > > emerge -a --update --newuse --deep --with-bdeps=y --keep-going @world > [...] > dev-lang/perl:0 > > (dev-lang/perl-5.22.2:0/5.22::gentoo, ebuild scheduled for merge) pulled > in by > =dev-lang/perl-5.22* required by > (virtual/perl-IO-Zlib-1.100.0-r6:0/0::gentoo, installed) > ^ ^^^^^ > (and 8 more with the same problem) > > (dev-lang/perl-5.20.2:0/5.20::gentoo, installed) pulled in by > dev-lang/perl:0/5.20=[-build(-)] required by > (dev-perl/Encode-Locale-1.30.0-r1:0/0::gentoo, installed) > ^^^^^^^^ > =dev-lang/perl-5.20* required by > (virtual/perl-Pod-Parser-1.620.0:0/0::gentoo, installed) > ^ ^^^^^ > (and 56 more with the same problems) > [...] > > > It seems that some pppl found perl 5.24 somewhere, which doesn't seem to > be available: > > > eix dev-lang/perl > [I] dev-lang/perl > Available versions: 5.20.2(0/5.20) ~5.20.2-r1(0/5.20) > ~5.22.0(0/5.22) ~5.22.1(0/5.22) {berkdb debug doc gdbm ithreads} > Installed versions: 5.20.2(01:11:43 AM 04/06/2015)(berkdb gdbm > -debug -doc -ithreads) > Homepage: http://www.perl.org/ > Description: Larry Wall's Practical Extraction and Report > Language > > > An update is overdue. What should I do? > >
