Hi,
I am new to Debian packaging and am trying to use `git-buildpackage` to
create packages for a relatively simple piece of code. My structure
looks like this:
- my code resides in a git repository
- the (only) branch is 'main'
- the repository includes a `debian/`-dir which contains the meta
information for packaging
- my versions are tagged `vX.Y.Z`.
From what I understand, this represents a "native" package. I have
tried creating the relevant files, but have trouble piecing the workflow
for my use-case together. From what I assume it should look something
like this:
```
# Finish work
git tag vX.Y.Z
gbp dch --commit --release
gbp buildpackage # --git-tag?
# Push to origin
# Publish package
```
Is this workflow roughly correct? I have struggled to get it to work, in
particular I have a few specific questions:
- Can I configure 'debian-branch' in 'debian/gbp.conf'? It doesn't seem
to be picked up from the '[DEFAULT]' section and I have to pass it to
both `gbp dch` and `gbp buildpackage`.
- How can I convince `gbp dch` to pick up the version? I have tried
passing `--git-upstream-tag=v%(version)s` as documented in the man-page,
but the option is not known to the tool. Likewise, configuring it in
'debian/gbp.conf' changes nothing.
- Does the changelog have to be tracked in the repository or is it
possible to regenerate it from scratch on every release?
Thanks for the help!
Best regards
Max Schettler
_______________________________________________
git-buildpackage mailing list
[email protected]
http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
