Differences between revisions 258 and 259
Revision 258 as of 2015-07-28 11:08:57
Size: 8082
Editor: ?RafaelLaboissiereAlt
Comment: Add link to liboctave 2→3 transition
Revision 259 as of 2015-07-30 18:49:59
Size: 7949
Editor: ?RafaelLaboissiereAlt
Comment: The liboctave2 → liboctave3 transition is completed
Deletions are marked like this. Additions are marked like this.
Line 156: Line 156:
The liboctave2 → liboctave3 transition is currently [[https://release.debian.org/transitions/html/auto-octave.html|under way]].

Introduction

The Debian Octave Group (DOG) is a collaborative effort for maintaining the Octave-related Debian packages. Coordination is done through the pkg-octave project at Alioth.

Any developer, either a member of Debian or not, is invited to participate. If you are interested, send an email to the development list or drop a note to the project administrators at Alioth.

Maintained packages

Development is coordinated through Git repositories, using the git-buildpackage tool (with the associated git-dch tool for generating debian/changelog entries).

Mailing lists

There are two mailing lists related to the project:

Check list for the Octave-Forge packages

  1. Bump the build-dependency on octave-pkg-dev to >= 1.0.1.

  2. Bump the Standards-Version to 3.9.6.
  3. Set the Uploaders field as described below.
  4. The recommended debhelper compat level is 9.
  5. We use a machine-readable debian/copyright with the 1.0 specification. Generating this file can be simplified by the following command:

    licensecheck -r --copyright -c  '\.m|\.cc|\.hh|\.c|\.h|\.f' . | /usr/lib/cdbs/licensecheck2dep5

    Note that you will have to update the Format line using the finalized URL for version 1.0. If you are using CDBS version 0.4.103 or later, the URL will be that for version 1.0.

    You can also automatically fix some errors in your file using the following command (from package libconfig-model-perl):

    cme fix dpkg-copyright
  6. Use the SourceForge redirector in the debian/watch file:

    version=3
    http://sf.net/octave/<package>-(.+)\.tar\.gz

Octave Forge packages not in Debian

Candidates for packaging

Packages that will never enter Debian

  • actuarial (unmaintained)
  • civil-engineering (unmaintained)
  • engine (unmaintained)
  • fenv (unmaintained)
  • generate_html (will not be packaged; only of interest for Octave-Forge developers)

  • gnuplot (unmaintained)
  • oct2mat (unmaintained)
  • octclip (will not be packaged; it is now part of the geometry package)

  • odebvp (unmaintained)
  • special-matrix (unmaintained)
  • tcl-octave (unmaintained; RFP: 482615)

  • video (unmaintained)
  • xraylib (unmaintained)
  • windows (tweber: I don't think - we would have to create Debian GNU/kwin32 first)

Packages that have been in Debian at some point but were removed

  • octave-ad
  • octave-ann
  • octave-benchmark
  • octave-bioinfo
  • octave-combinatorics
  • octave-ftp
  • octave-ident
  • octave-informationtheory
  • octave-integration
  • octave-irsa
  • octave-mapping
  • octave-multicore
  • octave-nlwing2
  • octave-nnet
  • octave-octgpr
  • octave-outliers
  • octave-pdb
  • octave-physicalconstants
  • octave-plot
  • octave-simp
  • octave-symband
  • octave-time (RM: 671089)

  • octave-xraylib
  • semidef-oct (RM: 669226)

Uploaders Field

The Uploaders field should normally list the team member(s) that are personally interested in the package and take the primary responsibility for maintaining it. Maintaining this field up-to-date gives a better overview of responsibilities within the team (in particular, it will make individual QA pages more relevant). Also note that team members not in the Uploaders field of a given package can still do Team Uploads, for example for fixing RC bugs or handling transitions.

There are however some packages that nobody is personally interested in for the time being, but which are nevertheless maintained by the team in the interest of our users. The Uploaders field of those packages should list all the team members willing to do this collective maintenance work, which are:

  • Thomas Weber
  • Sébastien Villemot
  • Rafael Laboissiere
  • Mike Miller

The packages in this situation are:

  • octave-bim
  • octave-data-smoothing
  • octave-epstk
  • octave-financial
  • octave-fpl
  • octave-missing-functions
  • octave-msh
  • octave-nan
  • octave-nurbs
  • octave-ocs
  • octave-octcdf
  • octave-parallel
  • octave-secs1d
  • octave-secs2d
  • octave-sockets
  • octave-specfun
  • octave-strings
  • octave-vrml
  • qtoctave

Work in progress

ToDo Items

The following list contains things that should be done at some point in the future.

  • Check that Octave compiles with clang and inform shogun maintainers about it, if yes (shogun-octave was dropped, as shogun uses clang now and some of the Octave code failed to compile)
  • We might want to add a reportbug script (/usr/share/doc/reportbug/README.developers.gz) that reports the BLAS library in use via the alternatives system and all octave-* packages installed. This should help with bug reports.

Obsolete material