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

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

Guidence over testing

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

Contents

  Guidence over testing jvk <jaivkadam@gmail.com> - 2025-12-05 06:40 +0100
    Re: Guidence over testing Andrey Rakhmatullin <wrar@debian.org> - 2025-12-05 08:00 +0100
      Re: Guidence over testing Jai kadam <jaivkadam@gmail.com> - 2025-12-05 09:10 +0100
        Re: Guidence over testing Carsten Schoenert <c.schoenert@t-online.de> - 2025-12-05 14:50 +0100
          Re: Guidence over testing jvk <jaivkadam@gmail.com> - 2025-12-05 16:50 +0100
      Re: Guidence over testing jvk <jaivkadam@gmail.com> - 2025-12-05 10:40 +0100
        Re: Guidence over testing Andrey Rakhmatullin <wrar@debian.org> - 2025-12-05 10:50 +0100
          Re: Guidence over testing jvk <jaivkadam@gmail.com> - 2025-12-05 11:30 +0100
            Re: Guidence over testing Andrey Rakhmatullin <wrar@debian.org> - 2025-12-05 11:40 +0100
              Re: Guidence over testing jvk <jaivkadam@gmail.com> - 2025-12-05 12:10 +0100
                Re: Guidence over testing Andrey Rakhmatullin <wrar@debian.org> - 2025-12-05 12:40 +0100

#17229 — Guidence over testing

Hello,

I was able to make a playwirght project under my name space on salsa
debian and i think have managed to get it in the format the debian
needs with the 1.56.0 version.
https://salsa.debian.org/jvk_here/python-playwright/

How did you test the 1.55.0 version with pytest? I tried many things
then decided to check the publishing pipeline of playwright to just
follow how they test it before publish and try to replicate it locally
but it fails cause no file found playwirght/driver/node, maybe i did
install the package in the correct way.


-- 
jvk <jaivkadam@gmail.com>

[toc] | [next] | [standalone]

#17230

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

On Fri, Dec 05, 2025 at 11:05:03AM +0530, jvk wrote:
>I was able to make a playwirght project under my name space on salsa
>debian and i think have managed to get it in the format the debian
>needs with the 1.56.0 version.

It looks like you've manually made the "New upstream version 1.56.0+ds" 
commit and included generated files in it. This commit should be done by 
gbp import-orig instead.


-- 
WBR, wRAR

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

#17232

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

On Fri, 5 Dec, 2025, 12:27 pm Andrey Rakhmatullin, <wrar@debian.org> wrote:

> On Fri, Dec 05, 2025 at 11:05:03AM +0530, jvk wrote:
> >I was able to make a playwirght project under my name space on salsa
> >debian and i think have managed to get it in the format the debian
> >needs with the 1.56.0 version.
>
> It looks like you've manually made the "New upstream version 1.56.0+ds"
> commit and included generated files in it. This commit should be done by
> gbp import-orig instead.

I should probably read all manuals now :)

>
> --
> WBR, wRAR
>

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

#17239

Hello Jai Kadam,

Am 05.12.25 um 09:59 schrieb Jai kadam:
..
> I should probably read all manuals now :)

yes, that is something we do expect from you.
So did you ever read the manual of git-buildpackage (aka gbp)? gbp is 
the chosen helper tool by the DPT, it's essential you know it!

https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/

You need to to get familiar with that, otherwise it's for you but also 
for others quite cumbersome to help.

You need to understand what steps you need to make and why, also what 
configure options you will need to give the various gbp commands sometimes.

The usual dance you will need to do with every new upstream version is:

1. Import the newer version into the packaging git tree.
2. Look into the changes Upstream has done like increased required
    versions for build depending packages or new added dependencies.
3. Adjust/Add/Remove additional needed patches if needed, the so called
    patch-queue.
4. Look into open bug reports and fix them if possible.
5. Adjust the packaging like updating copyright information, adjust
    sequencer files, fix build and test suite issues, check .
