public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] preparing for profile switch -- major problem
Date: Mon, 11 Dec 2017 01:36:19 +1300	[thread overview]
Message-ID: <20171211013619.1fba2e7b@katipo2.lan> (raw)
In-Reply-To: <m3k1xvjbm2.wl-covici@ccs.covici.com>

[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]

On Sun, 10 Dec 2017 02:17:09 -0500
John Covici <covici@ccs.covici.com> wrote:

> OK, thanks, I think I will try that.

The problem you're facing is that you masked dev-lang/perl, but not any
virtual/perl-* or perl-core/-* to compensate.

These 3 components work in concert like a single component, as a sort
of bodge to compensate for the fact portage has no working "provides" feature,
and to compensate for the dependency-system missmatch between how
Gentoo works and how CPAN works.

Theres' no easy way of fixing this atm, but the short of it is if you're using
an ~arch dev-lang/perl, you should be using an ~arch virtual/perl-*,
and if you're using an "arch" dev-lang/perl, you should be using only
"arch" versions of virtual/perl-*

Once you do this, portage may still scream at you, because portage is
very much optimised for upgrading, and it tends to think downgrading is
an error.

So once you get all your masks/keyword changes in place, you should do:

  emerge -C virtual/perl-*
  emerge -C perl-core/*

(or something to that effect)

This looks scary, but generally isn't, because you're not actually removing
anything with this, just juggling a few balls and making only older
versions of certain things available ( as they're alls shipped in
dev-lang/perl )

And then after you do this, portage is more likely to be persuadable
into doing the right thing.

You can additionally abuse my tool, gentoo-perl-helpers for doing some of this,
and some of the steps I've described are automated because they're just
that safe and useful.

https://wiki.gentoo.org/wiki/Perl#app-admin.2Fgentoo-perl-helpers


After putting the right masks in place, do:

	gentoo-perl gen-upgrade-sets 5.26 5.24

And if you're really lucky, the sets it generates will work the first time :)

( I actually tested this scenario when developing it, but its still an
undocumented use on purpose )

GLHF.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-10 12:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  5:44 [gentoo-user] preparing for profile switch -- major problem John Covici
2017-12-07 12:42 ` Michael Orlitzky
2017-12-07 14:04   ` John Covici
2017-12-07 18:22     ` Michael Orlitzky
2017-12-07 14:37 ` Alan McKinnon
2017-12-07 15:46   ` John Covici
2017-12-08 16:42     ` Alan McKinnon
2017-12-08 19:12       ` John Covici
2017-12-09  8:51         ` Alan McKinnon
2017-12-09 11:23           ` John Covici
2017-12-09 15:28             ` Daniel Frey
2017-12-09 16:18               ` John Covici
2017-12-09 23:20                 ` Daniel Frey
2017-12-09 23:30                   ` Peter Humphrey
2017-12-10  7:17                   ` John Covici
2017-12-10 12:36                     ` Kent Fredric [this message]
2017-12-10 12:54                       ` John Covici
2017-12-10 13:13                         ` Alan McKinnon
2017-12-10 15:16                           ` John Covici
2017-12-10 14:52                         ` Kent Fredric
2017-12-10 16:51                       ` John Covici
2017-12-13 10:58                       ` Marc Joliet
2017-12-09 16:30               ` 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=20171211013619.1fba2e7b@katipo2.lan \
    --to=kentnl@gentoo.org \
    --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