From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel@gnu.org
Subject: Re: Getting ‘core-updates’ merged
Date: Thu, 22 Nov 2018 10:41:59 +0100 [thread overview]
Message-ID: <875zwpcuu0.fsf@gnu.org> (raw)
In-Reply-To: <87muq7oko8.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Sat, 17 Nov 2018 15:14:47 +0100")
Hi there!
ludo@gnu.org (Ludovic Courtès) skribis:
> What remains to be done is mostly (1) ensuring that there’s no
> significant regression in terms of build failures compared to ‘master’,
> and (2) making sure GuixSD boots and works fine.
>
> For #1, a simple test is to try and upgrade your profile and see if
> everything builds and works well. In addition, you can look at these
> dashboards to identify build failures that need to be addressed:
>
> https://hydra.gnu.org/jobset/gnu/core-updates
> https://berlin.guixsd.org/jobset/core-updates-core-updates
There are still failures out there!
https://hydra.gnu.org/eval/110331?full=1#tabs-still-fail
The above list is slightly outdated so I’m restarting an evaluation on
hydra.gnu.org.
A prominent issue is LibreOffice:
https://lists.gnu.org/archive/html/guix-devel/2018-11/msg00332.html
There are also many more issues on armhf and i686 than on x86_64.
> For #2, running “make check-system”, or at least the inexpensive subset
> of system tests (the expensive tests are the installation tests) should
> give a good overview—Mark already reported an issue at
> <https://issues.guix.info/issue/33362>. The next step of course is to
> try it on the bare metal for your own system config.
I’m running GuixSD from ‘core-updates’ and everything is working fine.
:-) (I’m using Xorg, NM, etc., but not GNOME.)
Please check if it works for you! We need your help!
Ludo’.
next prev parent reply other threads:[~2018-11-22 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57 ` Marius Bakke
2018-11-16 18:10 ` Ludovic Courtès
2018-11-16 21:15 ` Ricardo Wurmus
2018-11-16 21:20 ` Ludovic Courtès
2018-11-16 22:03 ` Björn Höfling
2018-11-17 0:58 ` Gábor Boskovits
2018-11-17 14:14 ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22 9:41 ` Ludovic Courtès [this message]
2018-11-22 19:54 ` Björn Höfling
2018-11-23 13:52 ` Ludovic Courtès
2018-11-23 21:44 ` Julien Lepiller
2018-11-24 9:19 ` Danny Milosavljevic
2018-11-25 15:54 ` Ludovic Courtès
2018-11-26 17:59 ` Danny Milosavljevic
2018-11-26 18:18 ` Danny Milosavljevic
2018-11-28 10:46 ` Ludovic Courtès
2018-11-26 17:54 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zwpcuu0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).