Source: bind9 Version: 1:9.19.17-1 Severity: normal User: de...@kali.org Usertags: origin-kali
Dear Maintainer, In https://bugs.debian.org/1025519 was reported a bug in bind9 apparmor configuration. It was fixed on the branch `debian/9.18`, with commit https://salsa.debian.org/dns-team/bind9/-/commit/5c03f25e, and released version `1:9.18.10-2` of bind9 (released in December 2022). However today the issue is back. The regression is due to the fact that the commit 5c03f25e was not applied in the branch `debian/9.19`, which is currently in Debian unstable. Looking at the changelog (on branch `debian/9.19`), it jumps straight from `9.18.2-1` to `9.19.0-1`, makes me wonder how many good commits from the branch 9.18 are missing in the branch 9.19... Please have a look, and at least apply 5c03f25e, it's a must! Thanks in advance, Arnaud
