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 144910 - DHCP package is removed from RHEL3 WS
DHCP package is removed from RHEL3 WS
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: dhcp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Depends On:
  Show dependency treegraph
Reported: 2005-01-12 12:21 EST by Michele Codutti
Modified: 2007-11-30 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-13 18:07:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michele Codutti 2005-01-12 12:21:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.4.3)

Description of problem:
Upgrading a RHEL3 from WS U3 to U4 the package dhcp is not updated to
release dhcp-3.0.1-10_EL3 and from the new set of packages of U4
doesn't contain dhcp.

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

How reproducible:

Steps to Reproduce:
1. up2date -u 
2. see the system update all packages but dhcp
1. Perform a fresh installation and search for dhcp

Actual Results:  DHCP doesn't update or install

Expected Results:  DHCP update or install to version 3.0.1-10_EL3

Additional info:
Comment 1 Jason Vas Dias 2005-01-12 12:41:35 EST
Very sorry for this mistake in our package distribution policy. 
We'll try to get DHCP put back into RHEL-3-WS . Meanwhile, you
can download DHCP-3.0.1-10_EL3 from:
Comment 3 Jason Vas Dias 2005-01-13 18:07:56 EST
There is nothing I as the dhcp package maintainer can do about this.
At some point, the decision was taken not to ship dhcp server in
RHEL Workstation or Desktop releases. This is NOT a dhcp bug - hence,
I am closing as 'NOT A BUG'.

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