Rafael Laboissiere <rafael@laboissiere.net> writes: > This is the first time I use git-buildpackage. I think that other > newbies should also be clearly informed about the packaging practices. > At the time I participate to the DOG, there was a (quite complete) > document with the packaging guidelines. I think that we can survive now > with the wiki page, provided that the crucial information is present. > > BTW, I will also add a note on the about the use of git-dch for handling > debian/changelog, as soon as I get used to it. > > Another issue, should we require that the transitioned Octave-Forge > packages respect the following? > > * Bump Standards-Version to 3.9.3 > * Bump debhelper compat level to 9 > * Bump Build-Depends on octave-pkg-dev to >= 1.0.0 > (or whichever number the next release has) I think it would be good. Also, I would recommend that all the packages that have already a machine-readable debian/copyright upgrade to the finalized specification (see [1]). It can be helpful to run "cme fix dpkg-copyright" from package libconfig-model-perl. [1] http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
Attachment:
pgphANpHblEbM.pgp
Description: PGP signature