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

[Daigo Moriwaki]

Hi Paul,

Paul van Tilburg wrote:
>> 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.

$ 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.

My version is
westwood{daigo}% dpkg -l G svn-buildpackage
ii  svn-buildpackage                            
0.6.14                                      


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.


Thanks,
Daigo

-- 
Daigo Moriwaki
beatles at sgtpepper dot net