Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 130221 - [EASYFIX] [PATCH] bind-devel should require epoch:version if epoch is set
[EASYFIX] [PATCH] bind-devel should require epoch:version if epoch is set
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jason Vas Dias
Ben Levenson
: EasyFix, Patch
Depends On:
  Show dependency treegraph
Reported: 2004-08-18 05:13 EDT by Nils Philippsen
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version: bind-9.2.4rc6-FC2-7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-18 12:00:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:567 normal SHIPPED_LIVE Updated bind packages 2004-12-21 00:00:00 EST

  None (edit)
Description Nils Philippsen 2004-08-18 05:13:39 EDT
Description of problem:

bind-devel requires "bind = 9.2.4rc6", but bind only provides "bind =
2:9.2.4rc6-FC2_6", thus bind, bind-devel can't be upgraded without

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Try to upgrade bind, bind-devel
Actual results:

Dependeny problem

Expected results:

Installs flawlessly

Additional info:

Just use "Requires: %{name} = %{?epoch:%{epoch}:}%{version}" or
"Requires %{name} = %{?epoch:%{epoch}:}%{version}-%{release}" and it
should work regardless of whether Epoch is set or not.
Comment 1 Jason Vas Dias 2004-08-18 12:00:16 EDT
Whoops! Sorry about that. Now fixed & submitted to fc2-updates in
bind-9.2.4rc6-FC2_7 .
Comment 2 John Flanagan 2004-12-21 14:49:58 EST
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 the 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.


Note You need to log in before you can comment on or make changes to this bug.