-
-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | pip2 pulls wheels from Python3-only repo #3346
Comments
In case it helps:
|
@tanderson1992
The error is that for a strange reason the setuptools package pulled by Python2 |
Good to know, thank you for checking it out so quickly. |
@tanderson1992
In the
Hence no other setuptools is pulled, as 44.0.0 has been installed before. Could you paste your two blocks? In your case its somehow pulling setuptools 45.0.0 (not available in my case) as a dependency, which is as well different in my case. On ARM and x86_64 things are can be different, since on ARM most modules need to be compiled. As a quick fix, actually the following should work:
The APT package ships v40.8.0, hence pip does not need to pull any other version. |
Here's the pip install:
And here's sabnzbd (after sucessfully installing unrar):
At the end, part of the system shows that sabnzbd is installed (shows up in services, every install starts with "[ OK ] DietPi-Services | stop : sabnzbd" even though the service isn't running. Part of the system thinks it's not installed (for example, if I run re-install 139 it says 139 wasn't already installed). |
I ran the two commands you specified above. As I mentioned, the system doesn't think sabnzbd was installed, so it informed me it couldn't re-install it. I used the standard install command after successfully running |
not sure if this is relevant but it seems using cached files on the installation run of @tanderson1992
This was not the case on the run @MichaIng did
|
I think it's using cached files because I attempted the download multiple times, and those files were already available. It seems like sometimes it re-downloads files (install.py, for example) while others it uses the cache. I haven't used an apt system in ages. Would deleting the cache and trying to install again make a difference? |
@tanderson1992
|
Tested again on RPi, result is exactly the same as on VM:
|
That and a fresh install of sabnzbd looks like it worked fine. Thank you again for looking over this. I'm not sure why it failed on my fresh install but works well for you on RPi. |
As said, my guess is a temporary wrong or faulty upload/state of the pip repository that has been fixed until I ran the install tests. The pip cache then conserved this faulty module. |
Marking this as closed. Feel free to reopen if required. |
@MichaIng
I was able to overcome the situation by installing Markdown 3.1.1 manually once stuck on SABnzbd software installation.
afterwards SABnzbd installation could be restarted and finished successfully |
@Joulinar |
Ah and similar to above, since pip caches everything, after running in such error one should always purge the cache before retrying: |
@MichaIng
|
@Joulinar |
And btw in my case again it pulls correct Markdown 3.1.1 automatically:
So might the bug again be solved already? |
@MichaIng |
@MichaIng Buster VM:
Buster RPi3B+
|
@Joulinar
So this must not be used by Python2... Could you try:
|
Bug reported to pypa: pypa/pip#7842 @Joulinar
That https://www.piwheels.org/simple is inside the indexes while Python version is 2.X is the core of the issue, as well with |
Not a new issue, known to pywheels.org maintainers already: piwheels/piwheels#208 |
The wheels for newest Markdown have been removed from piwheels repo, which should resolve the issue. I'll run some test on RPi later to verify. So basically there is another layer to mark/derive wheels compatibility, i.e. the |
Creating a bug report/issue
Required Information
Additional Information (if applicable)
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
The SABnzbd service also shows a status of FAILED, and it won't start, most likely due to the initial install failure.
The text was updated successfully, but these errors were encountered: