test - ignore - Debian Buster 10.13 --> 11.10 Bullseye pre-reboot test (apt-get -y full-upgrade completed) # uptime; uname -a; ls -A1 /boot 13:21:59 up 4 days, 4:25, 2 users, load average: 0.13, 0.17, 0.28 Linux balug-sf-lug-v2.balug.org 4.19.0-27-amd64 #1 SMP Debian 4.19.316-1 (2024-06-25) x86_64 GNU/Linux System.map-4.19.0-27-amd64 System.map-5.10.0-32-amd64 boot config-4.19.0-27-amd64 config-5.10.0-32-amd64 grub initrd.img-4.19.0-27-amd64 initrd.img-5.10.0-32-amd64 lost+found vmlinuz-4.19.0-27-amd64 vmlinuz-5.10.0-32-amd64 #
Debian Buster 10.13 --> 11.10 Bullseye post-reboot test (apt-get -y full-upgrade completed) # uptime; uname -a; cat /etc/debian_version; ls -A1 /boot 13:33:48 up 3 min, 1 user, load average: 0.86, 1.46, 0.69 Linux balug-sf-lug-v2.balug.org 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64 GNU/Linux 11.10 System.map-4.19.0-27-amd64 System.map-5.10.0-32-amd64 boot config-4.19.0-27-amd64 config-5.10.0-32-amd64 grub initrd.img-4.19.0-27-amd64 initrd.img-5.10.0-32-amd64 lost+found vmlinuz-4.19.0-27-amd64 vmlinuz-5.10.0-32-amd64 #
And testing again after various cleanup. Seems to mostly be working ... except authentication from serial console is failing, but works via ssh. Anyway, nothing mailman3 related, anyway.
With the newer HyperKitty, downloading the "whole"* archive is not particularly obvious. E.g. main URL for (a) list archive: https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org/ Nothing on there about downloads, under "All Threads" it offers up this: https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org/... but hovering over it shows "This month in gzipped mbox format" If we go under "Threads by month" The Download that is offered up also, by hovering over it shows "This month in gzipped mbox format" However, URL: https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org/... will grab "everything" ... at least that HyperKitty offers up for that list. Not particularly obvious, but one can craft it from the other URLs offered. I wonder if maybe that's even intentional on GNU Mailman's part? "Security" by obscurity?
*or at least as much of it as the hyperkitty interface will hand over, and including some @ --> (a) obfuscation.