git-dch version formatting
 

I'm attempting to take a git repo (private, unfortunately) and turn it into a package. As I go, I'm borrowing liberally from a pre-existing package here.

The command that I'd dearly love to get working is:
git-dch --verbose --auto --ignore-branch --debian-branch=master --snapshot --id-length=8 --snapshot-number=${BUILD_NUMBER}

However, almost any invocation of git-dch throws: Version 1.0 not found

My change log entry reads:
packagename (1.0) lucid; urgency=low

* Initial release. I suspect there will be many more.

-- Corey Quinn <corey@sequestered.net> Sun, 22 Apr 2012 20:14:38 +0000

What magic am I missing here?

-- Corey


--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

git-dch version formatting
 

On 04/25/2012 07:34 AM, Corey Quinn wrote:
> I'm attempting to take a git repo (private, unfortunately) and turn it into a package. As I go, I'm borrowing liberally from a pre-existing package here.
>
> The command that I'd dearly love to get working is:
> git-dch --verbose --auto --ignore-branch --debian-branch=master --snapshot --id-length=8 --snapshot-number=${BUILD_NUMBER}
>
> However, almost any invocation of git-dch throws: Version 1.0 not found
>
> My change log entry reads:
> packagename (1.0) lucid; urgency=low
>
> * Initial release. I suspect there will be many more.
>
> -- Corey Quinn <corey@sequestered.net> Sun, 22 Apr 2012 20:14:38 +0000
>
> What magic am I missing here?
>
> -- Corey
>

git-dch uses tags and the current debian/changelog to determine what
range of commits should go in the changelog.
You probably have to use --since to specify which commits should go in
and/or --debian-tag to specify your tag format (debian/<version> is default)

--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu