[Pkg-octave-devel] octave2.1-2.1.64-2 uploaded

[Rafael Laboissiere]

* Dirk Eddelbuettel <edd@debian.org> [2005-01-25 05:24]:

> 
> In response to the mail by Rafael Laboissiere dated 25 January 2005 at 08:37:
> |   * debian/rules:
> |     - (clean) Inverse the order of the calls to rm libcruft/*/Makefile and
> |       make distclean.  This was causing several *.o in libcruft to be left
> |       after debian/rules clean, which resulted in dpkg-source breakage when
> |       building the diff.gz package file.
> |     - (configure) Save the original octave-bug.in file as octave-bug.in.orig
> |       prior to the tempfile substitution
> |     - (clean) Restore octave-bug.in.orig as octave-bug.in, such that the
> |       patch does not end up in the diff.gz file
> |
> |  -- Rafael Laboissiere <rafael@debian.org>  Mon, 24 Jan 2005 16:39:08 +0100
> | ===========================================================================
> 
> Cool. Never noticed the other issues.

The second and the third changes above only makes the diff.gz a bit smaller
and avoid having Debian-specific patches distributed in a hidden way.

The first change addresses a more critical issue, because it was impossible
to built the package in a non-fresh source tree.

> | ===========================================================================
> | W: octave2.1 source: changelog-should-mention-nmu
> | W: octave2.1 source: source-nmu-has-incorrect-version-number 2.1.64-2
> 
> I think this may go away if you add yourself as Uploaders: in debian/control.

I think we will follow Isaac's suggestion and change the signature entries
in debian/changelog to something like:

 -- Debian Octave Group <pkg-octave-devel@lists.alioth.debian.org>  [[date]]

which matches the Maintainer field in debian/control.

I already added:

Local Variables:
debian-changelog-full-name: "Debian Octave Group"
debian-changelog-mailing-address: "pkg-octave-devel@lists.alioth.debian.org"
End:

to the end of debian/changelog and it works with (X)Emacs.
 
-- 
Rafael