Re: [gentoo-user] preparing for profile switch -- major problem

[John Covici]

On Fri, 08 Dec 2017 11:42:16 -0500,
Alan McKinnon wrote:
>
> On 07/12/2017 17:46, John Covici wrote:
> > On Thu, 07 Dec 2017 09:37:56 -0500,
> > Alan McKinnon wrote:
> >>
> >> On 07/12/2017 07:44, John Covici wrote:
> >>> Hi. In preparing for the profile switch and the emerge -e world, I
> >>> have run into a serious problem with perl.  I think I saw on this list
> >>> where perl 5.26 was going to have problems -- maybe until it is
> >>> stabilized -- but if I mask it off,  I get the following:
> >>
> >> Unmask the latest perl and update world with the old profile
> >>
> >> This will go smoothly as the perl team did an excellent job making sure
> >> everything perl-ish in the tree works in concert with everything else.
> >> However I do recall that trying to do it with a partial world update
> >> didn't work - too many affected packages, so trying just perl + deps did
> >> not work. Rather do a normal world update.
> >>
> >> Once done, then switch your profile to 17.0 and do the giant emerge -e
> >> world that requires.
> >>
> >> tl;dr
> >>
> >> the news message about perl might make you think the sky will fall on
> >> your head and all your kittens will die, this is actually not true.
> >>
> >> The v5.26 updates mostly had to do with perl's search path for perl
> >> modules. Just like how we've frowned on having "." in the shell PATH for
> >> decades, perl now implemented something like that for modules too. The
> >> possible problem anticipated is that modules would now break if a
> >> modules could not find another module it needs. But this really only
> >> applied to modules outside the perl distribution itself. And the Gentoo
> >> perl team dealt with all that already
> >>
> >> It's widely discussed all over the internet in all the usual places, you
> >> are only affected if one of more of these applies:
> >>
> >> - you write perl modules yourself (solution: update your own code)
> >> - you use many ancient cpan modules that no-one touched for yonks
> >> (solution: maybe use currently supported modules instead)
> >> - you heavily rely on a third party perl app that might not have been
> >> updated - musicbrainz and radiator come to mind as examples (solution:
> >> harass your app vendor)
> >>
> >> --
> >> Alan McKinnon
> >> alan.mckinnon@×××××.com
> >>
> >>
> >
> > So, I have already switched to the new profile, should I switch back,
> > do a regular world update, or do the world update with the new profile
> > -- I am compiling gcc as I write, although its not finished yet, I can
> > interrupt it if necessary.
> >
>
>
> No, I don't think you should revert the profile change. I understood
> from your mail than you had not done that yet, and typed accordingly.
>
> I think Michael is on the right track with backtrack - set it to
> something very high like 1000, see if that gets to a solution.


I did switch back, but the only way I could do a "successful" update
was to mask off 5.26 and then it skipped the update and would have
been successful.  If I switch to the new profile, I can do nothing as
far as perl goes.  I will show the output of just trying to emerge
below, it seems there were many many packages still requiring 5.24.
This is with the new profile and backtrack set to 500.

 instances within a single package slot have been pulled
 !!! into the dependency graph, resulting in a slot conflict:

dev-lang/perl:0

  (dev-lang/perl-5.26.1-r1:0/5.26::gentoo, ebuild scheduled for merge)
  pulled in by
      =dev-lang/perl-5.26* required by
  (virtual/perl-ExtUtils-Manifest-1.700.0-r4:0/0::gentoo, installed)
      ^              ^^^^^
	     dev-lang/perl (Argument)
		    (and 13 more with the same problems)

  (dev-lang/perl-5.24.3:0/5.24::gentoo, installed) pulled in by
      =dev-lang/perl-5.24* required by
      (virtual/perl-Term-ANSIColor-4.40.0-r1:0/0::gentoo, installed)
	     ^              ^^^^^
		    dev-lang/perl:0/5.24= required by
      (dev-perl/XML-Twig-3.520.0:0/0::gentoo, installed)
	                  ^^^^^^^^
				       (and 260 more with the same problems)

NOTE: Use the '--verbose-conflicts' option to display parents omitted
above

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.




-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@××××××××××.com