On Friday, December 5, 2025 12:16:54 PM Mountain Standard Time jvk wrote:
> First of all thank you for addressing my confusions and helping me.
> There is this last thing which i didnt understand
>
> So i deleted the repo again and made a new one to redo and understand
> the work flow better .
> https://salsa.debian.org/jvk_here/python-playwright/
>
> I executed the following commands
>
> history :-
> mkdir maintain_playwright
> 847 cd maintain_playwright/
> 848 gbp clone
> https://salsa.debian.org/jvk_here/python-playwright.git --pristine-tar
> 849 cd python-playwright/
> 850 gbp import-orig --uscan --pristine-tar
>
> 852 gbp import-orig --uscan --pristine-tar
>
>
>
>
> 857 dch
> 858 gbp buildpackage --git-pristine-tar --git-color=on --git-verbose
> --git-notify=on --git-pbuilder
> 859 gbp buildpackage --git-pristine-tar --git-color=on --git-verbose
> --git-notify=on --git-pbuilder --git-ignore-new
>
>
>
> 863 cd python-playwright/
> 864 gbp push
> 865 git push
> (removed useless cmds such as ls,cd)
>
> i explecitly mentioned in import-orig and in build to handel the
> pristine-tar branch but if you check the repo there is no pristine tar,
> why?
I think the problem is that you haven’t included “--pristine-tar” in “gbp
push”.
However, if you want to use pristine-tar (which I highly recommend
because it makes sure that everyone working on a package has the same version
of the .orig.tar.gz, so that when different people upload -X revisions they
don’t fails because the .orig.tar.gz is subtly different), I would recommend
it add it to debian/gbp.conf. When you do this, you don’t need to add "--
pristine-tar" to any of the commands because it is added automatically. For
example, see:
https://salsa.debian.org/python-team/packages/python-electrum-ecc/-/blob/
debian/master/debian/gbp.conf?ref_type=head
Okay noted ✅️
--
Soren Stoutner
soren@debian.org