[SOLVED] ParseError: Profile contains unsupported EAPI '5':

subdriver · n00b Joined: 23 Mar 2010 Posts: 29

Well I can't find what's wrong now; when I try to emerge portage, I'm getting a message to the effect that no ebuilds satisfy dev-lang/python:3.3; if I do an emerge --search, it finds 3.1 which is what's installed, but nothing newer. I now that 3.1 has been deprecated, but no sure how to update to 3.3 or later.

subdriver · n00b Joined: 23 Mar 2010 Posts: 29

I came to the conclusion that I was never going to be able to emerge Python 3.3, so I downloaded a tarball for 3.3 and built it and copied the ../bin/ files across to the usr/bin directory where the existing Python binaries live. I realised that I need to tell Portage that I'm looking after the Python builds, so I tried adding an appropriate line to the package.provided file:
/usr/bin/python-3.3.0
However, on attempting to emerge portage, it complains about the 'invalid package' name. I've tried various different options, but have yet to work out what it's expecting, the manpage is of little help as it quotes an example but doesn't explain it. Further on in the emerge process, it then complained about there being no ebuilds for python 2.7, so I repeated the entire process for 2.7. I did an eselect python list and it shows the 2 new versions, as well as the old versions which I haven't unmerged (and don't want to until portage is aware that I'm managing the newer versions); I selected 3.3 from the list.
The next attempt at emerge portage then complained about there being no ebuilds for python 2.7!
OK, so I figured out that I don't quote the path to the package, but the package name as it's known by portage, i.e. dev-lang/python-3.3.0; I modified the package.provided file and emerge is now happy with my package.provided file and hasn't complained about python - it's now complaining that it can't find the required bash package! This is starting to remind me of updating my old Ubuntu system with endless dependencies

adamf663 · n00b Joined: 08 Mar 2007 Posts: 11

I tried most everything suggested on this page and couldn't get past the ParseError ... current profile invalid.
Switching profiles only worked when I switched to profile zero.
Then I was able to 'emerge --sync'.
However, I then had a large number of digest SHA256 errors.
The solution was to rename /usr/portage out of the way and do another sync which this time brought everything in.
Selected a valid profile (desktop/kde for me) and was good to go.

gent00-fun · n00b Joined: 05 Nov 2011 Posts: 20

I want update old gentoo. I've maked emerge --sync and want to update portage, but have a problem.

khayyam · Posted: Wed Mar 09, 2016 8:32 pm Post subject:

gent00-fun · n00b Joined: 05 Nov 2011 Posts: 20

Can i revert in some way `emerge --sync` which broke my old profile (/usr/portage/profiles/default/linux/amd64/10.0 disappear) ?
EDIT:
I've found archival portage snapshots here https://dev.gentoo.org/~swift/snapshots/ but don't know which one i had before `emerge --sync`...

EDIT:
Solved it a little.
I have downloaded `portage-20140120.tar.bz2` and replaced portage. I have now my old profile 10.0 and even though my profile is outdated i will stay with it for now.

stolar · Posted: Fri Oct 26, 2018 10:37 am Post subject:

Hi gent00-fun,

After restoring 'the old' portage, but still with the just performed

soporte · n00b Joined: 21 Aug 2019 Posts: 6

none of the suggestions have worked for me, have a new suggestion on this topic

Thank you.

soporte · n00b Joined: 21 Aug 2019 Posts: 6

I have tried to perform the validations that are suggested, but I have not found a solution to this error ...

the folder with the previous version does not appear, as if it had been completely deleted

What else can you do?