Upgrading to Fedora 30 broke my Sabnzbd

[zugzwang]

New users are not allowed to post links, so I paraphrase links in this query.

Upgrading to Fedora 30 broke my Sabnzbd.

I strongly suspect that the problem is that I have multiple copies of python. I suspect that because of this, I am not correctly sync'g sabyenc, the correct version of python, and sabnzbd. Assuming that this is so, although I am reasonably comfortable in bash, I found the instructions re multiple copies of python sparse and confusing. Request help: details below.

From the nuxref-repository at nuxref-com, I downloaded and then installed the rpm for nuxref-release version 1.0.0-4.fc30-nuxref-noarch-rpm.

Then : $ sudo dnf install sabnzbd

Last metadata expiration check: 1:05:40 ago on Fri 27 Dec 2019 12:42:49 AM PST.
Error:
Problem: conflicting requests
- nothing provides python-yenc needed by sabnzbd-2:2.3.5-1.fc27.nuxref.noarch
- nothing provides python-yenc needed by sabnzbd-2:2.3.3-1.fc27.nuxref.noarch
- nothing provides python-yenc needed by sabnzbd-2:2.3.2-1.fc27.nuxref.noarch
(try to add '--skip-broken' to skip uninstallable packages)

I reviewed the github link at sabnzbd/sabnzbd/issues/1039 but I am not savvy enough to correct the problem without hand-holding.

On the sabnzbd-org wiki/installation/sabyenc.html page, within the "Multiple installations of python" section, I found

/path/to/correct/python -m pip install sabyenc

I then tried $ /bin/python3.7 -m pip install sabyenc

That command resulted in (bash terminal) messages that I do not understand, some of which referred to errors.

I then executed $ python -c "import sabyenc ; print sabyenc.__version__ "

Result: 3.3.1

I then re-executed : $ sudo dnf install sabnzbd

No joy, same error messages as before.

[sander]

If you're using the standard SABnzbd version, you must use python2 (aka python), but NOT python3

[zugzwang]

sander, thanks for the reply. Unfortunately, I am not savvy enough to know what to do, based on your reply. Could you please be more explicit re what bash commands that I should execute to remedy not being able to use sabnzbd. Also:

1. If I remember correctly, I originally errored on sudo dnf install sabnzbd , and only then looked to install python3.

2. Isn't python2.7 going to reach end-of-life next January.

3. Can I remedy this by going to a newer version of sabnzbd and then using it with python3.

Anyway, I request explicit instructions. Thanks.

[sander]

Anyway, I request explicit instructions. Thanks.

Sorry, can't help you with that.

[safihre]

Maybe you can do the dnf with the skip broken ones so it ignores the yenc depencies? Since you already have it.

We are working on a Python 3 version, just needs some finishing and more alpha/beta testing.

[zugzwang]

"...dnf with the skip broken ones..."

Thanks for the interest, nice suggestion. Unfortunately, the idea failed... Details below.

1. sudo dnf install sabnzbd --skip-broken

Last metadata expiration check: ...
Dependencies resolved.

Problem: cannot install the best candidate for the job
- nothing provides python-yenc needed by sabnzbd-2:2.3.5-1.fc27.nuxref.noarch

Skipping packages with broken dependencies:
sabnzbd noarch 2:2.3.5-1.fc27.nuxref nuxref 2.5 M

Skip 1 Package

Nothing to do.
Complete!

2. sudo usermod -a -G sabnzbd steve

3. sudo systemctl start sabnzbd.service

Failed to start sabnzbd.service: Unit sabnzbd.service not found.

--------------------------------------------

"We are working on a Python 3 version..."

In the meantime, given that Fedora 30 came out about 7 months ago, what have
other Sabnzbd users done who upgraded from Fedora 29 to Fedora 30? Is Sabnzbd
currently unavailable for each of them?

What about Sabnzbd users who did a fresh install of Fedora 30, rather than trying
to upgrade. Is Sabnzbd currently unavailable for each of them?

[safihre]

I imagine just running from sources works just fine? Since you already have sabyenc.

[zugzwang]

"...just running from sources ..."

Very intriguing response, thanks again for the attention. If I understand correctly, I should open a bash terminal, navigate to the python2.7 bin directory, and then execute python2.7 <source-file.py>. If I understand correctly, "running from sources" replaces some of

1. sudo dnf install sabnzbd
2. sudo usermod -a -G sabnzbd steve
3. sudo systemctl start sabnzbd.service

I am a a retired professional programmer, a python total-newbie, and bash-semi-literate. Which of the above steps do I "run from source"? Also, how do I obtain the corresponding source file(s)?

Also, doesn't Fedora 30 use python3 in its package management? Should I first execute

/bin/python3.7 -m pip install sabyenc

so that Fedora 30's package management is not disrupted? Assuming so, is it dangerous to run a python2.7 script (via the python2.7 command) when the Fedora operating system regards python3 as "controlling"?

[safihre]

I think you should be able to just run
python /path/to/sabnzbd/SABnzbd.py
Usually "python" is already linked to Python 2, otherwise you can try "python2".
SABnzbd will start and tell you what it is missing.

To get the files you can download them from the Downloads page (Linux):
https://sabnzbd.org/downloads

[zugzwang]

Thanks again to safihre for the detailed support. I am going to keep the "run python from source" option in reserve. For other reasons, I have been forced to have a 2nd pc in another room that runs Windows 10, while my main pc is now running Fedora 30. Experimenting, I have found that the Windows-10_sabnzbd_installer works okay. Further experimenting, I have found that the free version of teamviewer (personal use only) works okay in both Windows 10 and Fedora 30. Therefore, my "functional" solution is to remotely control sabnzbd(Windows-10_pc) from my Fedora 30 pc.