Your message dated Fri, 10 Feb 2023 15:25:01 +0100 with message-id <[email protected]> and subject line Not a bug has caused the Debian Bug report #939187, regarding bind9: Bind cache directory owned by root, not writable by bind user to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 939187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939187 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bind9 Version: 1:9.11.5.P4+dfsg-5.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** This is a bug in the installation script of the bind9 package. * What led up to the situation? I run bind as the bind user. Upon a new install, using my previous server's config files, I was unable to successfully start the daemon. The error message cited an inability to write a file to /var/cache/bind. * What exactly did you do (or not do) that was effective (or ineffective)? I changed the ownership of /var/cach/bind to bind:bind. As installed it was owned by root:root. The package installation script needs to set the ownership to bind:bind. * What was the outcome of this action? The daemon started successfully. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bind9 depends on: ii adduser 3.118 ii bind9utils 1:9.11.5.P4+dfsg-5.1 ii debconf [debconf-2.0] 1.5.71 ii dns-root-data 2019031302 ii libbind9-161 1:9.11.5.P4+dfsg-5.1 ii libc6 2.28-10 ii libcap2 1:2.25-2 ii libcom-err2 1.44.5-1 ii libdns1104 1:9.11.5.P4+dfsg-5.1 ii libfstrm0 0.4.0-1 ii libgeoip1 1.6.12-1 ii libgssapi-krb5-2 1.17-3 ii libisc1100 1:9.11.5.P4+dfsg-5.1 ii libisccc161 1:9.11.5.P4+dfsg-5.1 ii libisccfg163 1:9.11.5.P4+dfsg-5.1 ii libjson-c3 0.12.1+ds-2 ii libk5crypto3 1.17-3 ii libkrb5-3 1.17-3 ii liblmdb0 0.9.22-1 ii liblwres161 1:9.11.5.P4+dfsg-5.1 ii libprotobuf-c1 1.3.1-1+b1 ii libssl1.1 1.1.1c-1 ii libxml2 2.9.4+dfsg1-7+b3 ii lsb-base 10.2019051400 ii net-tools 1.60+git20180626.aebd88e-1 ii netbase 5.6 bind9 recommends no packages. Versions of packages bind9 suggests: pn bind9-doc <none> pn dnsutils <none> pn resolvconf <none> pn ufw <none> -- Configuration Files: /etc/bind/named.conf.local changed: // // Do any local configuration here // zone "bgnet" IN { type master; file "/etc/bind/named.bgnet"; }; zone "7.7.10.in-addr.arpa" IN { type master; file "/etc/bind/named.rev.10.7.7"; }; // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; -- debconf information: bind9/different-configuration-file: bind9/start-as-user: bind bind9/run-resolvconf: false
--- End Message ---
--- Begin Message ---The postinst script sets correct permissions here (since forever): if [ "$uid" = "0" ]; then chown bind /etc/bind/rndc.key chgrp bind /etc/bind chmod g+s /etc/bind chgrp bind /etc/bind/rndc.key /var/cache/bind chgrp bind /etc/bind/named.conf* || true chmod g+r /etc/bind/rndc.key /etc/bind/named.conf* || true chmod g+rwx /var/cache/bind fi Whatever problem you had, it was a local issue, not packaging issue. Ondrej -- Ondřej Surý (He/Him) [email protected]
--- End Message ---
