Le samedi 20 février 2016 à 19:52:49+0000, Bernhard Schmidt a écrit : > Pierre-Elliott Bécue <be...@crans.org> wrote: > > Hi Pierre, > > > Before requesting for sponsorship, and packaging officially the other > > components of mailman3, I'd like some "testers" for the core package I > > built, in order to be sure that it works, and that I will not introduce some > > stupid caveats on the packaging of the other components. > > > > .deb can be found here: http://peb.pimeys.fr/mailman/mailman3-core/ > > git repo can be found there: https://gitlab.pimeys.fr/PEB/mailman3-core > > and there: https://github.com/P-EB/mailman3-core > > > > Any volunteer welcome! Please, I need your help, I cannot review my work > > alone! :) > > I just tried to have a look in a stretch docker image. > > - There are three .deb files on your webserver > > mailman3-core_3.0.0-1_all.deb > mailman3-core_3.0.0-3_all.deb > mailman3-core_3.0.0-3_amd64.deb > > It is not immediately obvious which one to test, since -1 has actually > a newer timestamp.
The good version is actually the 3.0.0-1, sorry for the remaining stuff, I removed it. > - Mailman Core 3.0.1 and 3.0.2 have been released in the meantime Yes, I'll ask to mailman devels how clever it'd be to take 3.0.2 for packaging now. > - it does not work on stretch/sid because it is not compatible with > Python 3.5, see https://gitlab.com/mailman/mailman/issues/181 Yeah, during my tries I didn't met this issue. I guess it's because 3.5 wasn't in. I'll work on it as I'm not fully aware of how to enforce 3.4. > - it does not install on Jessie (even with jessie-backports because of > missing dependencies) (just a note because of not working on stretch > either) Backporting all mailman3 suite will not be simple I guess, but I intend doing so when and if my packaging for sid succeeds. > - The systemd unit won't work because the parameter for the > configuration file is '-C', not '-c' My bad, I really thought I've fixed it before sending this email. > - installing python3.4 and changing the shebang in /usr/bin/mailman > leads to the following error > > root@4ca9477a166c:~# /usr/bin/mailman -C /etc/mailman3/mailman.cfg start > Starting Mailman's master runner > /usr/bin/python3.4: can't open file '/var/lib/mailman/bin/master': > [Errno 2] No such file or directory > > The files are installed in /var/lib/mailman3/bin, but bin_dir in > /etc/mailman3/mailman.cfg points to /var/lib/mailman/bin ... both > directories are wrong from my POV, it should probably be > /usr/lib/mailman3 or something like that During my discussions with Barry Warsaw, we agreed that except the mail binary, the others shouldn't be in /usr/bin as their name is "too generic". This error is mailman3.cfg was in the same stack of patches that should have been committed before my email (with -C option) > - Fixing this up leads to > > root@4ca9477a166c:~# /usr/bin/mailman -C /etc/mailman3/mailman.cfg start > Starting Mailman's master runner > Traceback (most recent call last): > File "/var/lib/mailman3/bin/master", line 9, in <module> > load_entry_point('mailman==3.0.0', 'console_scripts', 'master')() > File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 536, > in main > with open(config.PID_FILE, 'w') as fp: > FileNotFoundError: [Errno 2] No such file or directory: > '/run/mailman3/master.pid' > > because the directory does not exist. Since you are shipping a systemd > unit only you should probably ship a .tmpfile as well. During my initial test, I tried to run mailman3 standalone, and the directory stayed, so I never met the error. Fix committed. Thanks. > I now have a running daemon. I haven't done anything with Mailman3 so > far, so I need to read up on that first. Thanks for reviewing, sorry for the loss of time I induced. -- PEB
