Bug 80612 - RFE: replace package xinetd-2.3.7 with xinetd-2.3.9
RFE: replace package xinetd-2.3.7 with xinetd-2.3.9
Product: Red Hat Public Beta
Classification: Retired
Component: xinetd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-12-28 14:02 EST by Peter van Egdom
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-17 11:44:19 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 Peter van Egdom 2002-12-28 14:02:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
According to "http://www.xinetd.org/" there's a newer stable version of xinetd
available than the one shipped with Phoebe, it would be nice to replace this
package before Red Hat 8.1 beta 2 is out, so it can be tested during this
release cycle.

According to it's changelog it has some bugfixes and no major new features, so
it seems safe to update at this time.

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

How reproducible:

Steps to Reproduce:
1. Check out http://www.xinetd.org/
2. Check out Phoebe RPM's

Actual Results: 
 There's a newer stable version of xinetd available than the one shipped with

Expected Results: 
 At this time - before 8.1 beta 2 is released - is would be nice to update to
the latest stable.

Additional info:

Red Hat Linux release 8.0.92 (Phoebe)
Comment 1 Warren Togami 2002-12-29 19:14:37 EST
Please read Bug 76164.  xinetd-2.3.9 caused major problems when it became xinetd
errata for RH 7.x.  This has since been fixed.
Comment 2 Jay Fenlason 2003-01-17 11:44:19 EST
I've built 2.3.10-1 for rawhide.

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