Hi, Quoting Timo Röhling (2022-09-11 16:08:29) > * Johannes Schauer Marin Rodrigues <josch@debian.org> [2022-09-08 13:31]: > >It would be nice to display cross-build-failures on tracker.d.o > >or other packaging overviews but that doesn't make sense if there is not enough > >person-power to solve these problems. > While a TODO item in tracker.d.o might still be a bit too much, it > would be nice to have a cross build indicator in DDPO or DMD, so > maintainers who have an interest can see at a glance which of their > packages FTCBFS. unfortunately, whether a source package FTCBFS or not is not quite binary. The failure can be due to a temporary multi-arch version skew, you can have the same version be either successful or failing depending on when you look or you can have source packages that cross-build fine to some but not all arches. > Personally, I'll gladly fix cross-build issues in my packages whenever I > notice them (and know how to fix them), but I'm usually too lazy to manually > check if crossqa.d.n has something to say about my packages. Or is there a > way to list packages by maintainer of which I am not aware? The problem with displaying these is that maintainers might quickly learn that they cannot do anything about most of the FTCBFS and then learn to ignore them. Teaching them to ignore the FTCBFS is not useful. See Helmut's other mail in this bug. qa.debian.org/developer.php can have columns that are hidden by default. Maybe that would be a good fit for now? Thanks! cheers, josch
Attachment:
signature.asc
Description: signature