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.
autoconf-2.52g-1 fixes this.
oops, forgot that autoconf-2.52g requires automake-1.5b. This will have to wait a little more. :(
really fixed in 2.52-7 (reverted to 2.52 release).