[SOLVED] emerge sync - IndexError: list index out of range

Joseph_sys · Last edited by Joseph_sys on Fri Jun 09, 2006 5:33 pm; edited 1 time in total

On AMD64 I did as usual emerge sync and got this error:

Wilderness Child · Posted: Fri Jun 09, 2006 4:50 pm Post subject:

I just had the very same problem and checked on the forums, but there was no topic yet 10 minutes ago

After some debugging I found out that a file was damaged. Luckily, it contains only 2 characters

Quick fix (no warranty, either implied or bla bla bla...):

Ryoojin83 · n00b Joined: 07 Jan 2006 Posts: 12

I was installing gentoo 2006.0 from minimal install disk on my server at work and I have never seen this error, albeit im kinda new to gentoo... I am running an amd athlon 64 (amd64) install.

"""
Traceback (most recent call last):
File "/usr/bin/emerge", line 10, in ?
import portage
File "/usr/lib/portage/pym/portage.py", line 7187, in ?
settings=config(config_profile_path=PROFILE_PATH,config_incrementals=portage_const.INCREMENTALS)
File "/usr/lib/portage/pym/portage.py", line 946, in __init__
mypath = os.path.normpath(mypath+"///"+grabfile(mypath+"/parent")[0])
IndexError: list index out of range
"""

This error came about when I use emerge --sync (emerge was working previous to that or syslog-ng install and so on)
Any ideas on how to fix this? THanks!

Joseph_sys · Posted: Fri Jun 09, 2006 5:05 pm Post subject:

Erdie · Posted: Fri Jun 09, 2006 5:10 pm Post subject:

I guess the index update was not completed even you apply the suggested fix. How can i update the portage cache without syncing twice? Syncing again overides the bad file again

Update: I found it - "emerge --metadata" does the job

ERdie
_________________
Desktop AMD Ryzen 9 5900X 32GB RAM, Asus GF GTX 1060.
Notebook Tuxedo Pulse 15 Gen1 AMD Ryzen 7 4800H mit Radeon Vega 7
Raspberry Pi 1 + 2 + 3B+ + Zero W

alet_roux · n00b Joined: 12 Oct 2004 Posts: 54

I just had the same problem, but the workaround on this forum solved it for me:

https://forums.gentoo.org/viewtopic-t-469876.html

Wilderness Child · Posted: Fri Jun 09, 2006 5:12 pm Post subject:

Yes, the portage tree is not fixed yet, so it breaks again as soon as you sync. Quoting from above bugreport:

pelut · n00b Joined: 09 Jun 2006 Posts: 11 Location: Barcelona

Hi!

I have the same problem here. I am using amd64 as well. The profiles/default-linux/amd64/parent file was empty, I added .. and the emerge worked again. However I did "emerge --sync" and it went to 134.68.220.97 (hawk.gentoo.org) and, again, the same problem.

Is that a problem of hawk.gentoo.org?

Ryoojin83 · n00b Joined: 07 Jan 2006 Posts: 12

Thank You!!

Searched around and didn't see that, sorry for starting a new thread about it...

P.S. It worked

Erdie · Posted: Fri Jun 09, 2006 5:16 pm Post subject:

@pelut:
After syncing the first time, just use "emerge --metadata" to get an updated cache without syncing again

jipeee - I just became a guru :lol:

_________________
Desktop AMD Ryzen 9 5900X 32GB RAM, Asus GF GTX 1060.
Notebook Tuxedo Pulse 15 Gen1 AMD Ryzen 7 4800H mit Radeon Vega 7
Raspberry Pi 1 + 2 + 3B+ + Zero W

Wilderness Child · Posted: Fri Jun 09, 2006 5:16 pm Post subject:

pelut · n00b Joined: 09 Jun 2006 Posts: 11 Location: Barcelona

I'm doing it right now.

Thanks

Ryoojin83 · n00b Joined: 07 Jan 2006 Posts: 12

hrm, ok, just broke again with a sync, but i guess i just have to reinstall portage... thanks

kiksen · Guru Joined: 24 Jun 2002 Posts: 401 Location: Denmark

emerge --metadata will let you emerge after applying the fix.

interested1 · Tux's lil' helper Joined: 22 Feb 2006 Posts: 129

I executed

peterpower · n00b Joined: 07 Dec 2005 Posts: 37

The same problem here and the solution Wilderness Child fixt it. I'm also on AMD64 (Opteron)...

Joseph_sys · Posted: Fri Jun 09, 2006 5:33 pm Post subject:

So the correct sequece to fix it is:

bakaohki · Posted: Fri Jun 09, 2006 5:41 pm Post subject:

Since I happened to sync at 7pm CEU time, this is not yet fixed, but thanks for the quick solution! Now portage works again.

Enlight · Posted: Sat Jun 10, 2006 12:17 am Post subject:

It really was the bad moment to emerge --sync... and I did it just a this time do rm -fr /usr/portage, fetch last portage snapshot, untar it and then re-emerge --sync (it was fixed 10 minutes after)