6. Look into merge requests if existing.
7. Adjust/Update the CI/autopkgtest setup if needed.
8. Check if you need to update the debian/ folder in case a bump of the
    Debian Policy was released. The current value for Standards-Version
    is 4.7.2.
9. Run Lintian after your test build and fix Warnings, Errors and if
    possible other flags too.
10. Reach out for help if you feeling lost, don't end in try & error
     in case you do not really understand what's going wrong and why.

And as for you as a newcomer I would suggest to also get familiar with 
(git-)pbuilder first. It's to me easier to learn for starters and for 
building packages it doesn't matter if you use pbuilder or sbuild. Once 
you are more experienced you can dive into sbuild at any time then.

-- 
Regards
Carsten

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

#17240

On Fri, 2025-12-05 at 15:44 +0200, Carsten Schoenert wrote:
> Hello Jai Kadam,
> 
> Am 05.12.25 um 09:59 schrieb Jai kadam:
> ..
> > I should probably read all manuals now :)
> 
> yes, that is something we do expect from you.
> So did you ever read the manual of git-buildpackage (aka gbp)? gbp is
> the chosen helper tool by the DPT, it's essential you know it!
> 
> https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/
yup read the imp parts (imp which i felt, like in which i got confused
in past) now ig i will not
> 
> You need to to get familiar with that, otherwise it's for you but
> also 
> for others quite cumbersome to help.
> 
> You need to understand what steps you need to make and why, also what
> configure options you will need to give the various gbp commands
> sometimes.
> 
> The usual dance you will need to do with every new upstream version
> is:
> 
> 1. Import the newer version into the packaging git tree.
> 2. Look into the changes Upstream has done like increased required
>     versions for build depending packages or new added dependencies.
> 3. Adjust/Add/Remove additional needed patches if needed, the so
> called
>     patch-queue.
> 4. Look into open bug reports and fix them if possible.
> 5. Adjust the packaging like updating copyright information, adjust
>     sequencer files, fix build and test suite issues, check .
> 6. Look into merge requests if existing.
> 7. Adjust/Update the CI/autopkgtest setup if needed.
> 8. Check if you need to update the debian/ folder in case a bump of
> the
>     Debian Policy was released. The current value for Standards-
> Version
>     is 4.7.2.
> 9. Run Lintian after your test build and fix Warnings, Errors and if
>     possible other flags too.
> 10. Reach out for help if you feeling lost, don't end in try & error
>      in case you do not really understand what's going wrong and why.
> 
> And as for you as a newcomer I would suggest to also get familiar
> with 
> (git-)pbuilder first. It's to me easier to learn for starters and for
> building packages it doesn't matter if you use pbuilder or sbuild.
I just setuped pbuilder and yes it was easy than sbuild, thank you for
this suggestion!
The build was successful :)
> Once 
> you are more experienced you can dive into sbuild at any time then.


-- 
jvk <jaivkadam@gmail.com>

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

#17233

On Fri, 2025-12-05 at 11:57 +0500, Andrey Rakhmatullin wrote:
> On Fri, Dec 05, 2025 at 11:05:03AM +0530, jvk wrote:
> > I was able to make a playwirght project under my name space on
> > salsa
> > debian and i think have managed to get it in the format the debian
> > needs with the 1.56.0 version.
> 
> It looks like you've manually made the "New upstream version
> 1.56.0+ds" 
> commit and included generated files in it. This commit should be done
> by 
> gbp import-orig instead.
I seriously cant understand what you mean, this is not helping.
Ig it was you how told me to use git.
And what you are telling is not written in any workflow ,why?

> 

-- 
jvk <jaivkadam@gmail.com>

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

#17234

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

On Fri, Dec 05, 2025 at 03:00:25PM +0530, jvk wrote:
>> > I was able to make a playwirght project under my name space on
>> > salsa
>> > debian and i think have managed to get it in the format the debian
>> > needs with the 1.56.0 version.
>>
>> It looks like you've manually made the "New upstream version
>> 1.56.0+ds"
>> commit and included generated files in it. This commit should be done
>> by
>> gbp import-orig instead.
>I seriously cant understand what you mean, this is not helping.

