Re: Guidence over testing

On Fri, 2025-12-05 at 15:37 +0500, Andrey Rakhmatullin wrote:
> On Fri, Dec 05, 2025 at 03:57:39PM +0530, jvk wrote:
> > okay so i deleted the old repo and made a new one
> > https://salsa.debian.org/jvk_here/python-playwright/
> 
> This looks good, except that it doesn't have the new upstream tag, 
> the upstream branch commit and he pristine-tar branch commit pushed.
well in the previous attempt i used gbp and the upstream got pushed
automatically, you told not to use gbp now so how do i push upstream
and pristine-tar now?
> 
> > what i think is the next steps->
> > gbp-source (will make .dsc .changes and .tar.gz file)
> 
> There is no gbp-source (and you don't need to build a source package 
> separately when using gbp).
sorry i was talking about dpkg-source
> 
> > then sbuild -d unreleased <whatever name>.dsc will test it?
> 
> You should use gbp buildpackage, if you want to use sbuild with it
> you can 
> pass --git-builder=sbuild etc. to it.
okay noted so use gbp buildpackage --git-builder=sbuild instead of
dpkg-source -d . 
> 
> > if error emerges gbs pq import
> > git checkout patch-queue/debian (changes wd)
> > fix code
> > git commit
> > gbp pq export (will this push the commits?)
> 
> gbp pq export only (re-)generates debian/patches, nothing else. And
> the 
> patch-queue/debian commits themselves are never pushed anywhere.
>