After having bootstrapped (now in stage 2), "emerge -p system" tells me it wants to install some packages that are already installed (like glibc-2.2.5-r7, but I don't quite remember the exact version number :) However, "emerge -p -u system" leaves those packages out as one would expect for "emerge -p system". All this is with portage-2.0.17.
i thought bootstrap works like this: install the last version of a package known to be 'stable' (thus bootstrap installs sys-libs/glibc-2.2.4) when you goto update the system, it will update glibc to 2.2.5-r7 (which is the latest out in the portage tree) purpose: to get a known stable base before going anywhere else yes ?
nope.
Just to verify -- you started with a stage1 image, bootstrapped, and then did emerge system right? Because if you started with a pre-made stage2 then it could want to upgrade some things for you.
Yes, I've started with stage 1 and bootstrapped. Then when I did "emerge system" it wanted to re-merge already installed packages, like glibc (exactly the same ebuild version number). "emerge -u system" worked like one would expect for "emerge system" in that case.
OK, problem found and fixed in 2.0.18
I've just bootstrapped a new 1.4_rc1 system, and this pops up again with Portage 2.0.37.
see Bug 8128 ... he said its fixed in 2.0.38
Blizzy: Verify this one for me. Was it just the U/N flip flop, or is it still and issue?
assigned/fixed borks the database,changing to resolved:fixed. //ZhEN
