synced
** Changed in: octave3.0 (Ubuntu)
Status: Confirmed = Fix Released
--
[MoM SYNC] octave3.0 3.0.0-1
https://bugs.launchpad.net/bugs/185653
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Please sync octave3.0 from sid
** Changed in: octave3.0 (Ubuntu)
Importance: Undecided = Wishlist
Status: In Progress = Confirmed
--
[MoM SYNC] octave3.0 3.0.0-1
https://bugs.launchpad.net/bugs/185653
You received this bug notification because you are a member of Ubuntu
Bugs, which is
HI,
I just can prepare some quick rebuilds of source packages which are depending
on octave which is provided now from octace2.9 (which is already in the
archive) and octace3.0.
If everything is fine, I'll remove Provides: octave from octave2.9 and go
further with the sync of octave3.0.
The
Yes, my concerns are in the comments of bug #178424.
The problem is not as simple as a new octave package depending on
octave3.0. There are quite a few reverse(-build)-dependencies. We also
should think what to do with octave2.9. Leaving both in an LTS release
doesn't seem wise to me.
I still
Please Do Not Sync Anything Until
https://bugs.edge.launchpad.net/ubuntu//+bug/185959 is finished.
I'll work with Martin Pitt on this.
Thx,
\sh
** Changed in: octave3.0 (Ubuntu)
Assignee: (unassigned) = Stephan Hermann (shermann)
Status: Incomplete = In Progress
--
[MoM SYNC]
Ming Hua has some concerns about upgrade paths and the transition from
Octave 2.9 to 3.0 I believe. Perhaps we should get that worked out
before syncing?
** Changed in: octave3.0 (Ubuntu)
Status: Confirmed = Incomplete
--
[MoM SYNC] octave3.0 3.0.0-1
