[Pkg-octave-devel] All packages are in SVN now

Rafael Laboissiere Rafael Laboissiere <laboissiere@cbs.mpg.de>
Sat, 19 Feb 2005 18:52:27 +0100


* Rafa Rodriguez Galvan <rafael.rodriguez@uca.es> [2005-02-19 14:10]:

> OK, I have actualised the debian/changelog, introducing the upstream
> release 2.1.65. 
> 
> I have tested locally and it compiles correctly, building the debs:
> 
> octave2.1_2.1.65-1_i386.deb         .
> octave2.1-headers_2.1.65-1_i386.deb
> octave_2.1.65-1_i386.deb            
> octave2.1-htmldoc_2.1.65-1_all.deb
> octave2.1-doc_2.1.65-1_all.deb 
> octave2.1-info_2.1.65-1_all.deb
> octave2.1-emacsen_2.1.65-1_all.deb
> 
> Following the Guidelines, I made a new tag for it. Then,
> I run "cvs commit" and it worked fine!

Thanks for that.  I really appreciate your efforts in building the package
and using the svn repository.

> But I made a mistake: the program dhc complains with
> the current debian/changelog, so I had to edit it manually.
> I copied and pasted the line
> 
> " -- Debian Octave Group <pkg-octave-devel@lists.alioth.debian.org> 
> Thu, 27 Jan 2005 10:11:21 +0100 "

If you are using (X)Emacs to edit debian/changelog and have the
devscripts-el package installed, then you have just to type C-c C-c and the
line above with the current date/time is automagically inserted.

> but forgot to actualise the date. I suppose I may change it
> (both in trunk and in tags) and do a "svn commit" again. May I?

There was also another mistake: The entry for version 2.1.64-4 should be
merged with that for 2.1.65-1, since 2.1.64-4 has not been released.  This
is why the Guidelines insist in keeping the warning "NOT YET RELEASED!" and
the signature line empty when committing non-released debian/changelog to
the svn repository.  I already fixed that in SVN.

Finally, I think that the tag in tags/packages should be created only after
the version is actually uploaded to unstable.  The tag that you created is
okay but now it may become painful if it is created to early, because then
we have to do many svn copy commands to keep the tag in sync with trunk.  I
just added a note in the Guidelines about this.

Please, notice that these are contructive criticisms.  As I said before, I
am really pleased that somebody other than me is using the repository now.
 
-- 
Rafael