mediagoblin-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Initial run of ./bin/dbupdate fails.


From: bill-auger
Subject: Re: Initial run of ./bin/dbupdate fails.
Date: Sat, 15 Oct 2022 12:53:16 -0400

On Thu, 13 Oct 2022 14:37:33 -0700 (PDT) Art wrote:
>      raise VersionConflict(dist, req).with_context(dependent_req)
> pkg_resources.ContextualVersionConflict: (Jinja2 2.11.3 
> (/usr/src/mediagoblin/lib/python3.10/site-packages/Jinja2-2.11.3-py3.10.egg), 
> Requirement.parse('Jinja2>=3.0'), {'sphinx'})  

i hit that one too - the reason for that is the hard-coded
version in setup.cfg:

> jinja2<3.0.0  # 3.0.0 uses f-strings (Python >= 3.7) breaking Debian 9.

as it mentions "python 3.7" and "Debian 9"; perhaps that restriction
is outdated and could/should be relaxed - instead of trying that, i
instead downgraded python-jinja v2.11.3, to satisfy setup.cfg - then
the conflict above appeared - my actual error messages was different;
but this is very likely the same conflict:

> error: Jinja2 2.11.3 is installed but Jinja2>=3.0 is required by {'sphinx'}

that was because the up-to-date python-sphinx in most distros requires
jinja >=3 - to compensate for that, i downgraded python-sphinx to v4.5.0

over-all, i ran into many similarly unsatisfied dependencies; because
i am packaging it to fit into a conventional system (intentionally
avoiding virtualenv, pip, npm, but using all system packages instead)
- to do so, the hard-coded versions setup.cfg expect python packages
which were current in a system from about one year ago or older -
other than this sphinx<>jinja conflict, debian is probably still good;
but this was a PITA to install for a rolling distro - probably the
hard-coded dependency versions in setup.cfg could be relaxed today



reply via email to

[Prev in Thread] Current Thread [Next in Thread]