Bug 32317 - Strange versioning of rpm package
Summary: Strange versioning of rpm package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pan
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Powers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-19 22:07 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-19 22:08:01 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-03-19 22:07:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.1-0.1.9 i686; en-US; 0.7)
Gecko/20010227


There seems to be something strange about the rpm package of pan in
Wolverine. When I try to upgrade to the more recent 0.9.5, I get the following:

$ rpm -Uvh pan-0.9.5-1.i686.rpm
package pan-0.9.1-3 (which is newer than pan-0.9.5-1) is already installed

So, rpm seems to think 0.9.1-3 is more recent than 0.9.5-1.


Reproducible: Always
Steps to Reproduce:
1.download most recent version from pan.rebelbase.com
2.attempt to upgrade


Actual Results:  rpm refuses to upgrade the package without '--force'

Expected Results:  rpm should have allowed to upgrade the package.

Comment 1 Tim Powers 2001-03-19 22:49:27 UTC
I don't think that the pan package you already have installed was packaged by us
here at Red Hat. The version shipped in Wolverine was 0.9.1-2.

Do this:

rpm -e pan

rpm -ivh pan-0.9.5-1.i386.rpm

Or do this:

rpm -Uvh --force pan-0.9.5-1.i386.rpm

I am resolving this as "notabug" since this doesn't appear to be one of our
packages, and I can't do anything about packages installed on the system not
maintained by us.

FWIW - Chances are that the epoch in the package you installed is  greter than
1, which indicates that it didn't come from us (since our epoch has hasn't
changed from 1 since it was a Powertools package).

Tim




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