Page 1 of 1

Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: March 20th, 2010, 6:21 am
by sander
Hi,

Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12, not SAB 0.5.0

Is it still possible to get 0.5.0 into Ubuntu 10.04, or is it too late?

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: March 20th, 2010, 8:36 am
by jcfp
Currently awaiting sponsorship in debian (for sabnzbdplus as well as the required version of cherrypy3). So work in progress, no guarantees though as I'm simply not in control of the uploading to the distros.

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: March 20th, 2010, 12:05 pm
by sander
And Ubuntu 'inherits' SAB from Debian?


About cherrypy3: is the standard cherrypy on Ubuntu still 2.x? http://packages.ubuntu.com/lucid/python-cherrypy

I did this:
1) Installed SABnzbdplus from the standard Ubuntu repository to get the needed libraries
2) Downloaded SABnzbd-0.5.0-src.tar.gz , and run that.

Does that mean I use the cherrypy (3?) included in SABnzbd-0.5.0-src.tar.gz, and not the cherrypy (2?) from the standard Ubuntu repository?

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: March 21st, 2010, 6:02 am
by jcfp
sander wrote:And Ubuntu 'inherits' SAB from Debian?

Does that mean I use the cherrypy (3?) included in SABnzbd-0.5.0-src.tar.gz, and not the cherrypy (2?) from the standard Ubuntu repository?
Yes to both. There's a python-cherrypy3 package too, but it's not yet new enough for 0.5.0 to work with.

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: March 23rd, 2010, 4:09 am
by shypike
CherryPy is a constant headache for use.
We use an interim 3.2.0 release with a couple of patches.

2.x releases are totally incompatible.
With 3.1.0 https is simply unusable and is incompatible.
3.2.0RC1 contains another serious https bug and is again incompatible
with what we use.

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: April 13th, 2010, 9:27 am
by jcfp
0.5.0 is in lucid/10.04 now, with the cherrypy3 code that comes with the program releases included in the package.

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: April 13th, 2010, 1:47 pm
by sander
jcfp wrote: 0.5.0 is in lucid/10.04 now, with the cherrypy3 code that comes with the program releases included in the package.
Wow! Thank you!

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: April 30th, 2010, 3:55 am
by sander
I'm now on Ubuntu 10.04, and trying to install SABnzbd, I got the message below

After enabling Universe (or Multiverse?), everything was OK.


Code: Select all

ubuntu@ubuntu:~$ sudo apt-get install sabnzbdplus
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  sabnzbdplus: Depends: python-feedparser but it is not installable
               Depends: sabnzbdplus-theme-smpl (= 0.5.0-2) but it is not going to be installed
               Recommends: python-yenc (>= 0.3) but it is not installable
               Recommends: par2 (>= 0.4) but it is not installable
E: Broken packages
ubuntu@ubuntu:~$



Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: April 30th, 2010, 9:09 am
by jcfp
sander wrote:After enabling Universe (or Multiverse?), everything was OK.
No surprise there, to get those errors you must have had multiverse enabled but not universe. That is asking for trouble, since any package is free to have dependencies from both their own and 'higher' repositories (with "main" being top level).

Re: Ubuntu 10.04 Beta1 still has SABnzbd+ 0.4.12

Posted: April 30th, 2010, 3:22 pm
by sander
jcfp wrote:
sander wrote:After enabling Universe (or Multiverse?), everything was OK.
No surprise there, to get those errors you must have had multiverse enabled but not universe. That is asking for trouble, since any package is free to have dependencies from both their own and 'higher' repositories (with "main" being top level).
Yeah, I know. I just posted this because the (error) message looks different than in earlier Ubuntu versions. However, I might be wrong about that.