From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org
Subject: Release progress, week 7
Date: Thu, 24 Nov 2022 17:47:42 +0100 [thread overview]
Message-ID: <87bkowcn9t.fsf@gnu.org> (raw)
Hello Guix!
Release progress: week 7.
• ‘make assert-binaries-available’ reports 99% coverage (details
below). 💪
• Architectures:
- i586-gnu: Instead of dropping i586-gnu from
‘etc/release-manifest.scm’, I fixed a few things, running ‘guix
build’ on berlin to get substitutes there—almost there!
- armhf-linux: I started builds manually on berlin and we’re almost
done.
- aarch64-linux, powerpc64le-linux: Likewise, filled the gaps
manually and now we’re passing on both!
• Installer:
We seem to be ready to call for testing.
• Release issue <https://issues.guix.gnu.org/53214> blocked by 1 open
bug (1 fixed, 1 removed, and 1 new since last week):
59519 LibreOffice 7.3.5.2 fails to build on i686-linux
• Others:
- Some Cuirass, offload, and infrastructure issues were fixed:
<https://issues.guix.gnu.org/59493>
<https://issues.guix.gnu.org/59447>
Others are investigated: <https://issues.guix.gnu.org/59510>.
- Nautilus crash fixedL <https://issues.guix.gnu.org/58221>
Mathieu created a ‘version-1.4.0’ branch. As soon as ‘make
assert-binaries-available’ passes, I think we can produce a release
candidate (in the process we may find a couple of issues to fix) and
call for testing. This could be done by next week.
Thoughts?
Ludo’.
Week 6: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00161.html
Week 5: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00026.html
Week 4: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00026.html
Week 3: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00293.html
Week 2: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00210.html
Week 1: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00137.html
computing 400 package derivations for x86_64-linux...
looking for 507 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org ☀
99.0% substitutes available (502 out of 507)
at least 4,800.6 MiB of nars (compressed)
8,080.7 MiB on disk (uncompressed)
0.140 seconds per request (0.8 seconds in total)
7.1 requests per second
0.0% (0 out of 5) of the missing items are queued
at least 1,000 queued builds
aarch64-linux: 990 (99.0%)
powerpc64le-linux: 8 (.8%)
x86_64-linux: 2 (.2%)
build rate: 339.14 builds per hour
x86_64-linux: 302.52 builds per hour
i686-linux: 41.67 builds per hour
Substitutes are missing for the following items:
/gnu/store/c10jgnxjx5qx2h4lqy5h4ar6qidn7fmi-libreoffice-7.3.5.2 i686-linux
/gnu/store/d30mmhijhyy4kkykxikc28bnj9iad7zh-gcc-toolchain-12.2.0-debug i586-gnu
/gnu/store/gz7l1491gwznwhwssd2h13y5ykrks11q-gcc-toolchain-12.2.0 i586-gnu
/gnu/store/sfaigxk5z4xxxn8y1v05c2lz3hgb63gy-gcc-toolchain-12.2.0-static i586-gnu
/gnu/store/v7xmdapgwgqgcnacf3qmapahgwfbgcsq-emacs-28.2 armhf-linux
reply other threads:[~2022-11-24 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkowcn9t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.