Re: Playwright version bump and testing
Hello Aryan,
Am 06.12.25 um 06:59 schrieb Aryan Karamtoth:
playwright is already in the salsa namespace of DPT [1] and you should
push your changes there instead.
No!
Not yet now! I don't understand why this wish of behaving is constantly
repeated. People should use their namespace while learning all the
stuff, 20 commits back and forth about small changes that could have
been rebased before makes it no easier for me to understand what did happen.
Follow the instructions here [2] and join the Debian Python Team's
Salsa namespace.
That's doable at any time but not necessarily needed now to work on that
package. First things first.
Since you're going for NMU of an existing package, just run the build
directly. I use sbuild and it performs the tests automatically since the
upstream already has tests for this package.
Things do work automatically if there is a setup to do so. There is no
difference between git-pbuilder and sbuild here. git-pbuilder has a very
conservative default setting as we all have different ways of doing things.
I've configured my setup of git-buildpackage to do most of the things
automatically too. But it's up to you as user to do this.
For sure we can do better the documentation of how the DPT is working
and the workflows we use.
Not sure why you had difficulties with sbuild in the first place. This
manual [3] is a very straightforward process to set up sbuild in a few
minutes. sbuild makes it a lot easier to build, test and identify
lintian errors.
So pbuilder does not? Where is the difference in gbp buildpackage
--git-builder=sbuild vs. =pbuilder vs. =debuild?
And I disagree, sbuild isn't that straightforward or at least wasn't
that straightforward as you think. Using git-pbuilder is quite damn
simple and I always suggest this newcomers.
https://wiki.debian.org/git-pbuilder (for completeness)
sbuild itself has nothing to do with Lintan or autopkgtest directly nor
pbuilder has.
The question Jai has is a valid question, I wished maintainers would
take more the opportunity of using the fie README.Debian to explain the
state of packaging, what is missing or needed or other things that might
be important to know. Or at least a small comment in d/rules.
--
Regards
Carsten
Reply to: