Bug 8028 – bind scripts to upgrade from named.boot to named.conf fails

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 8028 - bind scripts to upgrade from named.boot to named.conf fails

Summary:	bind scripts to upgrade from named.boot to named.conf fails

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-12-28 17:03 EST by Göran Uddeborg
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-01-17 12:36:27 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 Göran Uddeborg 1999-12-28 17:03:56 EST

I upgraded from bind v4 to bind v8 with bind-8.2.2_P3-1.  This package has
an postinstall script which seems to be supposed to create a named.conf
from a named.boot if it doesn't already exist.  That applies to me.

The script fails, though, since it looks for an executable perl script

	/usr/doc/bind-8.2.2_P3/named-bootconf.pl

But there isn't any such script.  Instead there is a

	/usr/doc/bind-8.2.2_P3/named-bootconf/Grot/named-bootconf.pl

which, by the way, is not executable.  (But when I ran this "by hand" it
did the job nicely.)

Comment 1 Bernhard Rosenkraenzer 2000-01-17 12:36:59 EST

Thanks, fixed.

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