Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 2RHEL Program Management
2011-03-23 10:08:16 UTC
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. If you would like it considered as an
exception in the current release, please ask your support
representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-1174.html
Description of problem: Doxygen has a BuildRequires on qt-devel >= 4.4 The problem is that qt3-devel has the following: Provides: qt-devel = 1:%{version}-%{release} While qt4-devel provides: qt-devel = %{version}-%{release} Obviously, 1:whatever is always > (none):4.4, which causes yum-builddep to be wrong about the dependency to download for building doxygen. It has been discussed in Fedora and fixed already: - qt3 dropped its provide on qt-devel [1] - packages with BuildRequires on qt-devel have been fixed to explicitly require either qt3-devel or qt4-devel [2][3] Could this be fixed in RHEL like it was done in Fedora? Version-Release number of selected component (if applicable): doxygen-1.6.1-4.el6 Additional infos: This effectively makes doxygen unbuildable in mock. [1] https://bugzilla.redhat.com/show_bug.cgi?id=623106 [2] https://bugzilla.redhat.com/show_bug.cgi?id=651064 [3] http://pkgs.fedoraproject.org/gitweb/?p=doxygen.git;a=blobdiff;f=doxygen.spec;h=1797a0e447aa89eba064c7a3321332db258c8b3e;hp=36014ab7ce7d3afe27a69f9fdea068507718f3fa;hb=a491e5086492372df111b632152fab65d2a734bd;hpb=73fb3fe0fb44b00dde0995dcdd2d97d8742c3ac4