Please update Octave to version 3.0.3 (intrepid/hardy)

Bug #287235 reported by Nicola Ferralis
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
octave3.0 (Ubuntu)
Fix Released
Wishlist
thisismalhotra
Declined for Jaunty by Steve Langasek

Bug Description

Binary package hint: octave3.0

Packages in Hardy/Intrepid are still in version 3.0.1. Upstream released 3.0.3 as pure bugfix release (no new features).

Packages in Hardy/Intrepid should be updated accordingly.

Upstream patches from 3.0.1 to 3.0.2 to 3.0.3 are attached.

Tags: upgrade
Revision history for this message
Nicola Ferralis (feranick) wrote :
Revision history for this message
Nicola Ferralis (feranick) wrote :
Revision history for this message
dino (adinov) wrote :

I'm a newbie, but I really need Octave3.0.3
Its available on some other repositories, but I just cannot figure out how to install it. Can someone please help me??

I downloaded
octave3.0_3.0.3-1_i386.deb
and went through downloading and installing all the dependancies one by one. Then it said that it needs
libpcre3
but I already had the latest version of installed! so I am now stuck!

I also tried pointing the adept installer to one of the repositories that had octave3.0_3.0.3-1_i386.deb, but for some reason, it wouldn't recognize it.

So now I am completely stuck.

Please help!!

Revision history for this message
dino (adinov) wrote :

Daer thisismalhotra,

We need your expertise to fix this little bug in octave for Ubuntu. Please help!

Alex D.

Changed in octave3.0:
assignee: nobody → thisismalhotra
Revision history for this message
mahfiaz (mahfiaz) wrote :

My vote to upgrading this at least in backports or somewhere.

Revision history for this message
phil (fongpwf) wrote :

Looks like even Jaunty is 3.0.1

Changed in octave3.0:
status: New → Confirmed
Revision history for this message
Bhavani Shankar (bhavi) wrote :

hello

@ dino

From where did you download the deb?

Revision history for this message
Joseph Smidt (jsmidt) wrote :

Here is the debdiff needed to close this bug.

*Note, this package depends on suitesparse being updated as it is a build depends.*
I have made the appropriate debdiff for suitesparse here: (Please update this package first.)
https://bugs.launchpad.net/ubuntu/+source/suitesparse/+bug/319054

Revision history for this message
rmcd (rmcd1024) wrote :

In Intrepid, open Octave in a shell, type "clear all", and Octave 3.0.1 will segfault every time.

So I'm adding my vote to upgrade Octave to 3.0.3. Thanks.

Revision history for this message
Iain Lane (laney) wrote :

This debdiff doesn't actually change anything in the Debian package, and therefore is not required. Please follow the sync request process from [0] to get this package into Ubuntu instead. Thanks.

[0] https://wiki.ubuntu.com/SyncRequestProcess

Changed in octave3.0:
importance: Undecided → Wishlist
status: Confirmed → Incomplete
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

I'm unsubscribing u-u-s because you are requesting an update to a stable release, which should be judged my motu-sru or ubuntu-backporters teams. Please have a look at https://wiki.ubuntu.com/StableReleaseUpdates or https://help.ubuntu.com/community/UbuntuBackports and subscribe correspondant team accordingly.

Revision history for this message
phil (fongpwf) wrote :

The backports guidelines indicate the package must already be in Ubuntu's repositories. As far as I can tell 3.0.3 is not in any repository (Jaunty is still 3.0.1). Does this mean it is not eligible for backports?

Revision history for this message
mcnicholls (nicholls-mc) wrote :

I have just been trying to rebuild octave3.0 for Jaunty in light of libsuitesparse-3.1.0 -> libsuitesparse-3.2.0 and it FTBFS due to changes in libsuitesparse.

Seen as libsuitesparse-3.1.0 is NBS something has to be done to octave3.0 to get it to compile.

It looks like this issue has been addressed in the debian package, the latest of which is 1:3.0.4~rc7-1, which has made it into unstable in debian as it has been judged to be of release quality. Seen as it is a RC and it has been a while since it was last synced i am unsure if a sync is the correct move at this point in the cycle?

It looks like this was fixed in debian some point in the 1:3.0.3 release and was fixed upstream in 1:3.0.4~rc3-1 (deb patch was dropped).

Any thoughts?

Revision history for this message
Christian Neumair (chris-gnome-de) wrote :

Ping.

https://launchpad.net/~bhavi/+archive/ppa/+index?start=75&batch=75

offers version 3.03, but the official version seems to be 3.0.5.

Revision history for this message
Christian Neumair (chris-gnome-de) wrote :

I'd like to point out that one can download Debian's 3.0.5 source code from

http://packages.debian.org/de/source/sid/octave3.0

and build it manually after changing

GCCCURVER := $(shell gcc --version | perl -ne '/Debian (.*)-/; print "$$1"; last')

to

GCCCURVER := $(shell gcc --version | perl -ne '/Ubuntu (.*)-/; print "$$1"; last')

in debian/rules. You will also have to build & upgrade octave-communications and a myriade of octave packages, though.

Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

Karmic now has 3.0.5, the current upstream version. (Ubuntu bugs are officially "fix released" when fixed in the development version: https://wiki.ubuntu.com/Bugs/Status)

This 3.0.5 package depends on upgrades to several libraries including libstdc++6, so one can't simply install it in Intrepid as is; I do not know whether it would be possible to compile 3.0.5 against the Intrepid versions of these libraries.

Changed in octave3.0 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.