Epoch handling seems to be different in yum 1.0 and 1.95, and I think
1.0 should be fixed. Here's the scenario from a recent JPackage
(www.jpackage.org) RPM. Yes, it's kinda packaging bug, but I think yum
1.0 should have handled it, 1.95 did ok.
jakarta-commons-logging = 0:1.0.2-3jpp
jakarta-commons-logging = (none):1.0.3-1jpp
ie. the Epoch was accidentally dropped from 1.0.3-1jpp. Now when I have
1.0.2-3jpp installed, both yum 1.0 and 1.95 list the epochless
1.0.3-1jpp in check-update. 1.95 does the right thing, it actually
installs it with update or install, but 1.0 doesn't, it says:
Errors installing:
('package jakarta-commons-logging-1.0.2-3jpp (which is newer than jakarta-commons-logging-1.0.3-1jpp) is already installed', (8, None, 0L))
So 1.0 seems to think no-epoch < 0, which I think should be fixed to
no-epoch == 0.
--
\/ille Skyttä
ville.skytta at iki.fi
