From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl-5.20.1 - has anybody managed to upgrade Perl?
Date: Tue, 07 Oct 2014 17:41:11 +0200 [thread overview]
Message-ID: <1412696471.12590.0@numa-i> (raw)
In-Reply-To: <e7522b3a3f0f5c148bdc1e389240da36@shmu.sk> (from tomas.mozes@shmu.sk on Tue Oct 7 10:50:53 2014)
On 10/07/2014 10:50:53 AM, Tomas Mozes wrote:
> On 2014-10-07 10:13, Helmut Jarausch wrote:
>> Hi,
>>
>> dev-lang/perl-5.20.1 is in the tree (unmasked), but trying to upgrade
>> gives me lots of blocks requiring versions which are not
>> in the tree, yet, like
>>
>> [blocks B ] <perl-core/Socket-2.13.0 ("<perl-core/Socket-2.13.0"
>> is blocking virtual/perl-Socket-2.13.0)
>>
>> Has anybody tried to upgrade to this version of Perl?
>>
>> Many thanks for some hints/comments,
>> Helmut
>
> emerge -av1 perl-cleaner
> emerge -av1O dev-lang/perl
These two worked just fine, BUT
> perl-cleaner --all
fails miserably showing many blocks mentioning versions which are not
in the (unstable) tree
like, e.g.
perl-core/File-Spec-3.480.0 (and 28 more of those)
Typically there is virtual/perl-File-Spec-3.480.0 which requires
perl-core/File-Spec
of the same version, but (here) there is only
perl-core/File-Spec-3.400.0
I wonder how all of you could get around this?
Many thanks for your help,
Helmut
next prev parent reply other threads:[~2014-10-07 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 8:13 [gentoo-user] perl-5.20.1 - has anybody managed to upgrade Perl? Helmut Jarausch
2014-10-07 8:31 ` Kerin Millar
2014-10-07 8:39 ` Kerin Millar
2014-10-07 8:50 ` Tomas Mozes
2014-10-07 15:41 ` Helmut Jarausch [this message]
2014-10-07 15:55 ` Tomas Mozes
2014-10-07 16:07 ` Andreas K. Huettel
2014-10-07 16:19 ` Helmut Jarausch
2014-10-07 16:32 ` covici
2014-10-07 8:53 ` covici
2014-10-07 9:22 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1412696471.12590.0@numa-i \
--to=jarausch@igpm.rwth-aachen.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox