Your message dated Fri, 30 Dec 2022 23:58:25 +0100 with message-id <[email protected]> and subject line Re: Bug#982671: Supporting unbound in stretch by upgrading to 1.9 has caused the Debian Bug report #982671, regarding python-unbound: unbound doesn't start with python module enabled to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 982671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982671 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python-unbound Version: 1.6.0-3+deb9u2 Severity: important Dear Maintainer, After security upgrade of unbound from 1.6 to 1.9, it failes to start when trying to load the python module, with error message: [123376:0] error: module init for module python failed I guess this is because python-unbound did not receive an update, and is still in version 1.6. I disabled the python module in unbound config as a workaround, but this means I cannot use python-unboudn at all with the latest unbound in stretch. -- System Information: Debian Release: 9.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-14-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-unbound depends on: ii libc6 2.24-11+deb9u4 ii libunbound2 1.6.0-3+deb9u2 ii python 2.7.13-2 python-unbound recommends no packages. python-unbound suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message --- src:unbound1.9 only existed in stretch-security and LTS support for stretch has already ended, I'm therefore finally closing this bug.Andreas
--- End Message ---
