Bug 48681 – rpm-4.0.3-0.55 -> 4.0.3-0.60 upgrade screws things up

Bug 48681 - rpm-4.0.3-0.55 -> 4.0.3-0.60 upgrade screws things up

Summary:	rpm-4.0.3-0.55 -> 4.0.3-0.60 upgrade screws things up

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	rpm (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-07-11 03:39 EDT by Jonathan Kamens
Modified:	2007-04-18 12:34 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-07-11 03:39:31 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Jonathan Kamens 2001-07-11 03:39:28 EDT

I had rpm-4.0.3-0.55 installed on my machine.  I "upgraded" to
rpm-4.0.3-0.60.  Simple queries like "rpm -q -i" and "rpm -q --scripts"
stopped working.  Furthermore, when I attempted to use "rpm -U --force" to
reinstall the old rpm and rpm-build packages, it complained that only one
major mode could be specified at a time.

I finally had to (a) use rpm2cpio and cpio --extract to put back the files
from the old version of rpm, (b) remove /etc/rpm/macros.db1, (c) restore my
rpm database from a backup, and (d) rerun rpm -U on the packages I had
installed along with rpm-4.0.3-0.60 to bring the database up-to-date.

There is something wrong here.

Comment 1 Jeff Johnson 2001-07-11 07:54:09 EDT

Yes, the top level main() routine changed between -0.57 and -0.66
builds. You want rpm-4.0.3-0.66.

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