It should work with jinja 2.X, but it Seems that this one stopped working when Python jinja 3.0 dropped into Arch upstream
resolving dependencies...
looking for conflicting packages...
Packages (2) python-markupsafe-2.0.0-1 python-jinja-3.0.0-3
Total Download Size: 0.23 MiB
Total Installed Size: 1.35 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
python-jinja-3.0.0...
Probably another tweak in the requirements section would get it going.
edit: Looks like this does the trick:
-e 's|^Jinja2==2.11.3$|Jinja2>=2.11.3|' \
added to requirements .txt
prepare() {
cd "$pkgname-$pkgver"
# Arch usually has the latest versions. Patch requirements to allow them.
sed -i \
-e 's|^aiohttp==3\.7\.4.*|aiohttp>=3.7.4|' \
-e 's|^aiofiles==0\.6\.0$|aiofiles>=0.6.0|' \
-e 's|^sentry-sdk==1\.0\.0$|sentry-sdk>=1.0.0|' \
-e 's|^psutil==5\.8\.0$|psutil>=5.8.0|' \
-e 's|^distro==1\.5\.0$|distro>=1.5.0|' \
-e 's|^py-cpuinfo==7\.0\.0$|py-cpuinfo>=7.0.0|' \
-e 's|^Jinja2==2\.11\.3$|Jinja2>=2.11.3|' \ ##<---------- Here
requirements.txt
}
Pinned Comments
buzo commented on 2025-04-28 17:37 (UTC)
Upstream has split development of the major versions 2 and 3, with 2.2.54 being the latest release. I will keep this package tracking version 3, but could provide a separate package tracking version 2, if there is interest.