Page 2 of 2
Re: Problem Starting Up SAB on Debian
Posted: February 6th, 2011, 4:20 pm
by WarezMyGF
shypike wrote:
The file sabnzbd/utils/__init__.py is part of the tar.gz distribution.
I have my doubts about your unpacking program.
I am using 7-Zip, extract and fully send it over FTP which does crc check. It can't be the unpacking program.
Re: Problem Starting Up SAB on Debian
Posted: February 7th, 2011, 2:43 am
by shypike
Well, you need the __init__.py file and it is in the distribution tarbal.
It's an empty file (0 bytes), maybe that explains why you have problems with it?
Re: Problem Starting Up SAB on Debian
Posted: February 7th, 2011, 3:32 am
by sander
WarezMyGF wrote:
shypike wrote:
The file sabnzbd/utils/__init__.py is part of the tar.gz distribution.
I have my doubts about your unpacking program.
I am using 7-Zip, extract and fully send it over FTP which does crc check. It can't be the unpacking program.
Apart from the cause, just create the empty file with something like
Then check the file exists (with size 0). Then run SAB.
Re: Problem Starting Up SAB on Debian
Posted: February 9th, 2011, 12:24 pm
by WarezMyGF
Thanks for the input so far.
I am going to try the new Alpha 11. What is the proper way to upgrade in linux?
Thanks!
Re: Problem Starting Up SAB on Debian
Posted: February 9th, 2011, 7:05 pm
by john3voltas
You might not want to upgrade.
Since SAB+ has many dependencies, you should consider simply having 0.5.6 and 0.6.0A1x on your system at the same time.
That's what I've been doing.
Simply download the SABnzbd-0.6.0Alpha12-src.tar.gz.
Extract that file to an appropriate place.
Using the shell, CD'into the folder where you extracted SAB+'s Alpha and run ./SABnzbd/SABnzbd.py (watch the leading dot).
The Alpha is really stable but it's still an alpha.
So backup your queue in case something goes wrong
.
Cheers
Re: Problem Starting Up SAB on Debian
Posted: February 10th, 2011, 6:42 am
by shypike
Please note that 0.6.0 will upgrade the sabnzbd.ini file
so that 0.5.6 cannot use it anymore.
You should use separate INI files.