Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Cc: gentoo-user@l.g.o
Subject: [gentoo-dev] emerge -e question Was: GCC-3.4 will be marked stable in ~1 hour on x86
Date: Sat, 03 Dec 2005 12:53:05
In Reply to: [gentoo-dev] GCC-3.4 will be marked stable in ~1 hour on x86 by Mark Loeser
1 Mark Loeser posted <20051202215523.GA25803@×××××××××××××.com>, excerpted
2 below, on Fri, 02 Dec 2005 16:55:23 -0500:
4 > [1]
6 Reading this reminds me of a question I've had since I tried emerge -eav
7 world last time:
9 When portage merges, it stops the emerge process, updates its metadata or
10 whatever, then restarts the process. With the -e in there, at least here,
11 it reissued the same command over again, thereby restarting the process
12 from the beginning and of course, upon getting to portage, looping yet
13 again!
15 I don't know how many times it looped before I decided to check on things
16 and figured out what was happening, at which point I was able to do an
17 emerge -pe and get a listing, then delete <=portage from the list and just
18 remerge what came after.
20 I've yet to see anyone else mention this, and certainly the document above
21 doesn't mention it as an issue when invoking emerge -e world, so that
22 reasonably means I experienced the loop when others don't. Why might this
23 be (I know the reason for portage stopping and recalculating, but why is
24 it apparently not hitting others), and what can I do to prevent it the
25 next time I do an emerge -e world?
27 Maybe it was because I was using -KuD also, to remerge/upgrade from binary
28 packages? (Hard disk trouble, I was remerging the binary packages to
29 bring up2date an old installation snapshot.)
31 --
32 Duncan - List replies preferred. No HTML msgs.
33 "Every nonfree program has a lord, a master --
34 and if you use the program, he is your master." Richard Stallman in
38 --
39 gentoo-dev@g.o mailing list