| 1 |
Am Thu, 20 Apr 2017 05:05:25 +0800 |
| 2 |
schrieb Bill Kenworthy <billk@×××××××××.au>: |
| 3 |
|
| 4 |
> On 20/04/17 04:54, Grant Edwards wrote: |
| 5 |
> > I did my normal (approximately) weekly emerge sync/update today, and |
| 6 |
> > the update failed: emerge complained about a conflict between perl |
| 7 |
> > 5.22 and 5.24. There were a bunch of perl modules that required |
| 8 |
> > 5.22, but others required 5.24. |
| 9 |
> > |
| 10 |
> > After a bit of messing around, I just uninstalled all the ones that |
| 11 |
> > required 5.22 (and then uninstalled whatever apps required those |
| 12 |
> > modules). This took numerous iterations of 'emerge --pretend |
| 13 |
> > --depclean' and 'emerge -C <something>' and 'emerge -auvND'. After |
| 14 |
> > 10-15 minutes of this, the update ran without conflict, and then I |
| 15 |
> > reinstalled whatever apps I had uninstalled. |
| 16 |
> > |
| 17 |
> > Now update the next machine... same conflicts. |
| 18 |
> > |
| 19 |
> > This time I paid closer attention to the emerge output and added |
| 20 |
> > '--backtrack=30' as it suggested. Then the update worked ran no |
| 21 |
> > problem. |
| 22 |
> > |
| 23 |
> |
| 24 |
> simpler is to: |
| 25 |
> emerge perl --nodeps |
| 26 |
> perl-cleaner --all |
| 27 |
> emerge -NuDv world etc ... |
| 28 |
> |
| 29 |
> less work, no glitches ... I have just started machine #4 |
| 30 |
|
| 31 |
Well, you are lucky that no glitches appeared... No deps ignores all |
| 32 |
deps, perl may not properly work. At least I would rebuild perl again |
| 33 |
after everything was resolved. |
| 34 |
|
| 35 |
Or you use: |
| 36 |
|
| 37 |
# emerge -1a perl --reinstall-atoms "$(qlist -IC dev-perl/ virtual/perl-)" |
| 38 |
|
| 39 |
It may require you to first uninstall all virtuals: |
| 40 |
|
| 41 |
# emerge -Ca $(qlist -IC virtual/perl-) |
| 42 |
|
| 43 |
Also, "qlist -ICS ..." may be required instead. |
| 44 |
|
| 45 |
-- |
| 46 |
Regards, |
| 47 |
Kai |
| 48 |
|
| 49 |
Replies to list-only preferred. |
Archives