On 8/20/23 9:34 PM, Stephen J. Turnbull wrote:
David Newman writes:
I tried patching all importlib.resource references by hand, and MM3 starts ? but that can't be the "right" way to do this. Also, the diff references a src directory that doesn't exist under /opt/mailman.
The "right" way to do this kind of thing is to clone the git repository, apply the patch there, make a branch for it and commit it, build a wheel, and use pip to install that wheel to the venv.
Thanks in advance for patching clues.
I'm in a hurry so that's all the clue for now, but further inquiries are welcome if you need more detail or something doesn't go as expected.
Thanks for your response, Steve.
One detail that doesn't seem right is that the 1130.patch from GitLab references at least one file, .gitlab-ci.yml, that doesn't exist in the 3.3.8 production release that's installed when using 'pip install mailman' in the venv installation docs.
Just running 'git apply 1130.patch' on a local copy of the production 3.3.8 code fails because the file .gitlab-ci.yml isn't part of that code. There may be other errors too but the patch fails on that first one.
I'm looking to patch an existing production server running 3.3.8 so it will be able to start under Python 3.11 on Debian 12. Thanks in advance for additional clues on what seems like a fairly standard problem.
dn