public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kerin Millar <kerframil@fastmail.co.uk>
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 09:31:14 +0100	[thread overview]
Message-ID: <5433A4D2.2020702@fastmail.co.uk> (raw)
In-Reply-To: <1412669625.19459.0@numa-i>

On 07/10/2014 09: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?

Here is a generically applicable approach to handling upgrades in 
situations where a major dev-lang/perl update is queued.

1) emerge -auDN @world
2) If previous step fails: emerge -auDN --backtrack=30 @world
3) If previous step fails:
    a) emerge --deselect $(qlist -IC 'perl-core/*')
    b) Return to step #2
4) perl-cleaner -all
5) If previous step fails, follow the instructions in the error message
6) Re-select any perl modules that you may have explicitly requested

The final step won't apply to you unless you a Perl hacker.

--Kerin


  reply	other threads:[~2014-10-07  8:31 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 [this message]
2014-10-07  8:39   ` Kerin Millar
2014-10-07  8:50 ` Tomas Mozes
2014-10-07 15:41   ` Helmut Jarausch
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=5433A4D2.2020702@fastmail.co.uk \
    --to=kerframil@fastmail.co.uk \
    --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