Recommend more exhaustive form of cme check.
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.html|divand]]||* [[http://octave.sourceforge.net/divand/index.html|divand]] (uploaded, ITP: DebianBug:865794)|
|Line 84:||Line 84:|
|* [[http://octave.sourceforge.net/octproj/index.html|octproj]]||* [[http://octave.sourceforge.net/octproj/index.html|octproj]] (uploaded, ITP: DebianBug:871926)|
|Line 88:||Line 88:|
|Line 92:||Line 91:|
|* [[http://octave.sourceforge.net/zeromq/index.html|zeromq]] (uploaded, ITP: DebianBug:865865)|
- Maintained packages
- Mailing lists
- Check list for the Octave-Forge packages
- Packages currently in Debian but not maintained upstream
- Octave Forge packages not in Debian
- Uploaders Field
- Work in progress
- ToDo Items
- Obsolete material
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.
Development is coordinated through Git repositories, using the git-buildpackage tool (with the associated git-dch tool for generating debian/changelog entries).
There are two mailing lists related to the project:
pkg-octave-devel: Development discussion for Octave and Octave-related packages in Debian
pkg-octave-commit: Automatic Git activity notifications
Check list for the Octave-Forge packages
Bump the build-dependency on octave-pkg-dev to >= 1.4.2.
- Bump the Standards-Version to 4.0.0.
- Set the Uploaders field as described below.
- The recommended debhelper compat level is 10.
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
Use the SourceForge redirector in the debian/watch file (bump format version to 4 if needed):
Packages currently in Debian but not maintained upstream
- octave-audio (already removed from testing and unstable)
- 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)
- civil-engineering (unmaintained)
- engine (unmaintained)
fenv (unmaintained; find function __setround__ in the interval package)
generate_html (will not be packaged; only of interest for Octave-Forge developers)
- gnuplot (unmaintained)
- mechanics (unmaintained)
- oct2mat (unmaintained)
- odebvp (unmaintained)
- special-matrix (unmaintained)
tcl-octave (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
octave-epstk (RM: 850030])
- octave-simp (use octave-interval instead)
octave-time (RM: 671089])
semidef-oct (RM: 669226])
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:
Work in progress
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.