Re: Supporting unbound in stretch by upgrading to 1.9

[Robert Edmonds <edmonds@debian.org>]

Markus Koschany wrote:
> Hello,
> 
> Am Mittwoch, den 17.02.2021, 14:09 -0500 schrieb Robert Edmonds:
> > 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.
> 
> Please feel free to reassign and/or adjust the bug report as necessary.

I get the following error message from the BTS. Do I need to do
"reassign 982671 unbound1.9" instead?

    > reassign 982671 unbound 1.9.0-2+deb10u2~deb9u1
    Bug #982671 [python-unbound] python-unbound: unbound doesn't start with python module enabled
    Bug #982672 [python-unbound] python-unbound: unbound doesn't start with python module enabled
    Bug reassigned from package 'python-unbound' to 'unbound'.
    Bug reassigned from package 'python-unbound' to 'unbound'.
    No longer marked as found in versions unbound1.9/1.9.0-2+deb10u2~deb9u1.
    No longer marked as found in versions unbound1.9/1.9.0-2+deb10u2~deb9u1.
    Ignoring request to alter fixed versions of bug #982671 to the same values previously set
    Ignoring request to alter fixed versions of bug #982672 to the same values previously set
    Bug #982671 [unbound] python-unbound: unbound doesn't start with python module enabled
    Bug #982672 [unbound] python-unbound: unbound doesn't start with python module enabled
    There is no source info for the package 'unbound' at version '1.9.0-2+deb10u2~deb9u1' with architecture ''
--> Unable to make a source version for version '1.9.0-2+deb10u2~deb9u1'
    Marked as found in versions 1.9.0-2+deb10u2~deb9u1.
    Marked as found in versions 1.9.0-2+deb10u2~deb9u1.
    > thanks

> We don't intend to build the python bindings for unbound1.9. This decision was
> intentional, so here are the alternatives. 
> 
> 1. Don't upgrade unbound 1.6 if you are sure, you are not affected by the
>    existing security vulnerabilities.
> 
> 2. I could remove the configure option --with-pyunbound and announce this with
> a new DLA, this would it make explicit that the python bindings are not
> supported.
> 
> However the end result will always be the same. You can't use the existing
> python bindings with the 1.9 version.
> 
> Regards,
> 
> Markus

OK. I understand the src:unbound1.9 package in stretch does not support
the Python bindings. Does LTS intend to continue supporting the embedded
Python scripting support in the src:unbound1.9 package's daemon?

-- 
Robert Edmonds
edmonds@debian.org