[SCM] Debian packaging for jack-audio-connection-kit branch, master, updated. debian/0.116.1-4-92-g8b13fcc

[Felipe Sateler]

Eric Dantan Rzewnicki wrote:
> On Wed, Nov 18, 2009 at 01:26:12PM -0300, Felipe Sateler wrote:
>> Eric Dantan Rzewnicki wrote:
>>> On Wed, Nov 18, 2009 at 12:30:09PM +0000, 
>>> adiknoth-guest at users.alioth.debian.org wrote:
>>>> diff --git a/debian/NEWS b/debian/NEWS
>>>> index 5368ea5..1256015 100644
>>>> --- a/debian/NEWS
>>>> +++ b/debian/NEWS
>>>> @@ -1,3 +1,12 @@
>>>> +jack-audio-connection-kit (0.118+svn3796-1) UNRELEASED; urgency=low
>>>> +
>>>> +   Upstream has replaced -L by -r, so in order to disable realtime mode,
>>>> +   specify -r or --no-realtime now. The reason is to have the same
>>>> +   commandline args for jackd1 and jackd2, but -L was already in use
>>>> +   by jackd2. 
>>>> +
>>>> + -- Adrian Knoth <adi at drcomp.erfurt.thur.de>  Wed, 18 Nov 2009 10:16:27 
>>>> +0100
>>>> +
>>>> jack-audio-connection-kit (0.116.2+svn3592-3) unstable; urgency=low
>>> I'm curious to know where the version in the Subject: comes from and how
>>> it relates to the packaged version.
>> The version comes from git-describe, which in turn uses the last 
>> available tag (IIRC). The code is in 
>> /git/pkg-multimedia/git-commit-notice in alioth if you want to look at it.
> 
> Thanks. It comes from `git describe $rev`, which outputs the most recent
> tag and apends the number of commits since that tag and an abbreviated
> object name for the most recent commit. Which clears up my confusion
> about why Subject: didn't match the changlog version above.
> 
> So, then, is it the team policy to create a new tag when changing
> UNRELEASED to unstable (or other appropriate distribution name) for the
> next upload?

Not quite. The tag should be created by the DD uploading. That's in case 
the DD uploading makes a last-minute change. Upstream tags, on the other 
hand, should be created by the person importing the upstream tarballs. 
I'll update the wiki to clear this up.

-- 
Saludos,
Felipe Sateler