Bug 5469

Summary:	stage2 -> stage3: Portage wants to re-merge already installed packages
Product:	Portage Development	Reporter:	Maik Schreiber <blizzy-keyword-gentoo_bugs2.a8a736>
Component:	Unclassified	Assignee:	Gentoo Release Team <releng>
Status:	RESOLVED FIXED
Severity:	normal	CC:	blizzy-keyword-gentoo_bugs2.a8a736, drobbins, vapier
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Maik Schreiber 2002-07-23 13:42:37 UTC

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.

Comment 1 SpanKY gentoo-dev

2002-07-23 22:16:00 UTC

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 ?

Comment 2 Daniel Robbins (RETIRED) gentoo-dev

2002-07-24 19:10:03 UTC

nope.

Comment 3 Daniel Robbins (RETIRED) gentoo-dev

2002-07-24 20:47:28 UTC

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.

Comment 4 Maik Schreiber 2002-07-25 05:13:41 UTC

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.

Comment 5 Daniel Robbins (RETIRED) gentoo-dev

2002-07-25 06:25:23 UTC

OK, problem found and fixed in 2.0.18

Comment 6 Maik Schreiber 2002-09-24 14:12:37 UTC

I've just bootstrapped a new 1.4_rc1 system, and this pops up again with Portage
2.0.37.

Comment 7 SpanKY gentoo-dev

2002-09-24 16:54:34 UTC

see Bug 8128 ...
he said its fixed in 2.0.38

Comment 8 Nicholas Jones (RETIRED) gentoo-dev

2002-10-13 16:52:50 UTC

Blizzy:

Verify this one for me. Was it just the U/N flip flop,
or is it still and issue?

Comment 9 John Davis (zhen) (RETIRED) gentoo-dev

2002-12-19 18:23:20 UTC

assigned/fixed borks the database,changing to resolved:fixed.
//ZhEN