Bug 58210

Summary: Please use correct version label
Product: [Retired] Red Hat Raw Hide Reporter: Enrico Scholz <rh-bugzilla>
Component: autoconfAssignee: Jens Petersen <petersen>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-02-01 09:04:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Enrico Scholz 2002-01-11 01:24:14 UTC 
Description of Problem:

autoconf-2.52-5 contains autoconf-2.52f in reality; old ...-2.52-4 was -2.52d.
This relabeling is very confusing...

I don't see a reason why this packages can not be named as 'autoconf-2.52f-1' or
so. RPM works fine and can distinguish between this versions correctly:

----
$ python
>>> import rpm
>>> rpm.labelCompare(['0','2.52','1'], ['0','2.52d','1'])
-1
>>> rpm.labelCompare(['0','2.52d','1'], ['0','2.52','1'])
1
>>> rpm.labelCompare(['0','2.52d','1'], ['0','2.52f','1'])
-1
>>> rpm.labelCompare(['0','2.52f','1'], ['0','2.52d','1'])
1
----

Therefore, rpm would see the packages in order of

| autoconf-2.52-1 < autoconf-2.52d-1 < autoconf-2.52f-1

and upgrading will work without '--force' or so.
Comment 1 Jens Petersen 2002-02-01 08:25:00 UTC 
autoconf-2.52g-1 fixes this.
Comment 2 Jens Petersen 2002-02-01 09:04:07 UTC 
oops, forgot that autoconf-2.52g requires automake-1.5b.
This will have to wait a little more. :(
Comment 3 Jens Petersen 2002-02-04 04:55:14 UTC 
really fixed in 2.52-7 (reverted to 2.52 release).