Upgrade issue from 0.10 to 0.11

[TmCTux]

following the upgrade guide (and the installation guide just in case), I've encounter the following issue during upgrade:

1) after launching this command:
./bootstrap.sh && VIRTUALENV_FLAGS='--system-site-packages' ./configure && make

it fails during setup saying idna3.2 is installed (as one package require >2 and it picks the last available) but a later one require < 3 (this could be removed because python2 support has been dropped).

workaround was:
./bin/pip uninstall idna
./bin/pip install idna==2.10
and relaunch the last step:
./bin/python setup.py develop --upgrade
and continue the rest of the upgrade process:
make

2) on the last upgrade process we have to upgrade the db:
./bin/gmg dbupdate
this fails because jsonschema.compat is not found

workaround: commenting the import from the following file mediagoblin/tools/metadata.py

and now the gmg dbupdate works.

YMMV but that's what happend for me on buster 10.10 on 5th july 2021. (date can be important due to external nodejs dependency) - and it is only reported now as the trac seemed to have been broken for a while (on my side at least).

thanks again for this new release, works quite well so far!

[Ben Sturmfels]

Hi TmCTux,

Thanks for taking the time to report, and sorry for the Trac instability. We're working on fixing this.

Replying to TmCTux:

following the upgrade guide (and the installation guide just in case), I've encounter the following issue during upgrade:

1) after launching this command:
./bootstrap.sh && VIRTUALENV_FLAGS='--system-site-packages' ./configure && make

it fails during setup saying idna3.2 is installed (as one package require >2 and it picks the last available) but a later one require < 3 (this could be removed because python2 support has been dropped).

workaround was:
./bin/pip uninstall idna
./bin/pip install idna==2.10
and relaunch the last step:
./bin/python setup.py develop --upgrade
and continue the rest of the upgrade process:
make

Is there any chance you can figure out what package is requiring idna 3.2?

Looking at our CI builds for Debian Bullseye and Fedora 33, I'm seeing not seeing any errors during install and can see they have idna==2.10 (there's a pip freeze call part-way through the build logs to list package versions).

​https://builds.sr.ht/~mediagoblin/job/570699
​https://builds.sr.ht/

These are intended to closely mimick the deployment docs, so if you can find any differences, I'd consider that to be a bug.

2) on the last upgrade process we have to upgrade the db:
./bin/gmg dbupdate
this fails because jsonschema.compat is not found

This should now be fixed in the master branch. Please let us know if you have further issues.

Regards,
Ben

[Ben Sturmfels]

Hi TmCTux,

I'll close this issue now, but please do let me know if it's still persisting. I'd be glad to investigate if so.

Regards,
Ben

[Ben Sturmfels]

Hi TmCTux,

I'll close this issue now, but please do let me know if it's still persisting. I'd be glad to investigate if so.

Regards,
Ben

[TmCTux]

Hello Ben,

I don't mind this being closed, it's probably fixed by now, I anyway found a workaround to make the install successful, it was more to share and to maybe give hints if someone stumble on the same issue.

for 1) I think it came from lib/python3.7/site-packages/dnspython-2.1.0-py3.7.egg/EGG-INFO/requires.txt:idna>=2.1
so last version was installed, which was 3.2
and later on we have: lib/python3.7/site-packages/requests-2.25.1-py3.7.egg/EGG-INFO/requires.txt:idna<3,>=2.5
which fails because 3.2 is already installed.
as I said, forcing the installation of idna2.10 was the solution, but it wasn't done by itself.

2) great!

thanks again!
take care,
Tmc