After selecting 'None' as sync method for the tree and the installer unpacking the stage tarball the 'next' and 'previous' buttons don't do anything anymore, and there doesn't seem to be any activity either (no cpu or IO activity, and no child processes after gtkfe.py). The 'exit' and 'view log' buttons still work though, so I guess it's a logic bug there.
Created attachment 118963 [details] Installer logfiles
that log shows two attempted installs. the second one failed because the installer did not clean up after the first failed attempt (you must have killed the installer rather than exiting). Can you provide a bit more detail as to what your settings were up until you chose None for portage sync? (we don't see many cases of netmounted portage).
Ok, here it is (started from scratch and wiped /dev/sda1 before starting the installer): - install mode: advanced - partitioning: skipped - local mounts: Device Type Mount point Mount options /dev/sda1 ext3 / noatime /dev/hda1 ext2 /boot noauto,noatime /dev/sda2 swap - - - network mounts: Type Host Export/Share Mount point Mount options NFS nfs.. /srv/portage/porttree /srv/portage/porttree ro,async NFS nfs.. /srv/portage/distfiles /srv/portage/distfiles rw,async - manually starting nfsmount (otherwise the install fails at this point) - stage selection: fetching http://gentoo.osuosl.org/releases/amd64/2007.0/stages/stage3-amd64-2007.0.tar.bz2 - portage tree: none - (fetching+unpacking stage tarball) - (syncing portage tree) And there it stops working as described in comment #0
Created attachment 119057 [details] Installer logfile from clean install attempt
Ok, after taking a look at the code the problem is obvious: fe.gtk.MakeDotConf.__init__ has hardcoded references to /usr/portage (which isn't populated in my setup) and when it tries to open use.desc there an exception is thrown but silently swallowed somewhere. Note that the dialog installer doesn't have this problem, probably because it doesn't have such a "user friendly" screen layout for dealing with make.conf.
Starting with 2007.1, the installer will be for networkless installs only, which makes this bug moot.
