[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

debchange / git-buildpackage: custom version naming



Probably a noob question, but I didn't manage to find this information anywhere. We work on Ubuntu 14.10 and use debchange and git-buildpackage (thanks to  Neil Williams https://lists.debian.org/debian-devel/2015/05/msg00375.html) as a part of packaging process.

1.
For a certain reasons we need to give up default behaviour of debchange.

Here's what our changelogs look like (printed with cuts):
project-name (0.1.1ubuntu8) utopic; urgency=medium
project-name (0.1.1ubuntu7) utopic; urgency=medium
project-name (0.1.1ubuntu6) utopic; urgency=medium
project-name (0.1.1ubuntu5) utopic; urgency=medium
project-name (0.1.1ubuntu4) utopic; urgency=medium
project-name (0.1.1ubuntu3) utopic; urgency=medium
project-name (0.1.1ubuntu2) utopic; urgency=medium
project-name (0.1.1ubuntu1) utopic; urgency=medium
project-name (0.1.1) unstable; urgency=low
Every record (excepting the earliest one) were made with an `dch -i` command. The problem is in "ubuntu" keyword which is appended to the every new version. We would like to have a simple build number there instead of "ubuntu" + build number. `dch -i --vendor=" "` doesn't help here.

2.
If behaviour of debchange cannot be changed, it would be suitable at least to use custom tag format (without "ubuntu") when tagging the repo with the following command:
gbp buildpackage --git-builder="debuild -uc -us -j4"
    --git-debian-tag="%(version)s" --git-ignore-new --git-tag --git-posttag="git push && git push --tags"
I didn't find any information about the metavariables that --git-debian-tag can take. This fills our repo with a tonns of long tags (like "0.1.1ubuntu1"), but "ubuntu" makes no sense, because we're packaging only for this distro.

Any help will be appreciated.

Sincerely,
Vitaly Isaev

Reply to: