[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Initial run of ./bin/dbupdate fails.
From: |
Art |
Subject: |
Initial run of ./bin/dbupdate fails. |
Date: |
Thu, 13 Oct 2022 14:37:33 -0700 (PDT) |
Hi Folks,
happily, someone replied to my last email and shared with me how they had
configured GMG on Debian to talk with Postgres - set the entry to:
postgresql://<user>:<password>@<server>/<database_name>
They didn't post to the list, so I won't out them, for their privacy.
Unfortunately, though, the next step didn't work:
./bin/gmg dbupdate
I get all sorts of python errors, included below my sig line for your
reading pleasure. And, as I said, I don't know python.
Since this is "straight out of the box" with all the listed dependencies
given, in my view this enters bug territory. But maybe someone here knows
better? At the least it's a "documentation bug" as they are sometimes
called. My _suspicion_ is it's a dependency error, but I have no clue what
it could be, OR how to figure out what it is.
I'm pretty sure, but not certain, it has nothing to do with the postgres
connection because I went to the trouble, just for testing purposes, to create
the database on the same machine; it failed identically. Further, none of
the errors talk about postgres or database access that I can see but
rather speak to "Jinja2" and "sphinx."
I had a python-knowledgeable (but not true expert) colleague look at it
and he at first suggested that the additional version of Jinja I installed
(as root using dnf, of course) to overcome a weird sphinx-related issue
during the make and it appears to have fixed it. He noticed that there
were now two locations for was in an odd place, and proposed setting
PYTHONPATH.
It had not been set at all, so I tried setting it to include BOTH the
system's "normal" location and this one in the build-tree where I
installed GMG. Unfortunately, there was no change in behavior.
export
PYTHONPATH="/usr/lib/python3.10/site-packages:/usr/src/mediagoblin/lib/python3.10/site-packages"
I tried just the one & just the other - no luck.
I'm considering saving some bits from the source tree (which I had not
ralized was also intended to be the "installed directory), and trying
again "from scratch" in a different location. But, that's a good bit of
work which may result in failure again. I'm hoping someone someone can
give some insight.
Before I "hit send": I found the wiki but didn't find any place to post
this kind of problem, rather than the email list? Or, is the email list my
only option (within the Gnu community)?
Thanks,
Art
--
Art Richards
Art@TheTroyPress.com
http://TheTroyPress.com
------------------------------------------------------
$ ./bin/gmg dbupdate Traceback (most recent call
last):
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 568, in _build_master
ws.require(__requires__)
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 886, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 777, in resolve
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'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/mediagoblin/./bin/gmg", line 33, in <module>
sys.exit(load_entry_point('mediagoblin', 'console_scripts', 'gmg')())
File "/usr/src/mediagoblin/mediagoblin/gmg_commands/__init__.py", line
113, in main_cli
setup_func = import_component(command_struct['setup'])
File "/usr/src/mediagoblin/mediagoblin/tools/common.py", line 34, in
import_component
__import__(module_name)
File "/usr/src/mediagoblin/mediagoblin/gmg_commands/shell.py", line 20,
in <module>
from mediagoblin import mg_globals
File "/usr/src/mediagoblin/mediagoblin/mg_globals.py", line 21, in
<module>
import pkg_resources
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 3243, in <module>
def _initialize_master_working_set():
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 3226, in _call_aside
f(*args, **kwargs)
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 3255, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 570, in _build_master
return cls._build_from_requirements(__requires__)
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 583, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File
"/usr/src/mediagoblin/lib/python3.10/site-packages/pkg_resources/__init__.py",
line 777, in resolve
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'})
$
- Initial run of ./bin/dbupdate fails.,
Art <=
- Re: Initial run of ./bin/dbupdate fails., Andre van Eyssen, 2022/10/14
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/15
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/15
- Re: Initial run of ./bin/dbupdate fails., Art, 2022/10/15
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/15
- Message not available
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/16
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/16
- Re: Initial run of ./bin/dbupdate fails., Art, 2022/10/16
- Re: Initial run of ./bin/dbupdate fails., bill-auger, 2022/10/16