- Maintained packages
- Mailing list
- Git repositories
- Check list for the Octave-Forge packages
- Octave Forge packages not in Debian
- Uploaders Field
- Work in progress
- ToDo Items
- Obsolete material
Anyone is invited to participate. There is no need to be a Debian Developer. If you are interested, send an email to the development list (see below).
Team homepage at tracker.debian.org (for subscribing to notifications)
Development is coordinated through the debian-octave list on Debian list server. Subscription and posting are open to anyone.
Development is coordinated through Git repositories, grouped under the Debian Octave Group homepage at Salsa.
Our git workflow is the following:
Branches: We follow the DEP-14 specification for the reposiotry layout: debian/latest for Debian packaging, upstream/latest for upstream source, and pristine-tar for tarball deltas. Additional branches named according to Debian releases (e.g. debian/stretch, debian/stretch-backports) may be used as need arises for (old)stable uploads and backports.
Tags: debian/$DEB_VERSION for Debian releases and upstream/$VERSION for upstream releases
The upstream branch contains only diffs from tarballs, not the full upstream git history.
We use git-buildpackage tool for managing the repositories and building packages.
Changelog entries are generated using the associated gbp dch command.
In the past, we used to have a top-dir .gitignore file in our Git repositories. This was useful for ignoring the files left over by the package building process. This technique has some drawback, though, since this may interfere with the eventual .gitignore file shipped by the upstream authors and the setting merge-mode = merge in gbp.conf is needed. We then decided to have .gitignore files only in the 'debian/ directories. This means that, after the package is built, some Git commands (e.g. git status and git diff`) non-Debian-related changes in the repository will be indicated. It is then recommended running the following commands:
./debian/rules clean quilt pop -af rm -rf .pc
If there are any files left in the top-dir after running the commands above, then their names should be included in the debian/clean file. This would probably be an issue with the upstream package and should be reported to the upstream authors.
You may want to create an alias for the URL of our Salsa homepage, as follows:
git config --global url."firstname.lastname@example.org:pkg-octave-team/".insteadOf pkg-octave-team:
(this assumes that you are accessing Salsa with SSH; replace the corresponding URL if you use another mean)
Then you can clone repositories as follows:
gbp clone --git-pristine-tar pkg-octave-team:$pkg
(replace $pkg by package name, e.g. octave)
Pristine-tar default option
If you’re tired of always giving the --git-pristine-tar option to gbp (or if you fear forgetting it), you can set the following in ~/.gbp.conf:
[DEFAULT] pristine-tar = True
Note that all packages of the DOG have now the following file debian/gbp.conf, so that the pristine-tar is always True :
[DEFAULT] debian-branch = debian/latest upstream-branch = upstream/latest pristine-tar = True
Subscribing to git commit notifications
Git commit notifications are delivered through https://tracker.debian.org.
You can individually subscribe to commit notifications:
either through the web interface, making sure that you have enabled the vcs keyword
- or through the mail interface, with something like:
( echo "subscribe $pkg"; echo "keyword $pkg + vcs" ) | mail email@example.com
It is also possible to subscribe to all git commit notifications by subscribing to the Debian Octave Group at tracker.debian.org (making sure you have enabled the vcs keyword).
Check list for the Octave-Forge packages
- Bump the Standards-Version to the latest release.
- Set the Uploaders field as described below.
- The recommended debhelper compat level is 11.
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):
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-missing-functions (RM: 1038007)
octave-simp (use octave-interval instead)
octave-specfun (RM: 1038008)
octave-zenity (RM: 1038010)
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, who 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.