Bug#89762: Configuration::ReadConfigFile doesn't behave as documented

[Adam Heath <doogie@rlx.doogie.org>]

Package: apt
Version: cvs as of Thu Mar 15 17:29:54 UTC 2001

// ReadConfigFile - Read a configuration file                           /*{{{*/
// ---------------------------------------------------------------------
/* The configuration format is very much like the named.conf format
   used in bind8, in fact this routine can parse most named.conf files. 
   Sectional config files are like bind's named.conf where there are 
   sections like 'zone "foo.org" { .. };' This causes each section to be
   added in with a tag like "zone::foo.org" instead of being split 
   tag/value. */

Yet, doing the following:

doogie@debian-devel1:~/rlx/netinst$ apt-config -c /etc/bind/named.conf dump
...
options "";
options::directory "/var/cache/bind";
options::forwarders "";
options::forwarders:: "192.168.3.100";
options::forwarders:: "10.1.1.31";
logging "";
logging::category "cname";
logging::category:: "null";
logging::category:: "null";
zone "255.in-addr.arpa";
zone::type "master";
zone::file "/etc/bind/db.255";
--

According to the docs, that last block should look like this:

--
zone::255.in-addr.arpa "";
zone::255.in-addr.arpa::type "master";
zone::255.in-addr.arpa::file "/etc/bind/db.255";
--

And there should be several zone entries as well, instead of overwriting
them all.

It also affects the logging block, which looks like this in named.conf:

--
logging {
        category lame-servers { null; };
        category cname { null; };
};
--

It should have those looking like the following:

--
logging::category::lame-servers "";
logging::category::lame-servers:: "null";
logging::category::cname "";
logging::category::cname:: "null";
--