8318
Comment: Recommend more exhaustive form of cme check.

← Revision 276 as of 20170814 06:48:42 ⇥
8414
Update the list of candidates for packaging

Deletions are marked like this.  Additions are marked like this. 
Line 73:  Line 73: 
* [[http://octave.sourceforge.net/divand/index.htmldivand]]  * [[http://octave.sourceforge.net/divand/index.htmldivand]] (uploaded, ITP: DebianBug:865794) 
Line 84:  Line 84: 
* [[http://octave.sourceforge.net/octproj/index.htmloctproj]]  * [[http://octave.sourceforge.net/octproj/index.htmloctproj]] (uploaded, ITP: DebianBug:871926) 
Line 88:  Line 88: 
* [[http://octave.sourceforge.net/sparsersb/index.htmlsparsersb]]  
Line 92:  Line 91: 
* [[http://octave.sourceforge.net/zeromq/index.htmlzeromq]] (uploaded, ITP: DebianBug:865865) 
Contents
Introduction
The Debian Octave Group (DOG) is a collaborative effort for maintaining the Octaverelated Debian packages. Coordination is done through the pkgoctave 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 gitbuildpackage tool (with the associated gitdch tool for generating debian/changelog entries).
Mailing lists
There are two mailing lists related to the project:
pkgoctavedevel: Development discussion for Octave and Octaverelated packages in Debian
pkgoctavecommit: Automatic Git activity notifications
Check list for the OctaveForge packages
Bump the builddependency on octavepkgdev to >= 1.4.2.
 Bump the StandardsVersion to 4.0.0.
 Set the Uploaders field as described below.
 The recommended debhelper compat level is 10.
We use a machinereadable 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 libconfigmodelperl):cme fix dpkg
Use the SourceForge redirector in the debian/watch file (bump format version to 4 if needed):
version=4 http://sf.net/octave/<package>(.+)\.tar\.gz
Packages currently in Debian but not maintained upstream
 octaveaudio (already removed from testing and unstable)
 octavegsl
 octavemissingfunctions
 octavespecfun
 octavezenity
 qtoctave (already removed from testing and unstable)
Octave Forge packages not in Debian
Candidates for packaging
The following packages are listed as maintained by the upstream authors and are not yet in Debian:
Packages that should not enter Debian
 actuarial (unmaintained)
 civilengineering (unmaintained)
 engine (unmaintained)
fenv (unmaintained; find function __setround__ in the interval package)
 flcore
generate_html (will not be packaged; only of interest for OctaveForge developers)
 gnuplot (unmaintained)
 mechanics (unmaintained)
 oct2mat (unmaintained)
 odebvp (unmaintained)
 specialmatrix (unmaintained)
tcloctave (unmaintained; RFP: 482615)
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
 octavead
 octaveann
 octavebenchmark
 octavebioinfo
 octavecombinatorics
octaveepstk (RM: 850030])
 octaveftp
 octaveident
 octaveinformationtheory
 octaveintegration
 octaveirsa
 octavemulticore
 octavenlwing2
 octavennet
 octaveoctgpr
 octaveoctcdf
 octaveoutliers
 octavepdb
 octavephysicalconstants
 octaveplot
 octavesimp (use octaveinterval instead)
 octavesymband
octavetime (RM: 671089])
 octavexraylib
semidefoct (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 uptodate 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:
 octavebim
 octavedatasmoothing
 octavefinancial
 octavefpl
 octavemissingfunctions
 octavemsh
 octavenan
 octavenurbs
 octaveocs
 octaveparallel
 octavesecs1d
 octavesecs2d
 octavesockets
 octavespecfun
 octavestrings
 octavevrml
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 (shogunoctave 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.