The latest FC5 update is "ypbind-1.19-0.2", whereas the previous update was "ypbind-1.19-1" . As Epoch is not set explicitly, it seems that such update cann't take effect under "yum update" ...
Surely "As Epoch is not set explicitly" => "As Epoch is not changed" :)
Epoch for both is 3. Bug 199531 and Bug 202235 give insight on the version control issues. Just using rpm -q, it's not immediately clear if 1.19-1 includes the 1.19-0.2 changes. 1.19-1 was built after 1.19-0.2, but the changelog for 1.19-1 doesn't say anything about the 1.19-0.2 changes.
This has be fixed in later release of ypbind....
That's good, but the plan is to also push the fix to FC5 updates, right?
The reported version (and the actual issue) is "FC5". Still not fixed :( Please, be more attentive, don't hurry up... Reopen.
ping. :|
Well, ypbind-1.19-0.2 has disappeared from updates/5/i386 (but still exist in updates/5/SRPMS ;) ) Does it mean that it was just a typo? And FC5 should continue to use 1.19-1 ? In other words, may I close this bug now?
1.19-0.2 still exist in updates/5/ppc and updates/5/SRPMS ...
It's not really clear why this is closed, since the packager has yet to clarify what the canonical up-to-date version of ypbind for FC5 is...
Well, now all the binary "0.2" packages are removed. Uph-h-h-h... :) If anybody have a time, remove it from updates/SRPMS too.