Search found 5 matches
- May 31st, 2013, 8:25 pm
- Forum: General Help
- Topic: git repo update delay?
- Replies: 5
- Views: 2031
Re: git repo update delay?
Gotchya. Thank you very much for getting back to me, and thanks for contributing to an awesome project.
- May 31st, 2013, 2:26 am
- Forum: Debian/Ubuntu Package
- Topic: Sabnzbd + sickbeard post processing permissions issues
- Replies: 2
- Views: 5176
Re: Sabnzbd + sickbeard post processing permissions issues
not sure if this is the proper way to do it, but I have sabnzbd write out all my files at 777 (sabnzbd:sabnzbd, Config > Folders menu), then have a cron that scrubs through my TV directory and correct everything every night. If you're not familiar with cron, you can just throw the below into a file ...
- May 31st, 2013, 2:14 am
- Forum: General Help
- Topic: git repo update delay?
- Replies: 5
- Views: 2031
Re: git repo update delay?
I just found the mention of the gitflow model. Is this the cause of the discrepancy? Or should I just checkout the 0.7.x branch? Looks like that one was updated when the tarball was.
Edit: actually looks like the 0.7.x branch is the same version.
Edit: actually looks like the 0.7.x branch is the same version.
- May 31st, 2013, 2:12 am
- Forum: General Help
- Topic: git repo update delay?
- Replies: 5
- Views: 2031
Re: git repo update delay?
The one listed here:
http://sourceforge.net/projects/sabnzbd ... z/download
The git repo appears to be on version 0.7.11 (which matches my client), where the tarball is 0.7.12
http://sourceforge.net/projects/sabnzbd ... z/download
The git repo appears to be on version 0.7.11 (which matches my client), where the tarball is 0.7.12
- May 31st, 2013, 2:04 am
- Forum: General Help
- Topic: git repo update delay?
- Replies: 5
- Views: 2031
git repo update delay?
I recently switched my installation from the typical tarball extraction to a clone of the git repo, in order to keep it in line with the rest of the nzb related daemons I have running, and for easier updating. However, since doing so my client has reported an update is available, but a git pull repo...