>>>>> "Mark" == Mark Sapiro <m...@msapiro.net> writes:
Mark> On 8/24/25 17:03, Peter Chubb via Mailman-users wrote:
>> Hi Folks, I'm running the Debian-packaged mailman3 (yes I know ...)
>> and running: sudo -u list mailman -h gives a python backtrace
>> (which I've appended the tail end of). Can someone who has the
>> upstream installed version (using venv) please check that `mailman
>> -h` works there before I waste too much time investigating in the
>> wrong places?
Mark> Yes, `mailman -h` works and produces the same help output and
Mark> list of subcommands as `mailman` with no arguments or
Mark> options. Does it work with no options? Does it work if you do
Mark> `mailman -C path/to/mailman.cfg -h`?
Thanks. Without options it works; and it works with an explicit
config path. So I know where to look to fix it (and will report it on
the Debian bug tracker)
Interestingly:
sudo -u list mailman -C /etc/mailman3/mailman.cfg -h
works, but
sudo -u list env MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg mailman -h
does not.
And
sudo -u list mailman info
reports /etc/mailman3/mailman.cfg as the current configuration file.
Peter C
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/55BJDO3HRMIKPDR5RVBUCDRRUU73ANB3/
This message sent to arch...@mail-archive.com
