Am Thu, Mar 30, 2023 at 07:27:55PM -0400 schrieb Leo Famulari: > > It is possible to use data.guix.gnu.org to create these comparisons. > > Sometimes it takes me a few minutes to remember how to do it, so the UI > > could grow some hints or "affordances". I'll provide an example later > > today, when I am near a computer.
And this now also works: https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=5c893787be78a79433fe1343f5b70cd647e8f667&target_commit=51b8385acd6f7de668a994fe0523b3861240cd1a&system=x86_64-linux&target=none&build_change=broken&after_name=&limit_results=400 It finds 298 packages with problems on x86_64, which is suspiciously few. Actually unless I made a mistake, these are packages that build on master, but are broken on core-updates. I see more broken packages on core-updates, but it is quite possible that these are also broken on master... Not really: kcodecs builds on master, but not on core-updates, but it is not (yet) "broken" because it has not been scheduled yet. So expect the 298 to rise! Maybe it would be an idea to add "maybe broken" (was green, is blue) and "maybe fixed" (was red, is blue) to the search? And those that were and remain blue could go anywhere... Many thanks to Chris for making this possible! My impression is that we are making useful progress on the tooling; due to this website and ci working, it is finally possible to make assertions on core-updates beyond what I see when trying to build my own, subjective profile. Andreas
