Hi Daniel (2021.06.14_13:48:37_-0400)
> Turns out there is a file
> ~/.local/share/virtualenv/wheel/3.9/embed/1/setuptools.json with the
> following content:
>
> {
> "completed": "2021-05-17T17:34:03.491147Z",
> "periodic": true,
> "started": "2021-05-17T17:33:59.488436Z",
> "versions": [
> {
> "filename": "setuptools-56.2.0-py3-none-any.whl",
> "found_date": "2021-05-17T17:33:59.597757Z",
> "release_date": "2021-05-09T17:40:49.000000Z"
> },
> {
> "filename": "setuptools-56.1.0-py3-none-any.whl",
> "found_date": "2021-05-17T17:34:01.067885Z",
> "release_date": "2021-05-04T21:35:13.000000Z"
> },
> {
> "filename": "setuptools-56.0.0-py3-none-any.whl",
> "found_date": "2021-05-17T17:34:02.299115Z",
> "release_date": "2021-04-09T00:24:04.000000Z"
> }
> ]
> }
>
> Removing this file causes this problem to go away!
Aha. Yes, that looks like it may be our culprit.
Those setuptools versions are newer than the ones we use in pip in
Debian, we are still using 44.1.1, for compatibility with Python 2.7.
So, those must have come from the Internet.
Setuptools from the internet will also contain pkg_resources, which is a
separate package in Debian.
Which lead me to find the bug in debian_update_for_available_wheels.patch
It assumes that we're only using data from the internet if "--download"
is passed. However, once it has been updated with
"--upgrade-embed-wheels", it'll be used, even without "--download".
Thanks, again!
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
