Bug 17083 - RPM upgrade (-F or -U) of nfs-utils fails because a version number is misread
Summary: RPM upgrade (-F or -U) of nfs-utils fails because a version number is misread
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-29 17:45 UTC by jpranevich
Modified: 2008-10-27 18:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-12-19 16:11:52 UTC
Embargoed:

Attachments (Terms of Use)

Description jpranevich 2000-08-29 17:45:58 UTC 
When upgrading from nfs-utils-0.1.2-1 to nfs-utils-0.1.9.1 using rpm -Uivh, rpm reports that 0.1.2-1 is *newer* than 0.1.9.1-1. A similar problem 
is observed when upgrading to nfs-utils-0.1.6-2. I suspect the issue is with the third level minor revision number, but have not checked the 
source for an obvious fix.
Comment 1 Jeff Johnson 2000-10-12 16:12:17 UTC 
This is a nfs-utils packaging problem. Changing component ...
Comment 2 Pete Zaitcev 2002-10-23 20:19:34 UTC 
This is one super ancient bug.

I actually consulted Jeff, and he said it's likely the "Epoch" conflict.
The epoch is not visible in the RPM name, so SRPMs need to be compared.
If so, it's a bug, but since we are shipping 8.0 now, it's not something
I'm eager to investigate in detail.

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