[Pkg-privacy-maintainers] Packaging workflow onioncircuits

[Sascha Steinbiss]

Hi intrigeri,

[...]
>> I guess when using an upstream branch tracking the upstream repo, I
>> would have to manually pull changes into the upstream branch from the
>> upstream repo and tag the relevant signed release commit with
>> "upstream/<upstream_version>" for git-buildpackage to pick it up. Then
>> merge this tag into master and continue from step four above. Correct?
>> Do you know of any automation that might help? Of course, I would be
>> happy to learn something new and do things in a way that fits with the
>> rest of the team.
> 
> I suspect gbp import-orig's --upstream-vcs-tag option is what you want :)

So I would do both -- pull into the upstream branch _and_ link its tag
then to the tarball using above parameter when importing a tarball?

Cheers
Sascha

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20190711/c40500e7/attachment.sig>