Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1003247: mailman3-web: Mailman3 not working following distribution upgrade from Debian 10 to 11.

244 views
Skip to first unread message

Gordon Dickens

unread,
Jan 6, 2022, 7:00:03 PM1/6/22
to
Package: mailman3-web
Version: 0+20200530-2
Severity: important

Dear Maintainer,

I performed a distribution upgrade from Debian 10 Buster (which runs mailman 3.2.1) to Debian 11 Bullseye (which runs mailman
3.3.1) with the command "apt-get full-upgrade -y" and everything apparently worked properly except at the end of the upgrade when
the following error dialog was generated by the mailman3-web and mailman3-full post-installation scripts:

Setting up mailman3-web (0+20200530-2) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf
dbconfig-common: flushing administrative password
sed: -e expression #2, char 77: unterminated `s' command
dpkg: error processing package mailman3-web (--configure):
installed mailman3-web package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mailman3-full:
mailman3-full depends on mailman3-web; however:
Package mailman3-web is not configured yet.

dpkg: error processing package mailman3-full (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mailman3-web
mailman3-full
E: Sub-process /usr/bin/dpkg returned an error code (1)

Now, every time that I execute "apt-get upgrade" then I continue to get the above error dialog. Also, the command
"dpkg-reconfigure mailman3-web" generates this output:

/usr/sbin/dpkg-reconfigure: mailman3-web is broken or not fully installed

So, I am now stuck since apt-get is saying that mailman3-web is not configured yet, however, neither apt-get nor dpkg-reconfigure
will successfully configure mailman3-web.

Note the syntax error statement from the above dialog which may be the culprit: "sed: -e expression #2, char 77: unterminated `s' command"

Does anybody have any idea how to fix this? I would very much appreciate some suggestions.

Thanks,

Gordon Dickens


-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailman3-web depends on:
ii dbconfig-mysql 2.0.19
ii debconf [debconf-2.0] 1.5.77
ii init-system-helpers 1.60
ii lsb-base 11.1.0
ii python3 3.9.2-3
ii python3-django-hyperkitty 1.3.4-4
ii python3-django-postorius 1.3.4-2+deb11u1
ii python3-mysqldb 1.4.4-2+b3
ii python3-psycopg2 2.8.6-2
ii python3-whoosh 2.7.4+git6-g9134ad92-5
ii ucf 3.0043
ii uwsgi-core 2.0.19.1-7.1
ii uwsgi-plugin-python3 2.0.19.1-7.1

Versions of packages mailman3-web recommends:
ii libapache2-mod-proxy-uwsgi 2.4.52-1~deb11u2

Versions of packages mailman3-web suggests:
ii default-mysql-server 1.0.7
ii mariadb-server-10.5 [virtual-mysql-server] 1:10.5.12-0+deb11u1

-- Configuration Files:
/etc/mailman3/apache.conf changed:
Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico
Alias /mailman3/static /var/lib/mailman3/web/static
<Directory "/var/lib/mailman3/web/static">
Require all granted
</Directory>
<IfModule mod_proxy_uwsgi.c>
ProxyPass /mailman3/favicon.ico !
ProxyPass /mailman3/static !
ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost
</IfModule>


-- debconf information:
mailman3-web/pgsql/changeconf: false
mailman3-web/remote/host: localhost
mailman3-web/dbconfig-remove: true
mailman3-web/internal/skip-preseed: false
mailman3-web/db/basepath: /var/lib/mailman3/web
mailman3-web/upgrade-error: abort
* mailman3-web/database-type: mysql
mailman3-web/pgsql/no-empty-passwords:
* mailman3-web/superuser-name: gordon
* mailman3-web/db/app-user: mailman3web@localhost
mailman3-web/passwords-do-not-match:
* mailman3-web/db/dbname: mailman3web
mailman3-web/missing-db-package-error: abort
* mailman3-web/superuser-mail: gor...@mailhub4u.com
mailman3-web/install-error: abort
mailman3-web/pgsql/method: TCP/IP
mailman3-web/mysql/authplugin: default
mailman3-web/nginx-choice:
mailman3-web/dbconfig-upgrade: true
mailman3-web/pgsql/admin-user: postgres
mailman3-web/pgsql/authmethod-admin: ident
* mailman3-web/mysql/method: Unix socket
* mailman3-web/emailname: host2.mailhub4u.com
mailman3-web/pgsql/authmethod-user: password
mailman3-web/remote/port:
mailman3-web/remove-error: abort
* mailman3-web/restart-webserver: true
mailman3-web/pgsql/manualconf:
mailman3-web/dbconfig-reinstall: false
* mailman3-web/dbconfig-install: true
mailman3-web/purge: false
mailman3-web/internal/reconfiguring: false
* mailman3-web/mysql/admin-user: debian-sys-maint
mailman3-web/upgrade-backup: true
* mailman3-web/configure-webserver: apache2
mailman3-web/remote/newhost:

Joost van Baal-Ilić

unread,
Jan 7, 2022, 2:00:04 AM1/7/22
to
<snip>
>
> So, I am now stuck
<snip>
>
> Does anybody have any idea how to fix this? I would very much appreciate some suggestions.
>

Not a fix, but a _very_ _dirty_ workaround:

sudo mv /var/lib/dpkg/info/mailman3-web.postinst /var/lib/dpkg/info/mailman3-web.postinst.disabled

(Only do this if everything else failed.) After that, try the install again by
running

sudo apt-get -f install

. Your can now do dpkg/apt stuff again. However, you'll have to manually
execute all the needed things /var/lib/dpkg/info/mailman3-web.postinst was
trying to achieve: have a look at that script.

HTH, Bye,

Joost
0 new messages