[Pkg-freeipa-devel] Bug#998575: Bug#998575: Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)

[Timo Aaltonen]

On 9.11.2021 10.53, Ondřej Surý wrote:
> Hi Timo,
> 
>> On 5. 11. 2021, at 8:09, Timo Aaltonen <tjaalton at debian.org> wrote:
>>
>> On 5.11.2021 1.37, peter green wrote:
>>>>   bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be installed
>>> It looks like bind8 no longer builds the bind9-dev package. It's still present in
>>> unstable as a cruft package but is uninstallable due to version constraints, it's
>>> completely gone from testing.
>>
>> I don't know what's going on here, but at least the current bind9 packaging is not available on salsa, debian/main is on 9.16.22-1 and according to d/changelog it was uploaded to unstable on the same day as 9.17.19-1... (which has now migrated to testing already)
> 
> The 9.17 packaging is available from the isc/9.17 branch which should be up to date.
> 
>> The new bind9 doesn't mention dropping bind9-dev on d/changelog. Ondrej, why was it dropped?
> 
> We need to figure out what to do with bind-dyndb-ldap in the future.  The BIND 9 libraries are not
> meant for public consumption since 9.14.0. The upstream (which is incidentally also me) has declare the libraries
> private and the symbols could change even between patch releases. There’s absolutely no guarantee
> about symbol stability even on stable branch.
> 
> Unfortunately, bind-dyndb-ldap is licensed under GPL-2.0 which makes it impossible to include
> it directly in the src:bind9 package.
> 
> I see no easy way from this. I will reintroduce the bind9-dev package, but this will make
> the bind-dyndb-ldap package to regularly FTBFS anyway and it needs to be fixed before
> the next stable release.

Ok thanks. I asked about plans to upstream the ldap plugin, but 
apparently "upstream was not interested in it". Would it be possible to 
get merged now? :) (if the license is changed, of course)



-- 
t