Re: Supporting unbound in stretch by upgrading to 1.9

[Robert Edmonds <edmonds@debian.org>]

Markus Koschany wrote:
> Hi,
> 
> Am Mittwoch, den 17.02.2021, 12:43 -0500 schrieb Robert Edmonds:
> [...]
> > Hi,
> > 
> > It looks like #982671 / #982672 was assigned by the BTS to src:unbound
> > rather than src:unbound1.9. I attempted to re-assign the bug to
> > src:unbound1.9 with notfound/found but I don't think that worked since I
> > don't see it on
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=unbound1.9.
> > 
> > This bug also should have been reported against the unbound binary
> > package built by src:unbound1.9, not python-unbound, because the bug
> > appears to be about src:unbound1.9's unbound daemon failing to start. My
> > understanding is that the embedded Python scripting support in the
> > unbound daemon (which is built on stretch against Python 3, not Python 2
> > anyway) does not require the python-unbound or python3-unbound packages,
> > which are unrelated Python extension module bindings for the APIs in the
> > C libunbound library.
> > 
> > Also, it looks like the upload of unbound1.9 1.9.0-2+deb10u2~deb9u1
> > dropped the python-unbound and python3-unbound binary packages. It's not
> > clear why and it would be nice if the reason were documented in
> > debian/changelog.
> > 
> 
> python{3}-unbound is no longer supported in Stretch. See also DSA-4694-1. [1] 
> We only support the unbound daemon, unbound-host, unbound-anchor and
> libunbound8. Since unbound does not require the python bindings, both packages
> were dropped from src:unbound1.9. I suggest to mark this bug as wontfix.
> 
> Regards,
> 
> Markus
> 
> [1] https://lists.debian.org/debian-security-announce/2020/msg00098.html

Hi,

#982671 / #982672 is incorrectly reported against the python-unbound
package. It should instead be against the unbound binary package because
this functionality is in the unbound daemon. The error message cited in
the original report is an error message generated by the unbound daemon:

    [123376:0] error: module init for module python failed

Based on the original report this failure occurred after the bug
reporter upgraded to src:unbound1.9's unbound package in oldstable.

The embedded Python scripting support is in the unbound daemon and
enabled by the the '--with-pythonmodule' parameter to the unbound
configure script. It results in this dependency in the built unbound
package:

$ dpkg-deb -I unbound_1.9.0-2+deb10u2~deb9u1_amd64.deb | grep '^ Depends:'
 Depends: adduser, dns-root-data, lsb-base (>= 3.0-6), openssl,
     unbound-anchor, init-system-helpers (>= 1.18~), libc6 (>= 2.17),
     libevent-2.0-5 (>= 2.0.10-stable), libfstrm0 (>= 0.2.0), libprotobuf-c1
                 vvvvvvvvvvvvvvvvvvvvvvvvvv
     (>= 1.0.1), libpython3.5 (>= 3.5.0~b1), libssl1.1 (>= 1.1.0),
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
     libsystemd0

The python{3,}-unbound packages implement the Python extension module
bindings for the C libunbound library. The Python extension module is
enabled by the '--with-pyunbound' parameter to the unbound configure
script.

-- 
Robert Edmonds
edmonds@debian.org