From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release progress, week 8
Date: Sun, 04 Dec 2022 13:06:02 +0100 [thread overview]
Message-ID: <87fsdvwez9.fsf@gnu.org> (raw)
In-Reply-To: <877cz9pgr3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 02 Dec 2022 23:45:04 +0100")
Hey,
Thanks for your hard work to publish the RC1!
> Now we need reports from users to act upon. I’d say we can decide next
> week whether we need an RC2 or not. I can handle the next release
> candidate or the release itself, but I’ll be unavailable on Dec. 12–15.
I noticed that we have failing tests on the version-1.4.0-tests
specification.
- docker-system (https://ci.guix.gnu.org/build/215380/details)
- prosody (https://ci.guix.gnu.org/build/215424/details)
that fail both on Berlin and on my machine and,
- fail2ban-extension (https://ci.guix.gnu.org/build/215447/details)
that only fails on Berlin.
There is also an issue with the system images. The following images are
failing on Berlin:
- novena-barebones-raw-image (https://ci.guix.gnu.org/build/215363/details)
- pine64-barebones-raw-image (https://ci.guix.gnu.org/build/215361/details)
- pinebook-pro-barebones-raw-image (https://ci.guix.gnu.org/build/215362/details)
It seems that those failures are caused by an issue during info-reader
build. I cannot reproduce it locally though.
Having an RC2 with all the tests passing and images buildable could be
nice.
On the other hand, I don't have much bandwidth to fix those issues and
they should not prevent us from releasing I guess.
Mathieu
next prev parent reply other threads:[~2022-12-04 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 22:45 Release progress, week 8 Ludovic Courtès
2022-12-02 23:48 ` Vagrant Cascadian
2022-12-03 17:53 ` Ludovic Courtès
2022-12-04 1:55 ` missing sanity check Vagrant Cascadian
2022-12-03 10:10 ` Release progress, week 8 zimoun
2022-12-04 5:32 ` Maxim Cournoyer
2022-12-04 10:38 ` zimoun
2022-12-05 14:43 ` Ludovic Courtès
2022-12-03 17:55 ` Julien Lepiller
2022-12-05 14:44 ` Ludovic Courtès
2022-12-04 12:06 ` Mathieu Othacehe [this message]
2022-12-06 14:32 ` Ludovic Courtès
2022-12-07 9:34 ` Mathieu Othacehe
2022-12-06 16:51 ` Ludovic Courtès
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=87fsdvwez9.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.