On 06-12-2025 11:15, Carsten Schoenert wrote:
Hello Aryan, Am 06.12.25 um 06:59 schrieb Aryan Karamtoth:playwright is already in the salsa namespace of DPT [1] and you shouldpush 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.
I agree. Forking seems to be a better idea instead.
Apologies on my end, like I mentioned I haven't been able to read all of the previous threads as there were too many of them but I remember reading about them having difficulties with sbuild so I linked the guide for it. I personally use sbuild.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, Aryan Karamtoth, Sponsored Maintainer @Debian Ports Maintainer @FreeBSD Homepage: https://arklixs.in Matrix: @SpaciousCoder78:matrix.org XMPP: SpaciousCoder78@xmpp.earth GPG Fingerprint: 7A7D 9308 2BD1 9BAF A83B 7E34 FE90 07B8 ED64 0421
Attachment:
OpenPGP_0xFE9007B8ED640421.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature