Update sabnzbd and couchpotato.

[Keon91]

Hi  Joao,

I found out that there is a new update of Sabnzbd.

Can you update the package to 0.7.3?

http://sabnzbd.org/download/ 

do you still recommend installing nzbget instead of Sabnzbd?

Also the development of CouchPotato has stopped.

Now there is a new version out called : CouchPotatoServer.

Can you update the CouchPotato package to the new CouchPotatoServer version or make a new package?

https://github.com/RuudBurger/CouchPotatoServer 

Thanks!

[Keon91]

 Hi Joao,

 I also have a qnap nas and a dev from the package tread made a package for sabnzb which is a wrapper.

 On very start it does a git pull so you always have the latest version of sabnzbd.

 More info : http://forum.qnap.com/viewtopic.php?f=133&t=41670

 Maybe something like this would also be appropriate for couchpotatoserver

Op dinsdag 14 augustus 2012 17:00:43 UTC+2 schreef Keon91 het volgende:

[Joao Cardoso]

On Tuesday, August 14, 2012 4:00:43 PM UTC+1, Keon91 wrote:

Hi  Joao,

I found out that there is a new update of Sabnzbd.

Can you update the package to 0.7.3?

Sure, attached, untested and instrutions bellow.

[edited: sorry, the Sabnzbd package in this post is wrong, use the one from the next post]

http://sabnzbd.org/download/ 

do you still recommend installing nzbget instead of Sabnzbd?

From a memory perspective, yes, nzbget has a *much* smaller memory footprint then sabnzbd, and that makes a difference.

From a configuration point of view, sabnzbd is easier and nzbget harder, because it depends on also setting up the lighttpd web server used by nzbgetweb, which has an older and (apparently) complex user interface. 

Also the development of CouchPotato has stopped.

Now there is a new version out called : CouchPotatoServer.

Can you update the CouchPotato package to the new CouchPotatoServer version or make a new package?

Also attached as couchpotato2, and can coexist with couchpotato, if I remember correctly.

As a matter of fact I have updates to SickBeard and Couchpotato build since some time now, but there might exist problems upgrading from existing installations, that's the reason why I have not released them.

I ask users that have SickBeard and Couchpotato installed to wait for their current downloads to finish and them to upgrade to the attached versions and report any problems.

As now there are two downloaders available, sabnzbd and webget, configuration is not as automatic as before.

Releasing in the habitual way, using the web interface, will depend on users feedback, as I don't have the time to test everything.

To install, download the packages to a folder in the box and they type as user 'root' in the command line

   ipkg install <path to package>

To remove,

      ipkg remove pkg_name # e.g., "ipkg remove sabnzbd"

nzbget users should start upgrading lighttpd, then nzbgetweb than nzbget

sabnzbd users should upgrade sabnzbd

sickbeard and/or couchpotato users should then upgrade sickbeard and/or couchpotato

   

After installing, the *.ipk files can be removed.

Please report back any issues and

Thanks

https://github.com/RuudBurger/CouchPotatoServer 

Thanks!

[Joao Cardoso]

On Wednesday, August 15, 2012 4:45:56 PM UTC+1, Joao Cardoso wrote:

On Tuesday, August 14, 2012 4:00:43 PM UTC+1, Keon91 wrote:

Hi  Joao,

I found out that there is a new update of Sabnzbd.

Can you update the package to 0.7.3?

Sure, attached, untested and instrutions bellow.

The  Sabnzbd package from the previous post is in error, use this one instead.

[Keon91]

Sabnzbd and Sickbeard seem to work.

Only the user script dir isn't set anymore in sabnzbd.

so the sabtosickbeard script didn't work.

I will report if I find any more issues

Thanks!

Op dinsdag 14 augustus 2012 17:00:43 UTC+2 schreef Keon91 het volgende:

[Joao Cardoso]

On Wednesday, August 15, 2012 4:39:47 PM UTC+1, Keon91 wrote:

 Hi Joao,

 I also have a qnap nas and a dev from the package tread made a package for sabnzb which is a wrapper.

The sabnzbd/couchpotato/couchpotato2/sickbeard packages are just scripts that downloads and installs the real thing, as you can "see" from the packages file size, so it seems to be the same approach used in the qnap package.

 On very start it does a git pull so you always have the latest version of sabnzbd.

As  couchpotato/couchpotato2/sickbeard don't have release yet, they are alpha, the download step uses the last available setup "master". Afterwards you can use theirs own configuration web page to update them.

sabnzbd has releases, so I prefer to use them, as there are more guarantees of "fitness".

I'm not a regular user of that programs, but I think to remember that in one of them a 'git update' option appeared when I installed the 'git' package. Can you install it and report back?

[Joao Cardoso]

On Wednesday, August 15, 2012 8:31:01 PM UTC+1, Keon91 wrote:

Sabnzbd and Sickbeard seem to work.

Have you upgraded an existing installation ("ipkg install" on an existing install is in reality an upgrade)  or just installed the new versions?

