On 10/13/22 10:55, Eggert Ehmke wrote:
It shouldn't have been necessary to apply any patch. The head of the GitLab hyperkitty master branch is already compatible with mistune 2.0.4
strange, I still had the line with the (not working) from mistune.scanner import escape_html, escape_url
maybe because the migration step was not working at that time?
It should have nothing to do with migrations. The command
pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master
run as the mailman user with your venv active should have set the content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to be the same as https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer...., but it didn't. I wonder what else didn't get upgraded? Clearly it did do something because mistune was upgraded.
If you run pip freeze in your active venv,, what versions do you see
for the things you upgraded? Do they look for example like
HyperKitty @
git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a28fd7803
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan