-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Can't launch Sabnzbd on DSM 6.2.4-25556 Update 7 #5990
Comments
@th0ma7, this issue seems very similar to #5841. The challenge I see is that this user has tested with both of the two available versions of
Should this have worked before on ARMv5 platforms? Based on the log above, it did seem to work with |
It was a bad idea to install Python 3.11.4 for ARMv5. We intentionally deleted the ARMv5 packages for Python 3.11 - it is not supported on this platform (cryptography wheel i.e. SSL is not supported for ARMv5 toolchains). |
@hgy59, from the logs above the user never installed |
@Safihre we should delete the 88f6281 packages in the repository for sabnzbd depending on python311 (i.e. sabnzbd > 3.7.0-58). |
oops, you are right. thought it is related to your comment in #5841 (comment) |
I see... two issues:
Now that all packages have been migrated to python311, I could probably publish a "one-of" update for armv5 only of python310 for legacy reasons? It may be possible to jump back right before 941d41a and from there on a local repo, re-sync updates to openssl1.x and python310 and publish. but that state of code would never be merged back to master (or could be merged as branch, but what for?) I could potentially have a look at it after I close the qoriq issue (getting there, i hope) while finally working on the next set of python package upgrades to do that all at once ... |
@th0ma7 thanks for clarification. I was not aware that the cryptography issue occurred when updating openssl from 1.1 to 3.1. This said, what about python311 packages for ARMv5 with cross/openssl instead of cross/openssl3? |
But for Python 3.10 we still have ARMv5 packages with openssl3... 😕 |
What if:
And republish latest updates of packages? |
hey @th0ma7, would you be considering that for |
probably both... ? actually yes, and further it would (in theory) allow:
|
Is this a new Bug?
Package Name
Sabnzbd
Package Version
3.7.0-58
Device Model
DS213
Device Architecture
ARMv5
Firmware Version
DSM 6.2.4-25556 Update 7
What happened?
I have a small problem with a Synology DS213. I turned it off for a while (2 years). Now I want to start using it again, but won't install SABNZBD.
I found out that for the new update of SABNZBD, I need python 3.11 which my NAS no longer supports. So I started trying to install the older versions (3.7.0-58). Unfortunately, on execution I get: 'could not run the package service'.
I tried installing newer versions of SABNZBD, but it won't install my system because my system doesn't support python 3.11.
I am running the following version of DSM: DSM 6.2.4-25556 Update 7
Have any of you had a similar problem before and especially the question how can I solve this. It seems to me that surely I should be able to run an older version of SABNZBD.
I would love to hear about it.
Reproduction steps
...
Install Log
Service Log
Other Logs
The text was updated successfully, but these errors were encountered: