On 2022-10-29 13:49, Stephen J. Turnbull wrote:
since our last update from python 3.6 to python 3.9 If somebody knows what went wrong, that would be great.
I don't know if it would have this symptom but between 3.7. and 3.8 Python moved the clock() function (IIRC) out of time, and recent Mailman now use time.time() in mailman/src/mailman/utilities/uid.py:TokenFactory._next_unpredictable_id instead of clock(). If your Mailman is old enough to expect time.clock() to exist, it's going to have problems.
I recommend upgrading Mailman, but if for some reason that's not realistic for you (or this turns out to be a false lead), maybe Mark or Abhilash have some ideas. Hi Steve,
the error was really dumb on my side. I forgot to add in my ansible deployment command for the venv the package mailman-hyperkitty and because of that the commands where missing and it produced the error i described.
Today I read the documentation again and saw that i had missed that package somehow.
Thanks for your help and hard work on this project.
regards Jacob