From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C2087139083 for ; Sun, 10 Dec 2017 15:16:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 64220E11C8; Sun, 10 Dec 2017 15:16:51 +0000 (UTC) Received: from a2-out-001.smtp25.com (a2-out-001.smtp25.com [50.201.66.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 10946E11B9 for ; Sun, 10 Dec 2017 15:16:50 +0000 (UTC) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id vBAFGnxr025613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 10 Dec 2017 10:16:49 -0500 Received: (from covici@localhost) by ccs.covici.com (8.14.9/8.13.7/Submit) id vBAFGnLv025610; Sun, 10 Dec 2017 10:16:49 -0500 Date: Sun, 10 Dec 2017 10:16:49 -0500 Message-ID: From: John Covici To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] preparing for profile switch -- major problem In-Reply-To: <6f44f83f-af0d-00af-41fc-ae66ee90b714@gmail.com> References: <93fef73e-d48a-36df-465b-e92a62d52ea3@gmail.com> <48cd7f45-26c9-8611-c750-fff5a0c8417c@gmail.com> <20171211013619.1fba2e7b@katipo2.lan> <6f44f83f-af0d-00af-41fc-ae66ee90b714@gmail.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.3 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Organization: Covici Computer Systems Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SpamH-Filter: a2-out-001.smtp25.com-vBAFGnZ1031454 X-SpamH-OriginatingIP: 70.109.53.110 X-Archives-Salt: be0fdc07-1e43-4ffa-83c6-43653b897d9d X-Archives-Hash: 91a6a626c26ceeac20875af4eb902196 On Sun, 10 Dec 2017 08:13:09 -0500, Alan McKinnon wrote: > > On 10/12/2017 14:54, John Covici wrote: > > On Sun, 10 Dec 2017 07:36:19 -0500, > > Kent Fredric wrote: > >> > >> [1 ] > >> On Sun, 10 Dec 2017 02:17:09 -0500 > >> John Covici 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. > > > > I went ahead and did the upgrade which worked, but the emerge from > > perl-cleaner --all did not. I am using ~amd64 and have done so for > > years, so I don't think I need to maks off anything. I seem now to be > > stuck with dev-python/setuptools, so I am now trying to figure out why > > I can't emerge that -- it was triggered by the perl-cleaner --all . > > > > How recent is your tree? > > I had issues with setuptools doing the first run through the 17.0 > upgrade. I never looked into it too closely, I used --keep-going, but > setuptools seemed to think I had a useable python-3.4 > > After the first run through emerge -e world, nuking-python-3.4 and > re-syncing, setuptols worked normally again. > > YMMV of course where you are My tree maybe 30 days old or thereabouts. I could not run the emerge from perl-cleaner because of setup-tools problems. I will see what happens if I run a regular update, but I hate to do that if I am going to do an -e world. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com