Package: mailman3-web Followup-For: Bug #921128 I have tried to reproduce this in buster and at first I seem to recall I did reproduce it, but now I somewhat managed to get through and have it installed correctly.
Also note this might be a bug specific to MySQL: running the dbconfig stuff with a sqlite3 backend doesn't trigger the same bug, even in backports. That said, the bug doesn't occur within dbconfig itself. It's the django migration that raises the backtrace (which is logical considering dbconfig is written in shell and not Python). Specifically, this command reproduces the problem outside of dpkg: su --shell /bin/sh --command "python3 /usr/bin/django-admin migrate --no-input --verbosity 3 --pythonpath /usr/share/mailman3-web --settings settings" www-data And, for what it's worth, I tried backporting the 0+20180916-4 release of mailman-suite, to no effect: the same error still occurs. A. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mailman3-web depends on: ii dbconfig-sqlite3 2.0.11 ii debconf [debconf-2.0] 1.5.70 ii lsb-base 10.2018112800 ii node-less 1.6.3~dfsg-3 ii python3 3.7.2-1 ii python3-django-hyperkitty 1.2.1-4 ii python3-django-postorius 1.2.2-4 ii python3-psycopg2 2.7.7-1 ii python3-pymysql 0.9.3-1 ii python3-whoosh 2.7.4+git6-g9134ad92-1 ii ruby-sass 3.5.6-1 ii ucf 3.0038+nmu1 ii uwsgi 2.0.17.1-11 ii uwsgi-plugin-python3 2.0.17.1-11 Versions of packages mailman3-web recommends: ii libapache2-mod-proxy-uwsgi 2.4.37-1 Versions of packages mailman3-web suggests: ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.12-2 -- debconf-show failed