Bug#792567: Bug#929747: qa.debian.org: Please add cross-buildability in summary
Hi, whoever takes a stab at implementing this, here is what worked for the distro tracker: https://salsa.debian.org/qa/distro-tracker/merge_requests/74 Thanks! cheers, josch signature.asc Description: signature
Bug#792567: Bug#929747: qa.debian.org: Please add cross-buildability in summary
Hi, On Mon, 3 Jun 2019 17:12:22 +0200 Helmut Grohne wrote: > On Thu, May 30, 2019 at 05:22:12PM +0200, Helmut Grohne wrote: > > On Thu, May 30, 2019 at 10:57:52AM +0200, Samuel Thibault wrote: > > > https://tracker.debian.org/ has a link to the cross-buildability status > > > of a package. It'd be useful to have a tick or cross on the > > > https://qa.debian.org/developer.php page, e.g. in the CI/Rep column, as > > > a link to the cross-buildability status, to be able to easily check the > > > status of one's own packages. > > > > If you do, please consider: > > * crossqa.d.n only works on unstable. If a package is not in unstable, > >there shouldn't be a link. (e.g. gcc-9) > > * crossqa.d.n only fills a page if there is some package built for one > >of the architectures being tested. Therefore no link should be > >emitted for indep-only packages. Currently, we test for any non-x86 > >release architecture, so if a package only builds for some x86, it > >will be 404 as well. > > > > If some API is missing in the service, please get in touch with me. > > I talked with Christoph about the missing APIs and it became clear to us > that publishing cross build status doesn't make sense as long as > satisfiability isn't published. qa.d.o. does compute satisfiability for > a while now: > > https://qa.debian.org/dose/debcheck/cross_unstable_main_amd64/ > > Please integrate a satisfiability status before integrating crossqa.d.n. > 50% of packages are cross-unsatisfiable, so this is the big fish. bug #792567 is also relevant in this context. This bug asks for including cross build dependency satisfiability from qa.d.o/dose/debcheck. Bug #792567 asks for including build dependency and normal dependeny satisfiability results from qa.d.o/dose/debcheck. Since the data for both issues comes from the same source and since the data for both issues is exported in the same format, fixing one of these bugs will make it trivial to also fix the other. As the author of the feature that made qa.d.o/dose/debcheck export machine readable data and as the author of some commits to distro-tracker (which already includes the results of qa.d.o/dose/debcheck), I wanted to give an overview of the machine readable interface to qa.d.o/dose/debcheck. Basically you are interested in: https://qa.debian.org/dose/debcheck/SCENARIO/latest/some.txt Where SCENARIO can be one of: - "unstable_main" for dependency satisfaction problems of binary packages in unstable - "src_unstable_main" build dependency satisfaction of source packages in unstable - "cross_unstable_main" cross build dependency satisfaction of source packages built on amd64 for all other release architectures in unstable The format is line-based and values are separated by a '#'. The values are: - package name - version - whether the package is arch:all - a anchor hash so that you can directly link to the problem instance via https://qa.debian.org/dose/debcheck/SCENARIO/latest/packages/PKGNAME.html#ANCHOR - a human readable short summary of the problem - the architectures exhibiting the problem, separated by spaces Additionally, qa.d.org/dose/debcheck offers a per-source view under URLs of this format: https://qa.debian.org/dose/debcheck/src/PKGNAME.html where PKGNAME is a source package name. These pages are only computed for source packages that either produce binary packages with dependency problems or that suffer from (cross) build dependency problems themselves. Feel free to prod me if you need any help in making sense out of the data that comes out of qa.d.o/dose/debcheck. Thanks! cheers, josch signature.asc Description: signature
Bug#929747: qa.debian.org: Please add cross-buildability in summary
Helmut Grohne, le lun. 03 juin 2019 17:12:22 +0200, a ecrit: > What we need here is more people working on the difficult issues, not > random maintainers staring at undecipherable cross build failures. Ok :) > What we also need is maintainers replying to bug reports and > converting their packages to using debhelper. I get the feeling that > we're putting priorities in the wrong order. > > I'm sorry if this comes across a little blunt, but some of this looks > to me like wasting people's time. No problem, the rationale is clear and now recorded in an appropriate bug report :) Samuel
Bug#929747: qa.debian.org: Please add cross-buildability in summary
Control: clone -1 -2 Control: retitle -2 qa.debian.org: Please add cross build satisfiability in summary Control: block -1 by -2 On Thu, May 30, 2019 at 05:22:12PM +0200, Helmut Grohne wrote: > On Thu, May 30, 2019 at 10:57:52AM +0200, Samuel Thibault wrote: > > https://tracker.debian.org/ has a link to the cross-buildability status > > of a package. It'd be useful to have a tick or cross on the > > https://qa.debian.org/developer.php page, e.g. in the CI/Rep column, as > > a link to the cross-buildability status, to be able to easily check the > > status of one's own packages. > > If you do, please consider: > * crossqa.d.n only works on unstable. If a package is not in unstable, >there shouldn't be a link. (e.g. gcc-9) > * crossqa.d.n only fills a page if there is some package built for one >of the architectures being tested. Therefore no link should be >emitted for indep-only packages. Currently, we test for any non-x86 >release architecture, so if a package only builds for some x86, it >will be 404 as well. > > If some API is missing in the service, please get in touch with me. I talked with Christoph about the missing APIs and it became clear to us that publishing cross build status doesn't make sense as long as satisfiability isn't published. qa.d.o. does compute satisfiability for a while now: https://qa.debian.org/dose/debcheck/cross_unstable_main_amd64/ Please integrate a satisfiability status before integrating crossqa.d.n. 50% of packages are cross-unsatisfiable, so this is the big fish. Once that is done, we should revisit the cross-buildability as we have failures for roughly one sixth of the archive and patches for 1/14 of the archive. In other words: Every third cross build failure has a patch sitting in the BTS already. So for now, just checking whether your package has a patch is a much better use of your time. Beyond that, more than half of the patches essentially are "use debhelper". What we need here is more people working on the difficult issues, not random maintainers staring at undecipherable cross build failures. What we also need is maintainers replying to bug reports and converting their packages to using debhelper. I get the feeling that we're putting priorities in the wrong order. I'm sorry if this comes across a little blunt, but some of this looks to me like wasting people's time. Helmut
Bug#929747: qa.debian.org: Please add cross-buildability in summary
Hi, On Thu, May 30, 2019 at 10:57:52AM +0200, Samuel Thibault wrote: > https://tracker.debian.org/ has a link to the cross-buildability status > of a package. It'd be useful to have a tick or cross on the > https://qa.debian.org/developer.php page, e.g. in the CI/Rep column, as > a link to the cross-buildability status, to be able to easily check the > status of one's own packages. If you do, please consider: * crossqa.d.n only works on unstable. If a package is not in unstable, there shouldn't be a link. (e.g. gcc-9) * crossqa.d.n only fills a page if there is some package built for one of the architectures being tested. Therefore no link should be emitted for indep-only packages. Currently, we test for any non-x86 release architecture, so if a package only builds for some x86, it will be 404 as well. If some API is missing in the service, please get in touch with me. Helmut
Bug#929747: qa.debian.org: Please add cross-buildability in summary
Package: qa.debian.org Severity: normal Hello, https://tracker.debian.org/ has a link to the cross-buildability status of a package. It'd be useful to have a tick or cross on the https://qa.debian.org/developer.php page, e.g. in the CI/Rep column, as a link to the cross-buildability status, to be able to easily check the status of one's own packages. Samuel -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.0 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Samuel FYLG> Tiens, vlà une URL qui va bien : FYLG> ftp://127.0.0.1/WaReZ/NiouZeS/WinDoZe/NeWSMoNGeR/SuPeR c'est gentil sauf que l'adresse ne fonctionne pas sa me fais une erreur -+- Furtif in Guide du Neuneu Usenet : -+-
