Python backtrace from `mailman -h`

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?
... File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 44, in _load add_components('commands', ICLISubCommand, self._commands) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 218, in add_components for component_class in find_pluggable_components(subpackage, interface): ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 181, in find_pluggable_components for name, plugin_config in config.plugin_configs: ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 291, in plugin_configs plugin_sections = self._config.getByCategory('plugin', []) ^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'getByCategory'
Peter C

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?
Yes, mailman -h
works and produces the same help output and list of
subcommands as mailman
with no arguments or options. Does it work with
no options? Does it work if you do mailman -C path/to/mailman.cfg -h
?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

"Mark" == Mark Sapiro <mark@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
participants (2)
-
Mark Sapiro
-
Peter Chubb