Am Mon, Apr 27, 2026 at 02:44:07PM +0200 schrieb Hugo Buddelmeijer: > Ah yes, I was looking at QA: > https://data.qa.guix.gnu.org/job/19775 > Because I find the "blocking-builds" the most useful interface to figure out > the most important package to fix.
I agree, that is very useful once the builds are started; here we are still stuck in the evaluation phase, and the more information sources, the better. > Is it possible to restart the data.qa build as well? The easiest way is to rebase. > > And then there is the big blog > > over pages and pages of output, which is completely mysterious to me. > Is this the actual error that prevents the evaluation? No idea... > We need to resolve those conflicts at some point anyway right? I wouldn't > know how to do so though. I (hopefully...) just did, by comparing the conflicting commit on python-team Author: Yan Abu Arab <[email protected]> Date: Thu Feb 5 16:57:56 2026 +0200 gnu: maturin: Update to 1.11.5. with commit af2b12e51fb69d5ad1ea700816614957be0d872b on master Author: Efraim Flashner <[email protected]> Date: Thu Apr 23 16:21:10 2026 +0300 gnu: rust-crates: Remove some rust crates. The former adds one crate next to a location where the latter removes one, and the merge diff only shows that the commit to be applied has two more crates than master. So I kept the new one and dropped the removed one. Pushing soon again, Andreas
