Bug 151361 – EmergePackageError ... Could not emerge 'unknown'

• Product: Gentoo Release Media
• Status: RESOLVED CANTFIX

[Description David Relson 2006-10-14 10:05:31 UTC]

LiveCD 2006.1 failed with "EmergePackageError"

environment:  
  graphical installer
  separate partitions for boot, root, and home
  static ip address
  create 1 user
  

Will add files 'installprofile.xml' and 'installer.log.failed' shortly.

[Comment 1 David Relson 2006-10-14 10:06:48 UTC]

Created attachment 99663 [details]
install profile

[Comment 2 David Relson 2006-10-14 10:07:15 UTC]

Created attachment 99664 [details]
installer log

[Comment 3 Andrew Gaffney (RETIRED) 2006-10-14 10:21:18 UTC]

What is the filename and MD5sum of the CD you are using? This doesn't look like an official release. There is nothing in the official code that generates the error "Could not emerge 'unknown': I need something more specific.". Are you using lxnay's RR4 LiveCD?

[Comment 4 David Relson 2006-10-15 06:00:11 UTC]

Lines 265 and 270 of /opt/installer/GLIPortage.py are:					raise GLIException("EmergePackageError", "fatal", "emerge", "Could not emerge " + pkg + "!")

When pkg has value 'unknown', this would generate the message I reported, would it not?

Using links from the gentoo.org site I downloaded the 2006.1 livecd .iso and .DIGESTS files.  Here are their sizes/timestamps:

bash-3.00# ls -l
... 715732992 Sep 24 08:53 livecd-i686-installer-2006.1.iso
...       165 Sep 24 12:52 livecd-i686-installer-2006.1.iso.DIGESTS

### here's the DIGESTS file ###
bash-3.00# cat livecd-i686-installer-2006.1.iso.DIGESTS
# MD5 HASH
f46c9bcadea4944396f6ecdd7dbf283c  livecd-i686-installer-2006.1.iso
# SHA1 HASH
18cb21944055c6e52e1e7fbe6e8ebe6226396dc9  livecd-i686-installer-2006.1.iso

### here're the md5sum and sha1sum verifications ###
bash-3.00# md5sum -c livecd-i686-installer-2006.1.iso.DIGESTS
livecd-i686-installer-2006.1.iso: OK
bash-3.00# sha1sum -c livecd-i686-installer-2006.1.iso.DIGESTS
livecd-i686-installer-2006.1.iso: OK

[Comment 5 Andrew Gaffney (RETIRED) 2006-10-15 09:41:45 UTC]

(In reply to comment #4)
> Lines 265 and 270 of /opt/installer/GLIPortage.py are:                         
>         raise GLIException("EmergePackageError", "fatal", "emerge", "Could not
> emerge " + pkg + "!")
> 
> When pkg has value 'unknown', this would generate the message I reported, would
> it not?

If 'pkg' had the value "'unknown': I need something more specific.", then it would generate the message you got. There is nothing in the code that would pass that value for pkg. Nor is that value in your installprofile.xml. The value also is not coming from the portage output. If you're not using RR4 and you can figure out where that value is coming from, then I can do something.

[Comment 6 David Relson 2006-10-15 11:21:11 UTC]

Since the message is produced as the installer throws an exception and dies, it's a challenge to get further info.

Given a copy of the installer modified to start pydb when its ready to throw the exception, it'd be possible to learn more.  Is there a HOWTO on installing the livecd to a hard drive, and running from there?

[Comment 7 Andrew Gaffney (RETIRED) 2006-12-16 19:38:36 UTC]

No info indicating cause of bug, and doesn't seem like it's the installer's fault.