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