Bug 20686 – New bind package is missing lots of stuff.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 20686 - New bind package is missing lots of stuff.

Summary:	New bind package is missing lots of stuff.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bind (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	Dale Lovelace
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-11-11 16:23 EST by dan
Modified:	2005-10-31 17:00 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-11-11 18:16:16 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description dan 2000-11-11 16:23:05 EST

Take a  look at the bind packages that were always made available before.

http://www.redhat.com/support/errata/RHSA1999054-01.html

Now we have those 3 packages replaced with just 1, and missing almost all
the tools the 3 together provided.

This is bad, and yet another reason on my list to switch to debian.

I'm getting sick of this!

Comment 1 Bernhard Rosenkraenzer 2000-11-11 16:31:22 EST

The subpackages are not affected by the problem and did not change
at all between 8.2.2_P5 and 8.2.2_P7.

Comment 2 Bernhard Rosenkraenzer 2000-11-11 16:32:59 EST

I agree, though, that they should be updated to avoid confusions like
this; I'll take care of it.

Comment 3 dan 2000-11-11 18:16:13 EST

I did think of this, and yes clarity is a wonderful thing.
Thanks! I'll go eat some humble pie now.......

Comment 4 Bill Nottingham 2000-11-13 02:16:31 EST

This should be fixed now.

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