Comment 3 for bug 1980854

Alberto, Brett and James - thanks for looking into this.

One clarification: as I'm hoping eventually to submit changes to add devuan support to cloud-init, I'm working on a clone of the github repo and keeping the clone up-to-date - so hopefully at the moment I'm doing my investigations at the tip of the 'main' branch. When I know what's required for devuan support, I'll create a fork in my github account and eventually create a pull request.

Re. the jinja2 problem - I've just tried editing tox.ini to remove the markupsafe==2.0.1 line and changing the jinja2 line to a later version. It appears that jinja2 version 3.0.0a1 was the first one in which the soft_unicode problem was fixed (with the deps line in tox.ini set to "jinja2==3.0.0a1", the lowest-supported-dev tests run clean; with it set to "jinja2==2.11.3" (the last version before v3) they fail).

Note that I'm using the following command to find all the available releases of jinja2 (apparently it's the usual way of doing this in pip3):

pip3 install --use-deprecated=legacy-resolver jinja2==

I haven't as yet tried testing this on a distro/release which uses python<3.9 (I'll do this soon). I've also been adding devuan support to walinuxagent, and unfortunately that requires python 3.9 (using lower versions of python 3, walinuxagent can't distinguish between devuan and debian).