On Fri, May 20, 2016, at 16:33, walt wrote: > I spent most of today updating from perl-5.22 to perl-5.24 because so > many packages failed to install. I ran perl-cleaner about a hundred > times and tried emerge -ac in between, which always failed because it > falsely accused me of not doing emerge -auND. > > Finally I got through the perl update and noticed a message saying > 'emerge -auND --with-bdeps=y is the ultimate way to update...' so I > added the '--with-bdeps=y' and another twenty perl-related packages got > rebuilt after I thought I was done. > > Now I'm really done, I think, but I'm afraid to reboot this machine. > >
I had the perl 5.24 update go off without a hitch on three other boxes, but this morning I'm having a heck of a time upgrading it on #4. Everything appears to go fine until: > Couldn't copy cpan/podlators/blib/script/pod2man to > /var/tmp/portage/dev-lang/perl-5. > 24.0/image//usr/bin/pod2man: No such file or directory > Couldn't chmod 755 > /var/tmp/portage/dev-lang/perl-5.24.0/image//usr/bin/pod2man: No s > uch file or directory > /usr/bin/pod2text > Couldn't copy cpan/podlators/blib/script/pod2text to > /var/tmp/portage/dev-lang/perl-5 > .24.0/image//usr/bin/pod2text: No such file or directory > Couldn't chmod 755 > /var/tmp/portage/dev-lang/perl-5.24.0/image//usr/bin/pod2text: No > such file or directory > /usr/bin/pod2usage > Couldn't copy cpan/Pod-Usage/blib/script/pod2usage to > /var/tmp/portage/dev-lang/perl- > 5.24.0/image//usr/bin/pod2usage: No such file or directory > Couldn't chmod 755 > /var/tmp/portage/dev-lang/perl-5.24.0/image//usr/bin/pod2usage: No > such file or directory Then everything rolls along 'til dying with this: > installman: Can't open cpan/podlators/blib/script/pod2man: No such file or > directory > ABORTED Surprising to have this build fail like this when I've done it elsewhere. Odd. -- 0x7D964D3361142ACF