Only the user script dir isn't set anymore in sabnzbd.

so the sabtosickbeard script didn't work.

Can you please give more details? I only used those programs to create the packages, and I don't remember the details anymore.

Thanks

[Keon91]

First I removed the Sabnzbd and Sick Beard packages using : ipkg remove sabnzbd and ipkg remove sickbeard.

then I installed the new ones using : ipkg instal <package_name>

Something I noticed was that after install Sick Beard couldn't connect to Sabnzbd (use as search provider)

Solved this by editting the sabnzbd.conf 

The host field was blank, changed it to : "0.0.0.0" . This solved the problem.

There is a script available for Sabnzbd to let sickbeard do the postprocessing.

This script is located in the opt/SickBeard/Autoprocess dir.

By default the dir isn't set in sabnzbd.

Not a big problem, you already mentioned that for the new packages more configuration was required.

Op woensdag 15 augustus 2012 22:29:11 UTC+2 schreef Joao Cardoso het volgende:

[Joao Cardoso]

On Thursday, August 16, 2012 8:10:37 AM UTC+1, Keon91 wrote:

First I removed the Sabnzbd and Sick Beard packages

ah. I wanted to test the "upgrade" path, i.e., doing an install over an existing instalation. Pitty.

 

using : ipkg remove sabnzbd and ipkg remove sickbeard.

then I installed the new ones using : ipkg instal <package_name>

Something I noticed was that after install Sick Beard couldn't connect to Sabnzbd (use as search provider)

Solved this by editting the sabnzbd.conf 

The host field was blank, changed it to : "0.0.0.0" . This solved the problem.

I used the documentation:

Host: Change to 0.0.0.0 or leave it empty (auto-finds local ip address) to be able to access from other pcs in your network. (...)

empty = Finds and listens on your local (ipv4) ip address. Used for accessing from other computers.

I will use 0.0.0.0 as default.

There is a script available for Sabnzbd to let sickbeard do the postprocessing.

This script is located in the opt/SickBeard/Autoprocess dir.

By default the dir isn't set in sabnzbd.

Have you used the SickBeard/Sabnzbd Alt-F web page to setup them? Because when hitting the Submit button in either the copy is done:

# copy SickBeard postprocess script to SABnzbd

# autoProcessTV.cfg must be edited by the user if he adds a password to SAB/Sick

Not a big problem, you already mentioned that for the new packages more configuration was required.

I thought in adding a "Use Sabnzbd/Use nzbget"  button in both the Alt-F sickbeard/couchpotato web pages, in order to automate the instalation, what do you think?

[Keon91]

Sabnzbd is now on 0.7.6, can you update your package?

Or maybe you can make an check for update function or something?

[Joao Cardoso]

On Tuesday, December 4, 2012 12:28:53 PM UTC, Keon91 wrote:

Sabnzbd is now on 0.7.6, can you update your package?

Done.

 

Or maybe you can make an check for update function or something?

Yes, also done, thanks for the suggestion.

There is hidden code that shows the last available version, but it is too slow to download the data, so I have disabled it.

Do you know if Couchpotato/Couchpotato2/SickBeard built-in update functions work OK? Or do I have to do something similar to Sabnzbd?

[Keon91]

The new sabnzbd update works great! 

I really like how you implemented the update tunction, thanks!

The build-in update function from  Couchpotato/Couchpotato2/SickBeard work just fine.

I don't really know how the SickBeard package works, does it download the latest release on first instal?

If this is not the case, maybe you can update the package so the new config is implemeted:

Related issue: https://groups.google.com/forum/#!topic/alt-f/O_HbO4W29Jc

[Joao Cardoso]

On Friday, December 14, 2012 10:48:06 AM UTC, Keon91 wrote:

The new sabnzbd update works great! 

I really like how you implemented the update tunction, thanks!

The build-in update function from  Couchpotato/Couchpotato2/SickBeard work just fine.

I don't really know how the SickBeard package works, does it download the latest release on first instal?

As there are yet no releases, the current "master" development is downloaded and used. Odd that it says the the version is unknown...

The same download procedure is used with both couchpotato and couchpotato2

 

If this is not the case, maybe you can update the package so the new config is implemeted:

Related issue: https://groups.google.com/forum/#!topic/alt-f/O_HbO4W29Jc

ah, fixed, and an updated package is now available.

The issue was that sickbeard wanted to made a backup of its configuration file, but it has no permissions to write in /etc, so the backup fails.

The updated package uses /etc/sickbeard as the configuration folder, and as it belongs to the sickbeard user the backup file can now be created.

At package update time the old /etc/sickbeard.conf, if it exists, is copied to /etc/sickbeard/sickbeard.conf, preserving your settings. Everything else is maintained.

 

Thanks,

João

[Keon91]

I've updated the sickbeard package and it's stil working fine!

The sickbeard.conf location has indeed changed tot /etc/sickbeard/

Thanks!