Jump to content
  • 0
tsfoer

Totaly screwed up emerge and system after move to meta-repo

Question

I did not update my system for a long time and also missed the announcement for the meta-repo thing. I decided to update, read a lot of links from the forums etc. and ended up screwing up my build system. (for example this post

)

# epro

=== Enabled Profiles: ===

        arch: base
       build: (not set)
     subarch: (not set)
      flavor: (not set)
     mix-ins: (not set)


=== Python kit: ===

      branch: 3.4-prime
# emerge  -vpuD --newuse @world


!!! /etc/portage/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /var/git/meta-repo/kits/core-kit/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)
# ls -al /etc/portage/make.profile
lrwxrwxrwx 1 root root 62 Aug  7 10:48 /etc/portage/make.profile -> /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu

"epro flavor server" prints out a huge stacktrace.

"emerge --info" does the same:

  File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile
    self._addProfile(parentPath, repositories, known_repos)
  File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile
    self._addProfile(parentPath, repositories, known_repos)
  File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile
    self._addProfile(parentPath, repositories, known_repos)
  File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 227, in _addProfile
    parents = grabfile(parentsFile)
  File "/usr/lib64/python2.7/site-packages/portage/util/__init__.py", line 131, in grabfile
    mylines = grablines(myfilename, recursive, remember_source_file=True)
  File "/usr/lib64/python2.7/site-packages/portage/util/__init__.py", line 574, in grablines
    mode='r', encoding=_encodings['content'], errors='replace') as myfile:
  File "/usr/lib64/python2.7/codecs.py", line 303, in __init__
    IncrementalDecoder.__init__(self, errors)
RuntimeError: maximum recursion depth exceeded while calling a Python object

So basicaly i'm stuck here and don't know how to continue. "ego sync" is working fine, so the meta-repo structure seems to be OK.

Can anyone please help me to get back a working system?

Thank you,

Thomas

 

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Thank you for your help!

The step that fixed my problems was to remove /etc/portage/make.profile and have ego recreate it with "ego sync --config-only" and reset everything with epro

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...