I mean that simply using gbp import --orig, like you guides tell you, 
wouldn't produce the repo you linked, so you must have done something 
else. If you want help with this you can explain what did you do with 
details.

>Ig it was you how told me to use git.

I told you to use git push instead of gbp push, because gbp push is not 
suitable for your needs. Not sure if you mean that you decided to not use 
any of the gbp tools instead.

>And what you are telling is not written in any workflow ,why?

I don't think this is true but you can elaborate.

-- 
WBR, wRAR

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

#17235

On Fri, 2025-12-05 at 14:46 +0500, Andrey Rakhmatullin wrote:
> On Fri, Dec 05, 2025 at 03:00:25PM +0530, jvk wrote:
> > > > I was able to make a playwirght project under my name space on
> > > > salsa
> > > > debian and i think have managed to get it in the format the
> > > > debian
> > > > needs with the 1.56.0 version.
> > > 
> > > It looks like you've manually made the "New upstream version
> > > 1.56.0+ds"
> > > commit and included generated files in it. This commit should be
> > > done
> > > by
> > > gbp import-orig instead.
> > I seriously cant understand what you mean, this is not helping.
> 
> I mean that simply using gbp import --orig, like you guides tell you,
> wouldn't produce the repo you linked, so you must have done something
> else. If you want help with this you can explain what did you do with
> details.
okay so i deleted the old repo and made a new one
https://salsa.debian.org/jvk_here/python-playwright/

These are the exact command which i executed
cd maintain_playwright/
  732  gbp clone
https://salsa.debian.org/jvk_here/python-playwright.git
  733  ls
  734  cd python-playwright/

  736  gbp import-orig --uscan
  737  cd ..
  738  tree

  740  clear
  741  tree -L 1
  742  cd python-playwright/
  743  dch -i 
	this is the updated changelog
	jvk@debian
:~/maintain_playwright/python-playwright$ cat 	debian/changelog 
	python-playwright (1.56.0+ds-1) UNRELEASED; urgency=medium

	  * Non-maintainer upload.
 	 * New upstream release

	 -- JVK <jaivkadam@gmail.com>  Fri, 05 Dec 2025 15:33:48 +0530

	python-playwright (1.55.0+ds-2) unstable; urgency=medium

	  * Fix debian/copyright.

	 -- Roland Mas <lolando@debian.org>  Wed, 29 Oct 2025 16:20:31
+0100

	python-playwright (1.55.0+ds-1) unstable; urgency=medium

	  [ Andreas Tille ]
	  * Initial packaging.

	  [ Roland Mas ]
	  * Build on Andreas's work, many thanks.
	  * New upstream release.

	 -- Roland Mas <lolando@debian.org>  Wed, 22 Oct 2025 12:27:30
+0200
		
  744  gbp import-orig
  745  git push
  746  history 

what i think is the next steps->
gbp-source (will make .dsc .changes and .tar.gz file)
then sbuild -d unreleased <whatever name>.dsc will test it?
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?)


> 
> > Ig it was you how told me to use git.
> 
> I told you to use git push instead of gbp push, because gbp push is
> not 
ouu hmm sorry
> suitable for your needs. Not sure if you mean that you decided to not
> use 
> any of the gbp tools instead.
> 
> > And what you are telling is not written in any workflow ,why?
> 
> I don't think this is true but you can elaborate.
like you told i have manully push things , i didn't find it anywhere

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

#17236

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

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.

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

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

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


-- 
WBR, wRAR

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

#17237

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

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

#17238

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

On Fri, Dec 05, 2025 at 04:29:44PM +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?

Using git push as well.

-- 
WBR, wRAR

[toc] | [prev] | [standalone]

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

csiph-web