Bug 13655 – "sh grp-install.sh gnome-list.txt" generates an error and aborts

• Status: RESOLVED FIXED
• Product: Gentoo Release Media

[Description Danila 2003-01-10 12:15:23 UTC]

I was following the installation instructions almost step by step, when I came 
across the following bug. When I got to the GRP installation part, I ran the 
following:

sh grp-install.sh gnome-list.txt

But it terminated after installing about 40 out of 87 packages. Then I ran it 
again - it installed 1 package and terminated. I ran it again - 4 packages and 
terminated. (Note - those are approximate numbers, I might have missed a few) 
In the end I just kept rerunning it until it was fully installed. The error I 
got 2 times was this:

!!! doebuild: /usr/portage/app-text/docbook-sgml-dtd/docbook-sgml-dtd-
3.1.ebuild not found.
>>> Updating world
>>> Adding gnome-base/gnome

 *  Binary pkg installation completed

And another time:

>>> Regenerating /etc/ld.so.cache...
>>> gnome-base/gdm-2.4.0.12 merged.
!!! doebuild: /usr/portage/gnome-base/gdm/gdm-2.4.0.12.ebuild not found.
>>> Updating world
>>> gnome-base/gnome exists, skipping

Then next one was: 

!!! doebuild: /usr/portage/media-sound/sox/sox-12.17.3-r2.ebuild not found.
>>> Updating world
>>> gnome-base/gnome exists, skipping

 *  Binary pkg installation completed

I don't remember the others, but it aborted before finishing installation 
multiple times. I did not have this problem with any of the other GRP lists. 
Also - I was able to reproduce this error at least twice since I was 
reinstalling linux again after messing up partitions and got exact same 
problem with gnome list.

Oh, I am using the athlon version of the live cd with stage 3 tarball.

[Comment 1 Bruce A. Locke (RETIRED) 2003-01-11 22:08:57 UTC]

Confirmed here.

rc2 GRP from athlon stage3 tarball on a chroot'd partition.

It happened with all of the GRP batches.  Running the script enough times
eventually merged everything.

[Comment 2 Mark Guertin 2003-01-12 12:47:32 UTC]

This was a portage problem which has been fixed, try upgrading to the latest 
portage and run the grp-install.sh again and let me know if it's ok please 

[Comment 3 Mark Guertin 2003-01-12 16:01:09 UTC]

k, this was a problem with portage (wrongly) trying to reference the actual ebuild 
file. 
 
The portage fix is forthcoming, but 1.4 release will not be using/needing this sript, so 
going to close this bug as wontfix. 
 
Thanks though :)