17410 – Updating to RPM-4.2 requires double emerge

Bug 17410 - Updating to RPM-4.2 requires double emerge

Summary: Updating to RPM-4.2 requires double emerge

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Stefan Jones (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-03-12 17:44 UTC by Ilya Volynets
Modified:	2003-04-14 16:24 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ilya Volynets 2003-03-12 17:44:53 UTC

I had rpm-4.0 installed, and did
emerge rpm
resulting binary got inked against rpmdb-4.0.something, and that one was unmerged
after rpm build was done, of course, so resulting rpm binary wasn't runnable.
doing
emerge rpm
again fixed the problem.

Reproducible: Always
Steps to Reproduce:
1. emerge rpm 4.0
2. emerge rpm 4.2

Actual Results:  
rpm is linked against wrong rpmdb, and thus is not usable


Expected Results:  
RPM should have been linked *only* against its own rpmdb

I'm running ltest bersion of gentoo, with mask set to "~x86"

Comment 1 Stefan Jones (RETIRED) gentoo-dev

2003-03-14 06:28:16 UTC

You are not alone, I have seen this problem also.
When I have time I will attempt so check if a newer version fixes this or if I can patch it.

Stefan

Comment 2 Stefan Jones (RETIRED) gentoo-dev

2003-04-14 16:24:56 UTC

Added a patch to fix this libtool fuck up.
See rpm-4.2_pre069

Stefan