Bug 10578 – Portage fails after emerge rsync -- 1.2 install failure

• Status: RESOLVED FIXED
• Product: Portage Development

[Description GRIMLER Nicolas 2002-11-11 06:08:03 UTC]

After doing an 'emerge rsync' with a Gentoo 1.2 stage1, many errors occured 
when trying to run the bootstrap script

Portage return several errors as:
---- begin ----
Calculating dependencies   !!! Name error in : category or package part missing.
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1220, in ?
    mykey=portage.db[portage.root]["porttree"].dep_bestmatch(mypkg)
  File "/usr/lib/python2.2/site-packages/portage.py", line 2096, in 
dep_bestmatch
    if not self.hasnode(mykey):
  File "/usr/lib/python2.2/site-packages/portage.py", line 1851, in hasnode
    myreskey=self.resolve_key(mykey)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1800, in resolve_key
    self.load(mykey)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1759, in load
    self.populate()
  File "/usr/lib/python2.2/site-packages/portage.py", line 2456, in populate
    self.domask()
  File "/usr/lib/python2.2/site-packages/portage.py", line 2464, in domask
    self.zap(y)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1771, in zap
    mykey=cps[0]+"/"+cps[1]
TypeError: unsubscriptable object
---- end ----

I tried with a stage3 install and if I run 'emerge rsync' the same errors 
occured.

I supposed the Portage version (Portage 1.9.9) packaged in the stage1 or stage3 
is too old but if I want to upgrade it, I need to rsync the new Portage Tree 
and emerge stop running correctly after that!

[Comment 1 Nicholas Jones (RETIRED) 2002-11-12 23:19:42 UTC]

ALL 1.2 INSTALLS MUST USE A RESCUE PORTAGE.
(after emerge rsync)

cd /usr/portage/sys-apps/portage/files
less README.RESCUE

then continue per normal.

[Comment 2 Nicholas Jones (RETIRED) 2002-11-13 20:21:43 UTC]

*** Bug 10026 has been marked as a duplicate of this bug. ***

[Comment 3 SpanKY 2002-11-19 13:47:14 UTC]

how did that work out for you ?

[Comment 4 Arnaud Boudou 2002-11-19 15:53:31 UTC]

Oops, I'm sorry to forget this bug.
I'm tried again the tomorrow (a new emerge rsync), and portage worked great
(still the 1.9.9 version)

I think we could close this bug report

[Comment 5 SpanKY 2002-11-22 15:40:46 UTC]

*** Bug 11103 has been marked as a duplicate of this bug. ***

[Comment 6 Martin Holzer (RETIRED) 2002-11-24 16:42:53 UTC]

maybe this should be documented ?

[Comment 7 SpanKY 2002-11-25 15:20:50 UTC]

*** Bug 11219 has been marked as a duplicate of this bug. ***

[Comment 8 SpanKY 2002-11-26 18:25:51 UTC]

*** Bug 11271 has been marked as a duplicate of this bug. ***

[Comment 9 SpanKY 2002-11-30 13:31:42 UTC]

*** Bug 11380 has been marked as a duplicate of this bug. ***

[Comment 10 Martin Holzer (RETIRED) 2002-12-08 17:15:41 UTC]

yes it works

but this should be fixed in any kind. (portage tree or docu)

[Comment 11 Brad Laue (RETIRED) 2002-12-19 01:41:31 UTC]

Just ran into this tonight, and an untar of the rescue portage did indeed solve
the issue. Can the stage1 tarball be re-rolled with the newer portage? A 1.2a
release perhaps.

Or at least a documentation update explaining that the new portage needs to be
untarred.

Thanks!

[Comment 12 Robert Moss (RETIRED) 2003-11-10 13:07:19 UTC]

Is this blocker bug not a little dead? Seeing as it's now almost a year and
a minor stable revision out of date?

[Comment 13 Andrew Cooks (RETIRED) 2003-11-24 08:13:01 UTC]

This bug died from old age.