Bug 70611 - Aggrivating version numbers
Summary: Aggrivating version numbers
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: glibc   
(Show other bugs)
Version: limbo
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-02 20:50 UTC by Valdis Kletnieks
Modified: 2016-11-24 14:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-08-02 20:51:02 UTC
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.)

Description Valdis Kletnieks 2002-08-02 20:50:58 UTC 
Description of Problem:
Problematic RPM numbers for 'rpm -F'

Version-Release number of selected component (if applicable):
glibc-2.2.90-17.i686.rpm

How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:
Whenever glibc-2.2.6 comes out, 'rpm -F' will refuse to install it because .90
is bigger than .6

Expected Results:


Additional Information:
I've gotten bit by this on RawHide before - something will use 2.8.3, then
2.8.94, then when 2.8.4 comes out you have a headache in upgrading.  Wouldn't
'glib-2.2.5-90.17' have worked just as well?
Comment 1 Jeremy Katz 2002-08-03 20:35:35 UTC 
glibc 2.2.90 is CVS glibc 2.3, so it is newer than glibc 2.2.6
Note You need to log in before you can comment on or make changes to this bug.