Bug#1020413: nmu: bind-dyndb-ldap_11.6-3
> On 21. 9. 2022, at 20:35, Adam D. Barratt <adam@adam-barratt.org.uk> wrote:
>
> Control: tags -1 + bullseye
>
> On Wed, 2022-09-21 at 13:47 +0200, Ondřej Surý wrote:
>> nmu bind-dyndb-ldap_11.6-3 . ANY . bullseye . -m "rebuild for
>> bind9_9.16.33-1~deb11u1"
>>
>> Hi,
>>
>> after the bind9_9.16.33-1~deb11u1 is release to bullseye-security,
>> the
>> bind-dyndb-ldap plugin will require binNMU.
>>
>
> We can do that - once the packages are in p-u, because p-u chroots
> don't pull in packages from the security archive - but it will mean
> that users won't get the binNMUs until the next point release, which
> probably isn't until November now.
>
> Is that OK?
Adding Paul, Salvatore and Timo into the bunch.
I honestly don't know because I don't use this package, but I think
it might prevent the users using the bind-dyndb-ldap users from
upgrading the bind9 package.
Should I then prepare a NMU for bullseye-security?
Looks like only viable solution long-term would be to build all the
bind plugins from the src:bind9 package, but it's too late for bullseye.
Ondrej
--
Ondřej Surý (He/Him)
ondrej@sury.org
Reply to: