New sickrage repo?

[Supa]

I'm just wondering if we'll have to change anything on our ends...

https://github.com/SickRage/SickRage

http://pastie.org/private/m7lryrqqihyeyl1supuepq

https://github.com/SickRage/SickRage.git

 

[Joshua Parker Ruehlig]

Interesting news.

yes, you could replace your source at /usr/pbi/sickrage-amd64/share/sickrage
Or, I'll package up the new repo and issue an update to the sickrage plugin.

 

[ThomasDK81]

I don't know if a change is the right solution. I've tried to read up on the treads and I don't know who is the most reliable at the moment.
Both sides have arguments and money seems to be a big part of the problem.

My point is, do we change?
Joshua, if you do, you'll make the decision for a lot of people. Just saying, not pointing fingers :)
I my self is leaning to the new repository.

 

[INCSlayer]

Not really having looked into the "politics" of this i dont really care if we stay with the old or go with the new what i care about is that its stable and working

EDIT: i will say this though i think its a bit bad to keep the name the same since it was started by Echelon they should pick a new name in my opinion

 

[9C1 Newbee]

What is there to gain by switching?

Is it possible to have two plugins with both flavors?

 

[Joshua Parker Ruehlig]

whenever I looked into the commits for SickRage recently it was mostly miigotu and others, not echel0n. but I think its smart we give this a few days to shake out and seen if things are resolved. also, agree a new name is needed. is tvrage even around anymore?

 

[INCSlayer]

whenever I looked into the commits for SickRage recently it was mostly miigotu and others, not echel0n. but I think its smart we give this a few days to shake out and seen if things are resolved. also, agree a new name is needed. is tvrage even around anymore?

So its been a few days any plans for how your gonna proceed?

 

[Joshua Parker Ruehlig]

So its been a few days any plans for how your gonna proceed?

gonna use the new repo unless someone has a good reason not too. I'll do it in a few days

 

[Joshua Parker Ruehlig]

So its been a few days any plans for how your gonna proceed?

gonna use the new repo unless someone has a good reason not too. I'll do it in a few days

 

[ggoldfingerd]

I don't see any reasons. I need to update soon to see if my issues are resolved.

 

[Joshua Parker Ruehlig]

I don't see any reasons. I need to update soon to see if my issues are resolved.

got delayed a bit because autoupdate wasnt working with the new repo and freenas. Dev says fix is coming soon

 

[Wanderer89]

I've just been catching up on recent events, my SR auto-updated (within the app via git) a few days ago, but the web front end became unresponsive, though it appears to still be running in the background.

Anyway, noticed an update in the freenas plugin gui, and thought that might be related so applied it; but even after applying it the front end becomes responsive after a few minutes. I'm still tracking down what's going on in the debug logs.

But before I fix this, freenas plugin seems stuck trying to update back and forth between 9.3.3 and 9.1_autoupdate template versions of SR, which one should I be using? I agree sticking with the new org seems like the way to go... really maybe they should change their name to make it easier.

Or just wait this out a bit longer?

e: I see autoupdate.9_1 points to the new repo, but it's not able to connect to repo to check for updates right now.

 

[Joshua Parker Ruehlig]

I've just been catching up on recent events, my SR auto-updated (within the app via git) a few days ago, but the web front end became unresponsive, though it appears to still be running in the background.

Anyway, noticed an update in the freenas plugin gui, and thought that might be related so applied it; but even after applying it the front end becomes responsive after a few minutes. I'm still tracking down what's going on in the debug logs.

But before I fix this, freenas plugin seems stuck trying to update back and forth between 9.3.3 and 9.1_autoupdate template versions of SR, which one should I be using? I agree sticking with the new org seems like the way to go... really maybe they should change their name to make it easier.

Or just wait this out a bit longer?

e: I see autoupdate.9_1 points to the new repo, but it's not able to connect to repo to check for updates right now.

