Hi,
I’ve recently moved, so everything is in but of disarray including my
builder machine. The git repository should be up to date, so if this
cannot wait a day or two until I connect rest of my network, anybody
should be able to build and upload new upstream version using
git-buildpackage. Alternatively, just wait a few days, I am almost
there re-connecting stuff…
I just came back from vacation and stumbled over this, sorry I couldn't
help earlier.
You had uploaded 9.18.6-1, but somehow this ended up as an amd64 upload
binary to unstable, so it did not migrate. And it did not migrate
because a binNMU to bind-dyndb-ldap is necessary, see #1014503.
I have just made a no-change source-only upload, so the first problem
should be resolved. For the second I have filed Bug#1019220 .
Now, I'm still utterly confused how this problem could have happened at
all. I was able to verify at this point that sid was indeed lacking
bind9-libs:amd64.
But it was built on the buildds
https://buildd.debian.org/status/fetch.php?pkg=bind9&arch=amd64&ver=1%3A9.18.4-2&stamp=1657022678&raw=0
and (due to the migration issues) the package version that was lacking
in sid is still present in testing, including bind9-libs:amd64
bind9-libs | 1:9.18.4-2 | testing | amd64,
arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
https://packages.debian.org/bookworm/bind9-libs
http://ftp.de.debian.org/debian/pool/main/b/bind9/bind9-libs_9.18.4-2_amd64.deb
http://snapshot.debian.org/package/bind9/1%3A9.18.4-2/#bind9-libs_1:3a:9.18.4-2
Bernhard
