Red Hat Bugzilla – Bug 604620
Quagga incorrectly obsoletes Bird (and others)
Last modified: 2013-01-08 02:25:33 EST
Description of problem:
The Quagga package incorrectly claims to obsolete Bird (and other routing packages).
Version-Release number of selected component (if applicable):
Name : quagga
Arch : x86_64
Version : 0.98.6
Release : 5.el5_5.1
Size : 1.1 M
Repo : updates
Try to install Bird automagically (as from a kickstart, for example).
From the .spec file for Quagga :
Obsoletes: bird gated mrt zebra
Apparently it was acknowledged and marked to be fixed in Fedora 10.
It's still a problem in CentOS 5.5 .
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
What is the issue with fixing this? It's a simple spec file change with limited consequences.
(In reply to comment #4)
> What is the issue with fixing this? It's a simple spec file change with
> limited consequences.
As was written in the comment #3 - quagga package is not planned to be updated in RHEL-5.6. If the bug is critical for you please do contact our support:
Thanks Jiri, I opened support case #00370582.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.