| 1 |
On Mon, 13 Jul 2015 05:19:46 -0700, walt wrote: |
| 2 |
|
| 3 |
> Today's update started as a disaster: perl wants to upgrade from |
| 4 |
> 5.20.2 to 5.22.0, but all of my existing perl modules insist on having |
| 5 |
> 5.20.2 so the perl update blocks and then emerge stopped with an error |
| 6 |
> and left the whole mess for me to solve. (To me this appears to be a |
| 7 |
> bug in the perl family of ebuilds.) |
| 8 |
|
| 9 |
I've upgraded 4 machines so far and all of them handled it perfectly, |
| 10 |
updating Perl and then installing or reinstalling the modules. |
| 11 |
|
| 12 |
"emerge --update --deep --changed-use --ask -v --with-bdeps y --keep-going |
| 13 |
@system @world" reported |
| 14 |
|
| 15 |
Total: 190 packages (49 upgrades, 141 reinstalls, 3 |
| 16 |
uninstalls), Size of downloads: 6,246 KiB Conflict: 3 blocks |
| 17 |
|
| 18 |
The three blocks were handled automatically by portage. |
| 19 |
|
| 20 |
Which version of portage are you using? |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Neil Bothwick |
| 25 |
|
| 26 |
Smoking Can Damage Your Health....Unless us Non-Smokers do it first! |
Archives