11826 – emerge blackdown-jdk produces IndexError: string index out of range

Bug 11826 - emerge blackdown-jdk produces IndexError: string index out of range

Summary: emerge blackdown-jdk produces IndexError: string index out of range

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Todd Berman (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-12-09 03:21 UTC by lasse
Modified:	2011-10-30 22:22 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description lasse 2002-12-09 03:21:20 UTC

I try to merge openoffice. 

gentoo root # emerge openoffice
Calculating dependencies ...done!
>>> emerge (1 of 2) dev-java/blackdown-jdk-1.3.1-r7 to /
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1653, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 1045, in merge
    retval=portage.doebuild(y,"merge",myroot,edebug)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1195, in doebuild
    newuris=flatten(evaluate(tokenize(myuris),string.split(settings["USE"])))	
  File "/usr/lib/python2.2/site-packages/portage.py", line 170, in evaluate
    if cur[0]=="!":
IndexError: string index out of range
gentoo root # 

It get the same error with emerge blackdown-jdk and emerge blackdown-jre.

Comment 1 Joe Kowalski 2002-12-09 11:44:48 UTC

I'm getting this exact same error.  portage-2.0.45-r1, python-2.2.1-r5,
gcc-3.2-r4, glibc-2.2.5-r7.....

Comment 2 lasse 2002-12-09 12:13:17 UTC

I had the same configuration portage-2.0.45-r1, python-2.2.1-r5,
gcc-3.2-r4, glibc-2.2.5-r7.

I just updated to portage-2.0.45-r3, but still get the same error.

Comment 3 Joe Kowalski 2002-12-09 16:32:29 UTC

Was able to successfully install blackdown-jdk-1.3.1-r8.  r7 must be be broken
with the latest portage.

Comment 4 lasse 2002-12-10 01:32:45 UTC

I made an emerge rsync this morning and now i can not reproduce the error.
I am installing blackdown-jdk-1.3.1-r7 right now. ;-)

Comment 5 Eugene Koontz 2002-12-11 03:32:20 UTC

I was able to workaround this bug by replacing :

SRC_URI="x86?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/i386/FCS/j2sdk-1.3.1-FCS-linux-i386.tar.bz2
	ppc?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/ppc/FCS-02b/j2sdk-1.3.1-02b-FCS-linux-ppc.bin
	sparc?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/sparc/FCS-02b/j2sdk-1.3.1-02b-FCS-linux-sparc.bin"

with :

SRC_URI="x86?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/i386/FCS/j2sdk-1.3.1-FCS-linux-i386.tar.bz2"
#	ppc?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/ppc/FCS-02b/j2sdk-1.3.1-02b-FCS-linux-ppc.bin
#	sparc?
ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/sparc/FCS-02b/j2sdk-1.3.1-02b-FCS-linux-sparc.bin"

i.e., it is a bug with tokenizing the SRC_URI variable when there is more than
one architecture.

Comment 6 Todd Berman (RETIRED) gentoo-dev

2003-05-23 14:47:04 UTC

fixed apparently.