Hi Eric, Am 04.03.2018 um 04:59 schrieb Eric Côté: > Bug is still present.
I did quite some testing of the mailman3 packages in the last days, using all possible database backends. So far, I failed to reproduce the bug you discovered. We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to avoid further confusion about the purpose of the package. Similarly, we renamed 'mailman3-core' to 'mailman3'. You should find all these packages in Debian Unstable by now. Would you mind to purge all your mailman3 packages, do a fresh installation and see, whether you're still able to reproduce the bug with the latest packages from Debian Unstable? > Like I mentioned in my original report, "mailman3suite" is the user in > /usr/share/mailman3-suite/settings.py . I've had to hand edit it so my install > reads my DB settings in /etc/mailman3/mailman3-suite.py . After testing different settings, I'm pretty confident that indeed the database settings from '/etc/mailman3/mailman3-suite.py' (or now '/etc/mailman/mailman-web.py') are used in a clean mailman3-suite/mailman3-web installation. Please send the output of the following commands: $ ls -al /etc/mailman3/mailman-suite.py $ ls -al /usr/share/mailman3-suite/settings* > Seems this might be in either python-django-hyperkitty (which is I think is > the > case), since the log is referencing django and hyperkitty, or in > python3-mailman-hyperkitty (which doesn't seem to be picking up my list > content > anyway; I should be seeing archives, but I don't, in the web UI). > > I dunno how to refile a bug to another source package or tag another (if > that's doable). You can reassign existing bugreports by using 'Control:' pseudo-headers at the beginning of mails or by sending control commands to the bugtracker[1]. [1] https://www.debian.org/Bugs/server-control Cheers, jonas
signature.asc
Description: OpenPGP digital signature