Can't emerge system - loops while emerge wget

mahlerrd · n00b Joined: 21 Jun 2002 Posts: 2

Note: I'm not on that system now, so I'm going from memory (though I was careful to note everything as best I could).

I tried my first Gentoo install last night using a stage 1 tarball. I followed the instructions carefully making sure each step worked OK. Apart from the mentioned 'cosmetic' errors for dhcpcd, everything went fine.

Until I got to 'emerge system'. I ran that and it seemed to be working fine (emerging different things, subtly different compiles and files, that kind of stuff, just like when I'm compiling a FreeBSD port). I wandered off. I came back an hour later and watched it compiling for a while. I noticed it seemed to repeat the exact same pattern over and over again. The exact same pattern. It was still doing so 30 minutes later.

I interrupted the process and scrolled back. After trying a few more things I figured out that it seemed to be emerging wget 1.8.2 repeatedly. I tried emerging just misc-net/wget (? right path? It worked, anyway) and it did that for another hour. Exact same steps, exact same process, not seeming to move on to another package. Broke into it, and yes, it was still emerging wget.

I deleted that directory, then did another emerge rsync, then another emerge system (I didn't think it necessary to do the inbetween bootstrap.sh).

It did exactly the same thing.

So, did I just not let it run long enough? (This was on a Athlon 1800+ w/ 256 cas2 memory and a cable modem) Or is there something wrong with that package? I noted an option in emerge that would allow me to just pretend that I've already installed it, but it seemed that wasn't the proper solution because it should be using wget to retrieve packages, shouldn't it? There's no errors in any of the scroll back messages, and it was getting late so I didn't make a signficant effort to find any log files. I can this weekend if someone needs me to.

delta407 · Posted: Fri Jun 21, 2002 2:35 pm Post subject:

Hmmm... when something gives Portage a failure code, it stops. When something gives Portage a success code, it moves on. AFAIK there's nothing that would make Portage rebuild the same package over and over again.

Run an emerge rsync --clean and please post the output of emerge -p system.

Narses · n00b Joined: 21 Jun 2002 Posts: 12

delta407 · Posted: Fri Jun 21, 2002 9:53 pm Post subject:

Well, first off, the future timestamp thing is a result of your system clock. While I doubt it's causing your grief, set your system clock properly.

The wget thing could be just an issue with your wget ebuild. You could mask it so Portage would try to use an earlier version. Try this:

Narses · n00b Joined: 21 Jun 2002 Posts: 12

Thanks for you help! It seems now to be working properly with wget-1.8.1-r1 or something.

Now I know a lot more about emerge, masking, and all that stuff. Portage seems to have the feel of the FreeBSD ports only with version control, which has occasionally created problems for me. I think like portage. I decided to switch from FreeBSD on my desktop system because it's occasionally behind on the hardware front for video cards and other 'cutting edge' stuff (which I update way more often than my wife would like...).

Depending on the outcome of gentoo I may switch on my servers, too.