| 1 |
On 13/07/2015 14:58, Neil Bothwick wrote: |
| 2 |
> On Mon, 13 Jul 2015 05:19:46 -0700, walt wrote: |
| 3 |
> |
| 4 |
>> Today's update started as a disaster: perl wants to upgrade from |
| 5 |
>> 5.20.2 to 5.22.0, but all of my existing perl modules insist on having |
| 6 |
>> 5.20.2 so the perl update blocks and then emerge stopped with an error |
| 7 |
>> and left the whole mess for me to solve. (To me this appears to be a |
| 8 |
>> bug in the perl family of ebuilds.) |
| 9 |
> |
| 10 |
> I've upgraded 4 machines so far and all of them handled it perfectly, |
| 11 |
> updating Perl and then installing or reinstalling the modules. |
| 12 |
> |
| 13 |
> "emerge --update --deep --changed-use --ask -v --with-bdeps y --keep-going |
| 14 |
> @system @world" reported |
| 15 |
> |
| 16 |
> Total: 190 packages (49 upgrades, 141 reinstalls, 3 |
| 17 |
> uninstalls), Size of downloads: 6,246 KiB Conflict: 3 blocks |
| 18 |
> |
| 19 |
> The three blocks were handled automatically by portage. |
| 20 |
> |
| 21 |
> Which version of portage are you using? |
| 22 |
|
| 23 |
|
| 24 |
Same here, a mostly problem-free upgrade with portage-2.2.20. |
| 25 |
There was one file collision with perl-code/Encode, easily fixed rm |
| 26 |
|
| 27 |
I'm also busy with a new install while all this is going on, and that |
| 28 |
machine have some initial issues - something blocking perl-5.22.0 - |
| 29 |
which has now gone away and I don't know what I did to make that happen |
| 30 |
:-) IIRC I manually upgraded portage to latest ~ (but a lot wqas going |
| 31 |
on so can't be totally sure) |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Alan McKinnon |
| 36 |
alan.mckinnon@×××××.com |
Archives