Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #17245 > unrolled thread

Unexpected workflow

Back to article view | Back to linux.debian.maint.python

Contents

  Unexpected workflow jvk <jaivkadam@gmail.com> - 2025-12-05 20:20 +0100
    Re: Unexpected workflow Soren Stoutner <soren@debian.org> - 2025-12-05 20:30 +0100
      Re: Unexpected workflow Jai kadam <jaivkadam@gmail.com> - 2025-12-05 20:40 +0100
    Re: Unexpected workflow Andrey Rakhmatullin <wrar@debian.org> - 2025-12-05 20:30 +0100

#17245 — Unexpected workflow

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? 


-- 
jvk <jaivkadam@gmail.com>

[toc] | [next] | [standalone]

#17246

[Multipart message — attachments visible in raw view] — view raw

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=heads

-- 
Soren Stoutner
soren@debian.org

[toc] | [prev] | [next] | [standalone]

#17248

[Multipart message — attachments visible in raw view] — view raw

On Sat, 6 Dec, 2025, 12:57 am Soren Stoutner, <soren@debian.org> wrote:

> 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”.

Ahh i thought if i have mentioned it in import and build i dont need to
mention in 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
> <https://salsa.debian.org/python-team/packages/python-electrum-ecc/-/blob/debian/master/debian/gbp.conf?ref_type=heads>
>

Okay noted ✅️
> --
> Soren Stoutner
> soren@debian.org

[toc] | [prev] | [next] | [standalone]

#17247

[Multipart message — attachments visible in raw view] — view raw

On Sat, Dec 06, 2025 at 12:46:54AM +0530, jvk wrote:
>  864  gbp push
>  865  git push
>
>i explecitly mentioned in import-orig and in build to handel the
>pristine-tar branch 

And so locally you likely have it updated.

>but if you check the repo there is no pristine tar,
>why?

You didn't push it.

(note that normally explicit --git-pristine-tar aren't needed, because 
normally debian/gbp.conf explicitly enables it in repos that use it, but 
unfortunately not all maintainers do this in their repos)

-- 
WBR, wRAR

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web