Broken update path of ypbind in FC5
Dmitry Butskoy
buc at odusz.so-cdu.ru
Thu Sep 7 11:55:25 UTC 2006
On 2006.08.07 an update to ypbind for FC5 has appeared: "ypbind-1.19-1".
After that, on 2006.08.21 a new update has been released: "ypbind-1.19-0.2".
Because of "0.2 < 1" in release field, this update takes no effect with
yum-automated updating etc.
Bugzilla ticket for this is #203361
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203361>
It is already third precedent of such issues, see (now closed) #199247
<http://bugzilla.redhat.com/bugzilla/199247> and #199248
<http://bugzilla.redhat.com/bugzilla/199248>
The strange situation for me is that this issue was fixed for "rawhide"
only.
After some amount of persistence just the binary "1.19-0.2" rpm for i386
has been removed (i.e. the update has been cancelled), but "1.19-0.2" is
still present for ppc, x86_64 and SRPMS ...
This situation confuses me a little. My doubts is:
- Is it a right way to do such amount of my activity for this kind of bugs?
- What user should do in such case: just ignore the update or to update
manually (rpm --force) ?
- Why I'm the only man who catch such kinds of bug? Whether other people
see it too, or just think that it is not noteworthy?
- Does anybody use ypbind at all? :) If yes, what version now exactly?
Regards,
Dmitry Butskoy
--------
http://www.fedoraproject.org/wiki/DmitryButskoy
RHCE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20060907/1d32c52e/attachment.htm>
More information about the fedora-devel-list
mailing list