Package: python3-samba
Version: 2:4.11.5+dfsg-1+b1
Severity: important
Dear Maintainer,
* What led up to the situation?
attempting to update working Samba AD DC on Buster to Testing
* What exactly did you do (or not do) that was effective (or
samba tries to update DNS to match changes in it's IP addresses
ineffective)?
* What was the outcome of this action?
samba_dnsupdate is Python, and it fails due to error importing samba.gensec
C module
* What outcome did you expect instead?
upgrade should have been transparent
Upstream samba 4.11.6 contains the fix I believe:
git commit f0eb1e623f76d3dbd0c22f96cabebd1041c147df
Author: Torsten Fohrer <torsten.foh...@sbe.de>
Date: Sun Dec 15 16:58:40 2019 +0100
Avoiding bad call flags with python 3.8, using METH_NOARGS instead of zero.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1), LANGUAGE=en_CA
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-samba depends on:
ii libbsd0 0.9.1-2
ii libc6 2.30-4
ii libldb2 2:2.0.8-2
ii libpython3.8 3.8.2-1+b1
ii libtalloc2 2.3.0-5
ii libtevent0 0.10.1-4
ii libwbclient0 2:4.11.5+dfsg-1+b1
ii python3 3.8.2-3
ii python3-crypto 2.6.1-13
ii python3-ldb 2:2.0.8-2
ii python3-talloc 2.3.0-5
ii python3-tdb 1.4.2-3+b1
ii samba-libs 2:4.11.5+dfsg-1+b1
Versions of packages python3-samba recommends:
ii python3-gpg 1.13.1-6
python3-samba suggests no packages.
-- no debconf information
