Am Thu, 20 Apr 2017 05:05:25 +0800 schrieb Bill Kenworthy <bi...@iinet.net.au>:
> On 20/04/17 04:54, Grant Edwards wrote: > > I did my normal (approximately) weekly emerge sync/update today, and > > the update failed: emerge complained about a conflict between perl > > 5.22 and 5.24. There were a bunch of perl modules that required > > 5.22, but others required 5.24. > > > > After a bit of messing around, I just uninstalled all the ones that > > required 5.22 (and then uninstalled whatever apps required those > > modules). This took numerous iterations of 'emerge --pretend > > --depclean' and 'emerge -C <something>' and 'emerge -auvND'. After > > 10-15 minutes of this, the update ran without conflict, and then I > > reinstalled whatever apps I had uninstalled. > > > > Now update the next machine... same conflicts. > > > > This time I paid closer attention to the emerge output and added > > '--backtrack=30' as it suggested. Then the update worked ran no > > problem. > > > > simpler is to: > emerge perl --nodeps > perl-cleaner --all > emerge -NuDv world etc ... > > less work, no glitches ... I have just started machine #4 Well, you are lucky that no glitches appeared... No deps ignores all deps, perl may not properly work. At least I would rebuild perl again after everything was resolved. Or you use: # emerge -1a perl --reinstall-atoms "$(qlist -IC dev-perl/ virtual/perl-)" It may require you to first uninstall all virtuals: # emerge -Ca $(qlist -IC virtual/perl-) Also, "qlist -ICS ..." may be required instead. -- Regards, Kai Replies to list-only preferred.
