Using the 14 Aug installer snapshot, I received the following error after emerging dhcpcd. However, the installer manages to continue and emerge lilo. ---------- >>> emerge (1 of 1) net-misc/dhcpcd-1.3.22_p4-r11 to / >>> extracting info >>> extracting dhcpcd-1.3.22_p4-r11 >>> Merging net-misc/dhcpcd-1.3.22_p4-r11 to / --- /usr/ --- /usr/share/ --- /usr/share/man/ --- /usr/share/man/man8/ >>> /usr/share/man/man8/dhcpcd.8.gz --- /usr/share/doc/ >>> /usr/share/doc/dhcpcd-1.3.22_p4-r11/ >>> /usr/share/doc/dhcpcd-1.3.22_p4-r11/README.gz >>> /usr/share/doc/dhcpcd-1.3.22_p4-r11/ChangeLog.gz >>> /usr/share/doc/dhcpcd-1.3.22_p4-r11/NEWS.gz >>> /usr/share/doc/dhcpcd-1.3.22_p4-r11/AUTHORS.gz --- /sbin/ >>> /sbin/dhcpcd >>> net-misc/dhcpcd-1.3.22_p4-r11 merged. >>> Recording net-misc/dhcpcd in "world" favorites file... >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. Exception received: iteration over non-sequence Please submit a bug report (after searching to make sure it's not a known issue and verifying you didn't do something stupid) with the contents of /var/log/install.log and /tmp/installprofile.xml Calculating dependencies [32;01m*[0m Checking for LILO ... No [32;01m*[0m Issue 'dolilo' instead of 'lilo' to have a friendly wrapper that [32;01m*[0m handles mounting and unmounting /boot for you. It can do more then [32;01m*[0m that when asked, edit /etc/conf.d/dolilo to harness it's full potential. >>> Regenerating /etc/ld.so.cache... ...done! >>> emerge (1 of 1) sys-boot/lilo-22.7 to / >>> extracting info >>> extracting lilo-22.7 >>> Merging sys-boot/lilo-22.7 to / --- /usr/ --- /usr/local/ --- /usr/local/share/ --- /usr/local/share/man/ >>> /usr/local/share/man/man8/ >>> /usr/local/share/man/man8/lilo.8 >>> /usr/local/share/man/man8/mkrescue.8 >>> /usr/local/share/man/man5/ >>> /usr/local/share/man/man5/lilo.conf.5 --- /usr/share/ --- /usr/share/man/ --- /usr/share/man/man8/ >>> /usr/share/man/man8/lilo.8.gz >>> /usr/share/man/man8/mkrescue.8.gz --- /usr/share/man/man5/ >>> /usr/share/man/man5/lilo.conf.5.gz --- /usr/share/doc/ >>> /usr/share/doc/lilo-22.7/ >>> /usr/share/doc/lilo-22.7/README.gz >>> /usr/share/doc/lilo-22.7/README.raid1.gz >>> /usr/share/doc/lilo-22.7/COPYING.gz >>> /usr/share/doc/lilo-22.7/README.bitmaps.gz >>> /usr/share/doc/lilo-22.7/INCOMPAT.gz >>> /usr/share/doc/lilo-22.7/CHANGES.gz >>> /usr/share/doc/lilo-22.7/README.volumeID.gz >>> /usr/share/doc/lilo-22.7/samples/ >>> /usr/share/doc/lilo-22.7/samples/ins64a.bmp.gz >>> /usr/share/doc/lilo-22.7/samples/README.gz >>> /usr/share/doc/lilo-22.7/samples/ins64a.dat.gz >>> /usr/share/doc/lilo-22.7/samples/logo64a.bmp.gz >>> /usr/share/doc/lilo-22.7/samples/lilo.sample.conf.gz >>> /usr/share/doc/lilo-22.7/samples/lilo.raid.conf.gz >>> /usr/share/doc/lilo-22.7/samples/logo64a.dat.gz >>> /usr/share/doc/lilo-22.7/samples/blue.bmp.gz >>> /usr/share/doc/lilo-22.7/samples/blue.dat.gz >>> /usr/share/doc/lilo-22.7/README.pseudo.gz >>> /usr/share/doc/lilo-22.7/README.common.problems.gz >>> /usr/share/doc/lilo-22.7/README.disk.gz --- /usr/sbin/ >>> /usr/sbin/keytab-lilo.pl --- /boot/ >>> /boot/.keep --- /sbin/ >>> /sbin/mkrescue >>> /sbin/dolilo >>> /sbin/lilo --- /etc/ --- /etc/conf.d/ >>> /etc/conf.d/dolilo.example >>> /etc/lilo.conf.example >>> sys-boot/lilo-22.7 merged. >>> Recording sys-boot/lilo in "world" favorites file... >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date.
Created attachment 65979 [details] installer.log
Created attachment 65980 [details] installprofile.xml
I guess I missed an instance when I was modifying code when I made the IP->GLISD changes. This should be fixed in cvs. Use the instructions in the FAQ to update to the latest snapshot and test that.
Still not fixed. Using snapshot downloaded 3 hours ago (0730 GMT). Exception occurs at the same place - after emerging dhcpcd and before emerging lilo.
The bug is actually occuring *after* emerging lilo. It just appears to be before due to the way the GTK frontend tails the logfile. I'm going need the installer.log from the latest crash, as I thought I had fixed this.
I found the other place I missed. This should take care of it now. Try the latest snapshot.
Verified fixed! Using 20050816 snapshot. Thanks a million, agaffney! :-D
Moving to Release Media/Installer.
