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

[Art]

Thanks for that, Bill. I'm planning to do exactly this:

On Sat, 15 Oct 2022, bill-auger wrote:
> 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

...That is, I an NOT going to virtualize this and intend to run it on a 
"conventional system" and use "system packages."

Sounds like I'm headed for trouble.

Advice?

As for your comment that, "probably the hard-coded dependency versions in 
setup.cfg could be relaxed today", I'm hacking a version of setup.cfg to 
do exactly that. If it works, I'll report back!

Thanks again,
Art


--
Art Richards
Art@TheTroyPress.com
http://TheTroyPress.com