Re: coordination between lintian/piuparts/adequate
Holger Levsen <[email protected]>
| Newsgroups | gmane.linux.debian.devel.quality-assurance,gmane.linux.debian.devel.lint.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Dec 10, 2024 at 09:38:57PM +0100, Serafeim (Serafi) Zanikolas wrote: > > Probably adequate is the logical place for this test, but adequate > > doesn't build/run on ports architectures since it moved to golang, > > so piuparts should probably keep its tests on those arches until > > adequate moves to a more portable language or golang gets ported. > that's because unsupported ports architectures have not caught up to go 1.21, > which was released ~1.5 year ago. I'd claim that that says more about the > viability of those ports, than the suitability of go for Debian tooling. if you > feel strongly otherwise, I'd be happy to continue this discussion with a wider > audience at <[email protected]> rather than reply here I dont feel strongly about this, but I'd like to point out that I disagree. IMO it was wrong to rewrite adequate (as any central QA tool for Debian) in a language which is not available *everywhere*. > piuparts relies on humans to file bugs. autopkgtest on the other hand blocks > package migration to testing (that is, when one does not run autopkgtst before > upload). it's nice that some humans (including yourself) file bugs, but that > doesn't seem viable long-term. >90% of the piuparts bugs in the last 2 decades have been filed by 3 people, this might not seem viable long-term to you, but in practice it has been proven to be viable long-term. also: piuparts failures block migrations without anyone having to file bugs, just like autopkgtest. (oh, and for autopkgtests related bugs, there are also very few humans filing them.) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Any business accepting Bitcoin is participating in the human race’s suicide.
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmdZZkAACgkQCRq4Vgaa qhxX2w//TI+cMX17eO6EOonTrhCdDYcXd+PwTmETA0W02oZhWcnYLIkMDCByrJrd fpf6YXAYhXl8L6KgXYEhWTBjoXJULAH3/5wk40CxGHWqI/MThU4x21dPF0dsTmFC SW3HXF1UIV3sPjwyFnmWqxcNbCTldtNvUdS1+9oyRSIvzL76nMgkkBVPtQ0ggeY8 548F4i3MPX2EwTK8TedTZt3m0DUw80BasnI0WDYnrWKEX2nVLaHRXaVj6kbxZAeq h+s5ixRJd9xiXoxcD/AnNhBhKgBg9V4JpyDK0OS8eZYCAz87jRko42MPLCmCk0qA IQDdoXVO8o47Fa54B5+WU79ecyzbyLsfIVAMHku1abn3UwDr4MXsyG0/1YjcO7Vn OWsVtCvaA/SYclMcNcuZ1uU2IO+lBwgvyp4hOZAGY/ERcr06UjD9a/HEeE12ibzJ zkj1yeoUpH0x8doEoJGNyrS1Niij7dpHmX6d2UP8e/jUm5rjgDJmlLUQHrAPWpoM YRyAmvSscfM0gGpVlyMuvka+9oWhl5JXPnDCiiKzcAhQQe05zaPkV0NI8/VGhu6G U6FHxkmkUlK99QEtZ89LogUfiSBp8KxexVcKyYEW1Hn4XUcGhYAl2hb6yygCivQu o4NrG8ZYipkwsiqSXgerGAA41u+vLNikef14GKTRYyfoJXK9qMA= =fxxO -----END PGP SIGNATURE-----