From: SourceForge.net <no...@so...> - 2004-04-22 02:33:27
|
Bugs item #939730, was opened at 2004-04-21 20:31 Message generated for change (Comment added) made by brechin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=939730&group_id=9368 Category: Installation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Benoit des Ligneris (bligneri) Assigned to: David N. Lombard (dnl) >Summary: update-rpms /mdk / versioning problem Initial Comment: I have observed some bugs with the numerotation scheme of Mandrake. 1) Parsing : Querying RPMs... libGConf2_4-2.4.0.1-3mdk.i586.rpm Hmmm... libGConf2_4-2.4.0.1-3mdk provides "libGConf2 >= 2.4.0.1-3mdk" Querying RPMs... shadow-utils-4.0.3-7mdk.i586.rpm Hmmm... shadow-utils-4.0.3-7mdk provides "shadow-utils > 20000902-5" Querying RPMs... gaim-0.75-5mdk.i586.rpm Hmmm... gaim-0.75-5mdk provides "hackgaim <= 0.60" 2) Comparison of versions : libutempter0-0.5.2-12mdk libutempter0-0.5.2-12.1.100mdk (older) installed mkinitrd-3.5.18-4mdk mkinitrd-3.5.18-4.1.100mdk (older) installed mount-2.12-2mdk installed tar-1.13.25-11mdk installed utempter-0.5.2-12mdk utempter-0.5.2-12.1.100mdk (older) installed In all the "to update case", update-rpm is wrong and the installed rpms are newer than the one it chooses to update. ---------------------------------------------------------------------- >Comment By: Jason Brechin (brechin) Date: 2004-04-21 21:33 Message: Logged In: YES user_id=274641 So, to clarify, update-rpms is choosing utempter-0.5.2-12.1.100mdk instead of utempter-0.5.2-12mdk? If 12.1.100mdk is truly older than 12mdk, then Mandrake has some issues when it comes to versioning. If update-rpms is thinking the 12.1.100mdk is older and choosing the 12mdk over the 12.1.100mdk, then this is definitely an update-rpms bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=939730&group_id=9368 |