unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Core-updates after the staging merge
Date: Mon, 17 Apr 2023 08:18:00 +0000	[thread overview]
Message-ID: <878reqzzg5.fsf@kitej> (raw)
In-Reply-To: <ZDvXTibhTwsmXLZz@jurong>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Andreas Enge <andreas@enge.fr> skribis:

> Hello all,
>
> the merge of staging to master, and the subsequent merge of master to
> core-updates did break a few things; but on the positive side, we are
> halfway there with getting rid of the staging and core-updates branches ;-)
> CI has almost caught up on x86_64; looking at the dashboard at
>    https://ci.guix.gnu.org/eval/402403/dashboard
> shows much more red than on master, so we will need to do some more work
> before the merge. Since it is ordered alphabetically and our package names
> often start by the language, red streaks often indicate problems with
> a given programming language. There are things to work on for most of the
> teams!
>
> [...]
> - Everything common lisp related is red (cl-*, sbcl-*), but maybe there
>   is a similar thing going; or maybe not, since clisp is built.
> [...]

Hi,
I tried to build the 1611 dependents of sbcl on x86-64, and most of them
build fine. I get only 6 failures, some of them because some
dependencies like mysql or supercollider are failing to build.
So overall, Common Lisp packages on core-updates are in a pretty good
shape.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2023-04-17  8:27 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57   ` Andreas Enge
2023-04-17  8:06     ` Andreas Enge
2023-04-17  8:18 ` Guillaume Le Vaillant [this message]
2023-04-17  8:33   ` Core-updates after the staging merge Andreas Enge
2023-04-17  9:03 ` Andreas Enge
2023-04-17  9:56   ` Andreas Enge
2023-04-17 12:19     ` Simon Tournier
2023-04-17 12:38       ` Andreas Enge
2023-04-17 12:57         ` Simon Tournier
2023-04-17 14:12       ` Lars-Dominik Braun
2023-04-17 17:47         ` Simon Tournier
2023-04-17 18:07           ` Andreas Enge
2023-04-17 19:01             ` Lars-Dominik Braun
2023-04-18 17:16               ` Andreas Enge
2023-04-21 18:29                 ` Lars-Dominik Braun
2023-04-17 12:57   ` Andreas Enge
2023-04-17 18:03   ` Maxim Cournoyer
2023-04-17 18:08     ` Andreas Enge
2023-04-18  5:04   ` John Kehayias
2023-04-18 17:38     ` Andreas Enge
2023-04-19 10:48   ` Latest news on core-updates Andreas Enge
2023-04-19 10:58     ` Christopher Baines
2023-04-19 12:41       ` Andreas Enge
2023-04-21  7:58         ` Andreas Enge
2023-04-21 13:01           ` Maxim Cournoyer
2023-04-20 13:56       ` Christopher Baines
2023-04-20 18:09         ` Andreas Enge
2023-04-21  8:20     ` Simon Tournier
2023-04-21  8:47       ` Andreas Enge
2023-04-21 11:31         ` Simon Tournier
2023-04-21 16:12     ` Katherine Cox-Buday
2023-04-21 16:12       ` Katherine Cox-Buday
2023-04-21 17:04       ` reza.housseini
2023-04-23  7:17         ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2023-04-18  5:11 Core-updates after the staging merge John Kehayias

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=878reqzzg5.fsf@kitej \
    --to=glv@posteo.net \
    --cc=andreas@enge.fr \
    --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).