I went through the installer and painstakingly selected the packages and use flags that I wanted for a new install. GLI gave me an error message "Your install has failed" and pointed to the file "/tmp/installer.log.failed" for answers (this file didn't exist, but the error was in "/tmp/compile_output.log.failed"). So I've got a circular dependency which would also happen if I was installing from the command line, but now I'd love to click the "Previous" button on the installer so I can alter the USE flags that caused this and rerun the install. Reproducible: Always Steps to Reproduce: I'm not on the computer being installed, so I can't clip the error (would it be relevant anyway?). This might be considered an enhancement, but the installer also won't restart from where it left off (so my previously selected installation parameters will be overwritten when it reemerges the stage3 packages.
Presumably the installer is only running emerge, so you could open a terminal to run 'emerge --resume' to pick up where the installer died.
Created attachment 162346 [details] emerge xorg-x11 && cat /etc/make.conf this demonstrates the problem
I have the same problem, but not within the "installer". Ive installed my core system succesfully (with the help of Gentoo handbook). Then Ive followed the steps in official guide (http://www.gentoo.org/doc/en/xorg-config.xml) to install xorg-x11, but with the error (see attachement). Ive also run "emerge --sync" before and my gentoo version is 2008.1 (not shown above). Thank you for help
try this: #USE="-fam" emerge -av xorg-x11
Created attachment 165495 [details] emerge --info and emerge xorg-x11 output I also encountered this problem. As suggested I temporarily disabled fam in the USE variable and it installed without a hitch. I've attached my own "emerge --info" and "emerge xorg-x11" output.
RE: try this: #USE="-fam" emerge -av xorg-x11 Thanx, it works now, but I did also emerge --update --deep --newuse world before with "-fam" in make.conf so I dont know which one of this steps really helped me. Anyway, does somebody know where exactly is the problem located?
I had the same problem. see bug 217861 for an explanation
The installer is deprecated.