[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#667863: marked as done (transition: octave 3.2 -> 3.6)

Your message dated Mon, 18 Jun 2012 20:34:21 +0200
with message-id <20120618183421.GD7780@radis.cristau.org>
and subject line Re: Bug#667863: transition: octave 3.2 -> 3.6
has caused the Debian Bug report #667863,
regarding transition: octave 3.2 -> 3.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

667863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667863
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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.


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

--- End Message ---
--- Begin Message ---
On Mon, Jun 18, 2012 at 20:27:42 +0200, Cyril Brulebois wrote:

> kibi@franck:~$ dak ls octave3.2 -S -s testing
> kibi@franck:~$ 
> All done I think?
Indeed.  Closing.


--- End Message ---

Reply to: