Your message dated Wed, 28 May 2025 13:35:10 +0000
with message-id <e1ukgw2-000jwt...@fasolo.debian.org>
and subject line Bug#1106677: fixed in bind9 1:9.20.9-2
has caused the Debian Bug report #1106677,
regarding bind9: Vcs-Git field needs to be updated for trixie
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 ow...@bugs.debian.org
immediately.)
--
1106677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.20.9-1
Hello.
After upgrading a server today, I noticed that the
default file /etc/bind/named.conf.options is now like this:
------------------------------------
options {
directory "/var/cache/bind";
};
------------------------------------
However, I expected something similar to the file
debian/extras/etc/named.conf.options
in the source package, since there is a debian/bind9.install
file to install it.
How does the second file becomes the first one when
the package is built?
I was trying to figure out why the commented lines:
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 0.0.0.0;
// };
are not provided anymore, but I was unable to determine it
from the git history.
Thanks.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.20.9-2
Done: Ondřej Surý <ond...@debian.org>
We believe that the bug you reported is fixed in the latest version of
bind9, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1106...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý <ond...@debian.org> (supplier of updated bind9 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 May 2025 13:39:20 +0200
Source: bind9
Architecture: source
Version: 1:9.20.9-2
Distribution: unstable
Urgency: low
Maintainer: Debian DNS Team <team+...@tracker.debian.org>
Changed-By: Ondřej Surý <ond...@debian.org>
Closes: 1106677
Changes:
bind9 (1:9.20.9-2) unstable; urgency=low
.
* Fix the default branch in the Vcs-Git field (Closes: #1106677)
Checksums-Sha1:
ed8d2cd5803f00137a34fd84b77365f0f5600aa5 2914 bind9_9.20.9-2.dsc
a745004712db24610e88fba45787935dd03dfeba 61580 bind9_9.20.9-2.debian.tar.xz
fed5745ffc22e607ef5cdce10c67e6692c03c3de 14624 bind9_9.20.9-2_amd64.buildinfo
Checksums-Sha256:
0cc66ea15488be53609e28f1db7197e776d9617cbd7eb18b44ae6346dd1e71f5 2914
bind9_9.20.9-2.dsc
2993b283528f8735f459c051bfb8ea862cc3d9846f2367ab3cf0346f4fc76d77 61580
bind9_9.20.9-2.debian.tar.xz
3058acda4f15b7050a53a44379e420373722c9b4e687ececb78cc022fc7ebb8e 14624
bind9_9.20.9-2_amd64.buildinfo
Files:
c0f21fb2a6a53c2c4e4d79b599e55d36 2914 net optional bind9_9.20.9-2.dsc
b06e16ce8840f7a14812de60bd1fa521 61580 net optional
bind9_9.20.9-2.debian.tar.xz
56d2f4c6c24139e0ef9bad2f6fbe8ada 14624 net optional
bind9_9.20.9-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmg3CYtfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKX3xAAk8Je6EzO5SqPC51oWmFJ3y784oNdpkJgVNrof+m//EZ4OGTVQUijXSP/
IQ5inrzHPA1Ip5ol7fAdDRSsj575k8gJO4mBUksOr3ybaFtxnmHn/E0sPhkX4fON
hZwANuTx45py3YpS7610owCEsLniq4duLTgzIJtrfspdtCcQxv4KrS1p3EH5+b+E
4TvQTUEXUa+dFo0kwvlpP26AiX2yQNzAqqrew0ErTRoX018f8n/UcpOgcf+UQjKa
ypLGvviK2DXa3K785TO1Iwm2HMNh4rEISCUdTb1xLjOPPbKGBasMKyjcbVWFTgtm
8GRkJo74VmBxVpIOnqRhbzObf2wpbpBR99zp9JHYIrdxbIBAkNQrmkHAm6d3abGy
pUDBtTyeN4gnS1eIx+1jIV4kAK1GrQeKHf7gomPW7vmv17QhvD9k+z2cUw2tzTUc
74uQ3CXfOjw2Ll0nlSaZv4/SRyFT2573Yl442iy+DZDN6B8tY3vaqYS8bSxEYJOD
nvtQY615YocMXLNB5dIDe7E3FlAyU37kDI67yHjQQct/iZWZSYIxCx70s3n90vUK
lsVu/J6VVIDtBrCkKfnFHsYe2pw+R/xzPecJzJn0jQP17QS2G9juLFxm/M0MxQWi
N84WIgmNUp5zDT7zi15Mi/kLkQtWSTnvspF2dhfn6BLwBxEQB10=
=62Cy
-----END PGP SIGNATURE-----
pgpJzvVsS5eGq.pgp
Description: PGP signature
--- End Message ---
