Hello Guix! I’d like to propose merging ‘core-updates’ real soon, say by next week, Friday 30th.
But first, this branch started about a year ago (!), and it’s hard for someone who’s not following IRC 7 days a week to figure out what the status is—something we should definitely improve on. An overview in terms of package coverage can be found here: https://qa.guix.gnu.org/branch/core-updates To view “blocking builds” (packages that fail to build and thus “block” all those that depend on it), say for i686-linux, see: https://data.qa.guix.gnu.org/revision/aab1fe98574e1cd4c7911c1e5571b3733fb71d67/blocking-builds?system=i686-linux&target=none&limit_results=50 or run: ./pre-inst-env guix weather -s i686-linux -c 200 from a ‘core-updates’ checkout. This gives an idea where to focus our efforts. You can also browse individual ci.guix builds at: https://ci.guix.gnu.org/eval/latest/dashboard?spec=core-updates Currently, we’re at ~95% on x86_64-linux, 80–90% on the other *-linux systems, and ~2% on i586-gnu (GNU/Hurd; that’s more or less where we were before.) Note that ci.guix is still struggling with aarch64-linux build and hasn’t even attempted armhf-linux builds, but bordeaux.guix is doing well. I’m aware of at least one important issue that prevents use of Guix System on i686-linux: https://issues.guix.gnu.org/72725 To me, that’s the last blocker, even though there’s room for improvement here and there (for instance, FFmpeg currently fails to build on i686-linux). Anything else? A number of people already provided feedback informally after reconfiguring their systems on ‘core-updates’. Please share your experience, positive or negative, here! Ludo’.
