[Pkg-ruby-extras-maintainers] r828 - packages/libgems-ruby/tags

Paul van Tilburg paulvt at debian.org
Tue Sep 12 19:56:48 UTC 2006

Hello Daigo,

On Mon, Sep 11, 2006 at 02:04:03PM +0000, Daigo Moriwaki wrote:
> Author: daigo-guest
> Date: 2006-09-11 14:04:03 +0000 (Mon, 11 Sep 2006)
> New Revision: 828
> Added:
>    packages/libgems-ruby/tags/0.9.0-3/
> Log:
> [svn-buildpackage] Tagging libgems-ruby (0.9.0-3)
> Copied: packages/libgems-ruby/tags/0.9.0-3 (from rev 827, packages/libgems-ruby/trunk)

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.

I'm not accusing you of anything, but when adding changelog entries I
find myself editing a changelog entry of a version that has already been

Kind regards,


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/20060912/aafdbcb4/attachment.pgp

More information about the pkg-ruby-extras-maintainers mailing list