Bug 18629 – bind 9 ebuild config fails to create the chroot directory after an existing directory has been found

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Matt Bishop 2003-04-02 06:39:12 UTC]

Emerged bind 9 with no problems.

Following the instructions at the bottom of /etc/conf.d/named, I:
1. created a directory with the correct permissions
2. ran 'ebuild /var/db/pkg/net-dns/<bind version>/<bind-version> config'

The script reported that the directory already exists and then exited.

I deleted the directory and ran the ebuild again. The script this time reported 
nothing but did not create the chroot directory as expected.

Reproducible: Always
Steps to Reproduce:
1.create a directory
2.update /etc/conf.d/named with the directory name
3.run 'ebuild /var/db/pkg/net-dns/<bind version>/<bind-version> config'
4.delete the directory
5.run 'ebuild /var/db/pkg/net-dns/<bind version>/<bind-version> config'


Actual Results:  
The chroot directory is not created. No information is outputed by the ebuild 
script

Expected Results:  
created the directory named in the CHROOT variable in /etc/conf.d/named and 
populated it with the chroot directories and the required files for bind named.

added the line:

EXISTS="no"

at the top of the ebuild script bind-9.2.2.ebuild in directory /var/db/pkg/net-
dns/bind-9.2.2/

The script fails to run properly after an existing directory has been detected 
as the EXISTS variable is being persisted between runs and is not initialised 
at any point in the script. Initialising the var fixes the bug.

[Comment 1 Martin Holzer (RETIRED) 2003-04-15 10:46:13 UTC]

fixed in cvs

*** This bug has been marked as a duplicate of 18290 ***