Bug#667863: transition: octave 3.2 -> 3.6
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
The Debian Octave Group (DOG) is preparing the transition from Octave 3.2
to 3.6. There will be an important impact on the Debian ecosystem
because we abandoned the versioned naming scheme. Indeed, the Octave
package currently in stable/testing is called octave3.2. From now on, it
will be called simply octave (which will conflict/replace octave3.2).
After the transition is completed, we will ask for the removal of the
octave3.2* packages. This will affect a large number of packages in
testing. We are coordinating this transition through our wiki page [1].
There are two types of packages involved. First, the Octave-Forge [2]
packages that are maintained by the DOG itself. We have already ported
all of them and requested removal of the obsolete ones.
Second, packages not maintained by the DOG that have reverse dependencies
on the octave3.2* packages. The situation of each one of these packages
have been analyzed and appropriate bug reports with patches have been
filed [3].
We have also filed a RC bug report (Bug#661521) against the octave
package currently in unstable (version 3.6.1-4). We will wait until all
Octave-Forge packages, at least, are ready for migration into testing
before we close that bug report. The expected date when this will happen
is April 15, 2012.
Best,
Rafael Laboissière
[1] http://wiki.debian.org/Teams/DebianOctaveGroup#Migration_to_git-buildpackage_and_Octave_3.6
[2] http://octave.sf.net
[3] http://wiki.debian.org/Teams/DebianOctaveGroup#Reverse_dependencies_on_octave3.2.2A_packages
Reply to: