Can't launch Sabnzbd on DSM 6.2.4-25556 Update 7 about spksrc HOT 11 OPEN

@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 python310 in our repo but is getting the following message on install:

WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.

Should this have worked before on ARMv5 platforms? Based on the log above, it did seem to work with python310 3.10.4-9 (#5171).

from spksrc.

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).

from spksrc.

@hgy59, from the logs above the user never installed python311. This launch failure was with python310.

from spksrc.

@Safihre we should delete the 88f6281 packages in the repository for sabnzbd depending on python311 (i.e. sabnzbd > 3.7.0-58).

from spksrc.

@hgy59, from the logs above the user never installed python311. This launch failure was with python310.

oops, you are right. thought it is related to your comment in #5841 (comment)

from spksrc.

I see... two issues:

1. openssl 3.x migration of python 3.10 shouldn't be made available to armv5 - packages needs to be deleted
2. and yup, older version pre-openssl3 migration got deleted somehow ...

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 ...

from spksrc.

@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?

from spksrc.

But for Python 3.10 we still have ARMv5 packages with openssl3... 😕

from spksrc.

What if:

openssl/
├── openssl1 (if armv5)
└── openssl3 (else)

And republish latest updates of packages?

from spksrc.

hey @th0ma7, would you be considering that for python310 and python311 or just the former? Also, would that same workaround be useful for qoriq?

from spksrc.

probably both... ?

actually yes, and further it would (in theory) allow:

1. re-publishing all armv5 "compatible" packages
2. re-publishing all currently broken qoriq packages

from spksrc.