Your repository contains master and upstream branches, but not pristine-tar. pristine-tar makes it a lot easier to use gbp, especially when processing new upstream releases, because it can regenerate the upstream tarball automatically, so that those building the package don’t need run `uscan -- download-current-version` and the can just use `gbp buildpackage`. You can enable --pristine-tar for future `gbp import-orig --uscan` by adding a debian/gbp.conf with contents similar to the following: https://salsa.debian.org/soren/privacybrowser/-/blob/master/debian/gbp.conf? ref_type=heads You can also import a pristine-tar for the current version if desired. Your source package currently ships a binary in /usr/bin/ and Python modules in /usr/lib/python3/dist-packages/. These should be split out into two different binary packages, one probably named vkbasalt-cli and the other probably named python3-vkbasalt. You can see an example of how this is done for the electrum package: https://salsa.debian.org/cryptocoin-team/electrum/-/tree/master/debian? ref_type=heads As this package relates to the vkbasalt source package already in Debian, have you reached out to Stephan to coordinate your efforts? https://tracker.debian.org/pkg/vkbasalt -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.