[ QSickRage ] [ 9.3.81 ] SickBeard PVR Fork

[LennyM]

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

[teroan]

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

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.

[LennyM]

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

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.

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

[teroan]

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?

[LennyM]

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?

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

[LennyM]

It looks that the correct repo is now being renamed to SickChill to not confuse anyone any further.

https://github.com/SickChill/SickChill

[LennyM]

Hi,

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

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

Best regards
Lenny

[teroan]

Hi,

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

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

Best regards
Lenny

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

[QoolBox]

guess it needs a separate package for sickchill

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

[LennyM]

guess it needs a separate package for sickchill

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

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