Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend
On Wed, 1 Feb 2023 21:10:57 +0100 Matej Zagiba wrote: > I believe real problem lies in package management procedures - there > should be trigger to recompile and repackage (and retest) > bind9-dyndb-ldap after each version change and/or repackage of > bind9-libs. This action should be done automatically. Otherwise > bind9-dyndb-ldap will be permanently broken. This is, unfortunately, not as simple as you write there. bind9-dyndb-ldap is not as independent from bind9 upstream as we all would like. To make it compile with bind9 9.18.11, a tiny change is required, see [1]. So even if Debian packaging would do things like "recompile triggers", it wouldn't help here. > Should I open another bug? I don't think it's necessary, but if you want this tracked in the BTS then it needs to be a new one as it's a different issue, even if similar in nature. Cheers, sur5r [1] https://pagure.io/bind-dyndb-ldap/pull-request/218 -- ceterum censeo microsoftem esse delendam. pgpIi6WeHhtLD.pgp Description: OpenPGP digital signature
Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend
Dear Maintainers, this bug is NOT FIXED, which manifests right now. packake bind9-dyndb-ldap is now broken both in stable and unstable. In stable: bind9-dyndb-ldap is in version 11.6-3 and this package depends on bind9-libs >= 1:9.16.15. Reality is, that bind9-dyndb-ldap actually depends on bind9-libs == 1:9.16.15. Which is no longer available, so package install but fails to load (bringing bind9 down whit itself.) In unstable: bind9-dyndb-ldap is in version 11.10-2 and this package depends on bind9-libs == 1:9.18.10-2. Which is no longer available. bind9-dyndb-ldap is not installable on fresh installs of unstable, or which is even worse, bind9 will not upgrade to latest version, so leaving systems vulnerable to handful of CVEs. I believe real problem lies in package management procedures - there should be trigger to recompile and repackage (and retest) bind9-dyndb-ldap after each version change and/or repackage of bind9-libs. This action should be done automatically. Otherwise bind9-dyndb-ldap will be permanently broken. Should I open another bug?
Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend
l3mm.0x kirjoitti 1.2.2022 klo 12.35: > Package: bind9-dyndb-ldap > Version: 11.6-3 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > after an upgrade from buster to bullseye my previously working > bind9-dyndb-ldap > installation dosn't work anymore. > > It seems that there is something wrong with the dependencies to the package > bind9-libs. > > named log: > ... > Feb 01 07:53:19 testing named[4485]: loading DynDB instance 'ldap-db' driver > '/usr/lib/bind/ldap.so' > Feb 01 07:53:19 testing named[4485]: failed to dynamically load instance > 'ldap- > db' driver '/usr/lib/bind/ldap.so': libdns-9.16.15-Debian.so: cannot open > shared object file: No such file or directory (failure) > Feb 01 07:53:19 testing named[4485]: dynamic database 'ldap-db' configuration > failed: failure > Feb 01 07:53:19 testing named[4485]: loading configuration: failure > Feb 01 07:53:19 testing named[4485]: exiting (due to fatal error) > > > The package bind9-libs lists a newer version about the shared object file. > > /usr/lib/x86_64-linux-gnu > /usr/lib/x86_64-linux-gnu/libbind9-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libdns-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libirs-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libisc-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libisccc-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libisccfg-9.16.22-Debian.so > /usr/lib/x86_64-linux-gnu/libns-9.16.22-Debian.so Oh nice, a rather big version bump disguised as a CVE update.. You'd need the version from unstable to have some hope of it working with bind9 9.16.17+.