I was able to get autoupdate to work. I might have had to restart sickrage and try it a few times.

they do plan on changing the name, there's an issue on github somewhere to pick a new name.

 

[delfrogo]

I just manually switched to the new repo and it fixed a postproccesing error with a long html code in the sab log that i've been having.

Here is what I did.

1. Just stop sick rage:

Code:

service sickrage stop

2. backup these 3 files in /var/db/sickrage (failed.db, config.ini, sickbeard.db)
3. Also delete the cache.db in the same folder. It will just gen up a new one.
4.Move to a tmp folder and download the zip from the github.

Code:

cd /tmp
git clone git://github.com/SickRage/SickRage.git 

5. Delete the old SickRage folder.

Code:

rm -R /usr/pbi/sickrage-amd64/share/sickrage/SickRage 

6. Copy the newly downloaded SickRage folder from the tmp folder to the one you just deleted.

Code:

cp -R /tmp/SickRage /usr/pbi/sickrage-amd64/share/sickrage/

7. Fire up sickrage and access it via the gui. Make sure it works and then shut it down again.
8. Copy those 3 files (failed.db, config.ini, sickbeard.db) back to the /var/db/sickrage folder.
9. start sickrage again and make sure everything is working.

I just did this and it's working for me. I tried doing an update, but it says im up-to-date.

 

[overthinkingme]

I used an old post by Joshua to update and it worked well too. I just updated the repo url.

Code:

rm -r /usr/pbi/sickrage-amd64/share/sickrage/SickRage
fetch --no-verify-peer "https://github.com/SickRage/SickRage/archive/master.tar.gz"
tar xzf master.tar.gz
mv SickRage-master /usr/pbi/sickrage-amd64/share/sickrage/SickRage
chown -R media:media /usr/pbi/sickrage-amd64/share/sickrage/SickRage
rm master.tar.gz

EDIT: auto update does not work with this method.

Code:

CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

 

[Joshua Parker Ruehlig]

I used an old post by Joshua to update and it worked well too. I just updated the repo url.



EDIT: auto update does not work with this method.

Code:

CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

hmm, not sure why this wouldn't work. it should pull down the latest commit, then store the version somewhere to reference.

I used the update button on the Plugins >Installed tab and after clicking the check version/update button on the SR home screen I'm able to see I'm on the latest commit. did you stop SR before running those commands?

 

[overthinkingme]

hmm, not sure why this wouldn't work. it should pull down the latest commit, then store the version somewhere to reference.

I used the update button on the Plugins >Installed tab and after clicking the check version/update button on the SR home screen I'm able to see I'm on the latest commit. did you stop SR before running those commands?

Hi Joshua,

Yeah, I stopped SR via terminal before running commands.
Also, I did not use freenas gui to attempt update, I checked for update within SR. Error I listed is from SR.
I noticed that when I used the method I posted here the resulting Sickrage directory doesn''t contain a .git and cannot git pull.
Not sure if that's relevant.

Anyway, using the git clone method SR does not report the error.
Thanks for the awesome plugins.

 

[Joshua Parker Ruehlig]

Hi Joshua,

Yeah, I stopped SR via terminal before running commands.
Also, I did not use freenas gui to attempt update, I checked for update within SR. Error I listed is from SR.
I noticed that when I used the method I posted here the resulting Sickrage directory doesn''t contain a .git and cannot git pull.
Not sure if that's relevant.

Anyway, using the git clone method SR does not report the error.
Thanks for the awesome plugins.

the steps you listed doesn't use git, it's the "source install/update" method. glad you got it working

 

[INCSlayer]

I have the same issue with sickrage after updating from the freenas plugin page

CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

 

[Joshua Parker Ruehlig]

I have the same issue with sickrage after updating from the freenas plugin page

CHECKVERSION :: Unable to contact github, can't check for update: UnknownObjectException()

did you update the plugin or do the steps people are posting? can you guys also confirm you can ping github.com?