On Wed, Sep 13, 2006 at 10:03:23AM +0900, Daigo Moriwaki wrote:
> Paul van Tilburg wrote:
> > I was wondering... if you do the tagging with svn-buildpackage (as the
> > log indicates), how do you prevent it doing the dch -i. It's a bit
> > confusing because after upload & tagging all our packages, we
> > automatically have a new changelog entry for suite UNRELEASED so that we
> > know this is an unreleased package, whereas yours somehow do not.
>> $ svn-buildpackage --svn-only-tag
>> My process is
> - commit the working directory by debcommit.
> debcommit is not so popular, but very useful.
> - build a package by svn-buildpackage with pbuilder
> - install and test it
> - upload it to Debian by dput
> - tag by svn-buildpackage --svn-only-tag
>> After --svn-only-tag, a new changelog entry with UNRELEASED is added,
> but remains uncommitted.
Aahh.. that must be it. I always do after the above steps:
$ cd ..
$ svn ci -m "Uploaded libfoo-ruby (<version>), prepare changelog for new version/revision."
> I did not know svn-buildpackage commits a new changelog entry. I was not
> aware about that. I did not select --svn-only-tag in order to avoid
> commit, but it just fit my process. So, I don't know it is the correct way.
No problem! I guess, you know now ;)
Best regards,
Paul
--
Student @ Eindhoven | email: paulvt at debian.org
University of Technology, The Netherlands | JID: paul at luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20060913/fef41892/attachment.pgp