Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 217546

Summary: The error was: ''ACCEPT_KEYWORDS''
Product: Gentoo Release Media Reporter: bryan <whoami2u22>
Component: InstallerAssignee: Gentoo Linux Installer <gli-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: 2008.0_beta1   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description bryan 2008-04-13 19:10:22 UTC
first bug report; let me know if anything else is needed. thanks.

reproduced three times. used gtk installer.

GLI: April 14 2008 02:55:39 - Gentoo Linux Installer version 0.6.3
GLI: April 14 2008 02:58:25 - Mounted mountpoint: /
GLI: April 14 2008 02:58:25 - Mounted mountpoint: /boot
GLI: April 14 2008 02:58:25 - Mounted mountpoint: /home
GLI: April 14 2008 03:07:02 - Stage3 was generated successfully
GLI: April 14 2008 03:07:03 - Chroot environment ready.
GLI: April 14 2008 03:07:26 - Portage tree install was custom.
GLI: April 14 2008 03:07:29 - Make.conf configured
GLI: April 14 2008 03:08:18 - Root Password set on the new system.
GLI: April 14 2008 03:08:20 - Edited Config file /mnt/gentoo/etc/conf.d/clock
GLI: April 14 2008 03:08:20 - Edited Config file /mnt/gentoo/etc/conf.d/clock
GLI: April 14 2008 03:08:20 - Timezone set.
GLI: April 14 2008 03:08:21 - Starting emerge_kernel, package is livecd-kernel
GLI: April 14 2008 03:08:28 - This is a bad thing. An exception occured outside of the normal install errors. The error was: ''ACCEPT_KEYWORDS''
GLI: April 14 2008 03:08:28 - Traceback (most recent call last):
GLI: April 14 2008 03:08:28 - File "/opt/installer/GLIClientController.py", line 122, in run
    func()
GLI: April 14 2008 03:08:28 - File "/opt/installer/GLIArchitectureTemplate.py", line 685, in emerge_kernel_sources
    arch = portage_info["ACCEPT_KEYWORDS"].split(" ")[0].strip("~")
GLI: April 14 2008 03:08:28 - KeyError: 'ACCEPT_KEYWORDS'
Comment 1 Andrew Gaffney (RETIRED) gentoo-dev 2008-04-13 19:42:48 UTC

*** This bug has been marked as a duplicate of bug 215971 ***