| 1 |
On 08/16/2016 10:58 AM, hw wrote: |
| 2 |
> |
| 3 |
> Three months is not "ridiculously outdated", yet the update doesn´t work. |
| 4 |
> 1.5 years isn´t "ridiculously outdated", either --- maybe a bit old, but |
| 5 |
> what´s the problem? |
| 6 |
> |
| 7 |
>> Of course, you'll have to deal with new/renamed/moved/gone packages |
| 8 |
>> and such stuff, but that's to be expected[3]. |
| 9 |
> |
| 10 |
> Perhaps you can do that when you´re an expert user of the packagage |
| 11 |
> management and have lots of time on your hands. I just need to update. |
| 12 |
> |
| 13 |
|
| 14 |
Since everyone is telling you that three months is too long, I've been |
| 15 |
perfectly happy updating our systems about once every three months. |
| 16 |
|
| 17 |
Here's what happened: you got unlucky. You waited a long time to update, |
| 18 |
and we happened to release a new EAPI right at the beginning of that |
| 19 |
time, and someone didn't notice that they were breaking the portage |
| 20 |
upgrade process a year later when they updated an ebuild to EAPI=6. It |
| 21 |
sucks, but a few people have posted easy solutions. |
| 22 |
|
| 23 |
You're not going to break the system even if you trash portage. Try to |
| 24 |
download a snapshot of portage from git and run that. Once you have a |
| 25 |
portage that works with EAPI=6, all of the other errors get a lot |
| 26 |
simpler. Work your way through the list of packages to be installed |
| 27 |
(say) twenty at a time to keep the output readable. Start with the |
| 28 |
@system stuff, have some coffee on hand, and remember -- you haven't |
| 29 |
been doing anything for a year and a half so you have a lot of time to |
| 30 |
waste before you're in the red =P |
Archives