QNAP [ QSickRage ] [ 9.3.81 ] SickBeard PVR Fork

Hi,

please change SickRage repo to https://github.com/Sick-Rage/Sick-Rage because of this again: https://github.com/Sick-Rage/Sick-Rage/issues/4984

Thanks
lenny
 
LennyM a dit:
Hi,

please change SickRage repo to https://github.com/Sick-Rage/Sick-Rage because of this again: https://github.com/Sick-Rage/Sick-Rage/issues/4984

Thanks
lenny
Cliquez pour agrandir...

Not sure if this is just a coincidence but my QSickRage installation isn't working as of today. Noticed some new update notification and something about version not set (or something similar). From QNAP it shows as "started" (Open) but is not reachable.
 
teroan a dit:
LennyM a dit:
Hi,

please change SickRage repo to https://github.com/Sick-Rage/Sick-Rage because of this again: https://github.com/Sick-Rage/Sick-Rage/issues/4984

Thanks
lenny
Cliquez pour agrandir...

Not sure if this is just a coincidence but my QSickRage installation isn't working as of today. Noticed some new update notification and something about version not set (or something similar). From QNAP it shows as "started" (Open) but is not reachable.
Cliquez pour agrandir...
yes it is related. You updated the repo.
This guy - link above - took over the the repo again (happend a couple of years ago as well). Basically it is ex repo owner vs. dev team.
Apparently he infused his repo/taken over repo with a bitcoin miner as well.....

QSickRage has to be changed to the new repo otherwise everyone who updates the installation won't work.
If you install QSickRage fresh, then you will have the taken over repo, with the possible bitcoin miner. So that's no option in my opinion.

Best regards
Lenny
 
Ah yes, i remember reading something about that back then. Well that sucks... hope this gets fixed. Any ideas if theres any manual workaround or do we need to do fresh install with correct repo?
 
teroan a dit:
Ah yes, i remember reading something about that back then. Well that sucks... hope this gets fixed. Any ideas if theres any manual workaround or do we need to do fresh install with correct repo?
Cliquez pour agrandir...

I think this should work. But I'm not sure if the github link actually updates the QSickRage package settings.

https://github.com/SickChill/SickChill/issues/5024#issuecomment-428277335

"
Hi,

I have the same problem.

I will do following, and it should work

reinstall QSickRage
don't update
stop qsickrage
go via ssh to /share/MD0_DATA/.qpkg/QSickRage/SickRage-master -> do as followed:
Edit config.ini
Replace "git_remote_url = https://github.com/SickRage/SickRage.git" with "git_remote_url = https://github.com/Sick-Rage/Sick-Rage.git"
Save config.ini
Restart Sickrage
then update
best regards
Lenny
"
 
It looks that the correct repo is now being renamed to SickChill to not confuse anyone any further.

https://github.com/SickChill/SickChill
 
Hi,

here is the temp solution to make QSickRage work with SickChill.
https://github.com/SickChill/SickChill/issues/5022#issuecomment-428712223

I will wait until the qpkg is updated, as I don't want to git clone within the installation.

Best regards
Lenny
 
LennyM a dit:
Hi,

here is the temp solution to make QSickRage work with SickChill.
https://github.com/SickChill/SickChill/issues/5022#issuecomment-428712223

I will wait until the qpkg is updated, as I don't want to git clone within the installation.

Best regards
Lenny
Cliquez pour agrandir...

Yes i'll wait for update as well unless it takes too long then i'll try to fix it. Thanks for the information!

P.S. Probably backing up the database files etc. is a good idea. These files under ".qpkg/QSickRage/SickRage-master"

sickrage/cache/*
cache.db
config.ini
failed.db
sickbeard.db
Cliquez pour agrandir...
 
QoolBox a dit:
guess it needs a separate package for sickchill

in case SickRage fixed this issue... i will update it to 9.0.80 anyway
Cliquez pour agrandir...

Hi,

SickRage was taken over by the roque developer. He infused his code from the sickrage tv repo, which wasn't under development from the team which your package is based on. The correct team renamed their repo to SickChill. Everyone who updates your package will destroy their installation.
Thus changing you package to SickChill will resolve that issue as it has the same commits.

Best regards
Lenny
 
just checked

there is new python package requirement missing in previous release

i will make a separate package for sickchill

Code: 
[/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master] # $PYTHON SiCKRAGE.py -p "29989" --datadir $QPKG_ROOT/DATAS --config $QPKG_ROOT/CONFIG/sickbeard.conf
Traceback (most recent call last):
  File "/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/sickrage/__init__.py", line 219, in main
    from sickrage.core import Core
  File "/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/sickrage/core/__init__.py", line 39, in <module>
    from keycloak.realm import KeycloakRealm
ImportError: No module named keycloak.realm
Failed to import required libs, please run 'pip install --user -U -r /share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/requirements.txt' from console
 
QoolBox a dit:
just checked

there is new python package requirement missing in previous release

i will make a separate package for sickchill

Code: 
[/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master] # $PYTHON SiCKRAGE.py -p "29989" --datadir $QPKG_ROOT/DATAS --config $QPKG_ROOT/CONFIG/sickbeard.conf
Traceback (most recent call last):
  File "/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/sickrage/__init__.py", line 219, in main
    from sickrage.core import Core
  File "/share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/sickrage/core/__init__.py", line 39, in <module>
    from keycloak.realm import KeycloakRealm
ImportError: No module named keycloak.realm
Failed to import required libs, please run 'pip install --user -U -r /share/CACHEDEV1_DATA/.qpkg/QSickRage/SiCKRAGE-master/requirements.txt' from console
Cliquez pour agrandir...
Hi,

I would recommend to make yourself familiar with the whole mess, which is going on about the old sickrage github repo (see posts before), before you might repair qsickrage and create possibly new qsickchill.
It's a big mess and alot of novice users will be sucked into it - i.e. possible background bitcoin mining.

Best regards
Lenny
 
What's the best way to migrate from SickRage to SickChill?

Would going to http://server-name:29989/config/backuprestore/ and create a backup there, while restoring in SickChill work?

What port is SickChill running out of by default? Also 29989?

P.S. if anybody wants to read up on the whole saga, here are two articles:
https://torrentfreak.com/ongoing-sickrage-dispute-descends-into-trademark-war-181008/
https://torrentfreak.com/sickrage-rebrands-to-sickchill-to-avoid-trademark-war-181027/
 
Vous devez vous connecter ou vous enregistrer pour répondre ici.
Haut Bas