unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Core-updates, the last metres
Date: Sun, 23 Apr 2023 09:30:05 +0200	[thread overview]
Message-ID: <ZETefUUbMqUnSMvO@jurong> (raw)

Hello,

yesterday I updated my system to core-updates. Since I am writing this
message now, you can deduce that it succeeded. Well, there is no reason
you should care, but it could encourage you to do the same. :)

I used commands like "./pre-inst-env guix package/system ...", but this
resulted in strange behaviour; I suppose I may have ended up with a
mixture between old and new guix.
I think the safest approach is to use "guix pull --commit=..." with
a commit from core-updates, or probably just
   guix pull --commit=core-updates
Then I would start by updating the system, followed by the user profiles.

Please tell us if there is a show-stopper for the merge!

We already received a first report:
python-yubikey-manager does not build. It should be repaired very shortly
after the merge (the fix is there, but would cause too many rebuilds now);
so if you rely on it, maybe delay updating your system, or hold this one
package back in your profile ("guix package --do-not-upgrade ... -u").

As for the architectures, x86_64 looks good; i686 and powerpc64le look
okay (or at least not much worse than on master; R does not work on
powerpc64le, and should also be fixed shortly after the merge).
For aarch64 it is difficult to say, since the build farm has trouble
keeping up. We brought back a few machines, but they are churning through
the backlog.

Andreas



             reply	other threads:[~2023-04-23  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  7:30 Andreas Enge [this message]
2023-04-23 18:51 ` Core-updates, the last metres John Kehayias
2023-04-23 19:25   ` Andreas Enge
2023-04-23 20:00   ` Guillaume Le Vaillant
2023-04-23 21:12     ` John Kehayias
2023-04-24 10:00       ` Josselin Poiret
2023-04-24 10:01         ` [PATCH] gnu: python-shiboken-2: Do not rely on _Py_Mangle being available Josselin Poiret
2023-04-24 10:57           ` Andreas Enge
2023-04-23 23:32     ` python-ledgerblue as input for electrum? (was: Core-updates, the last metres) Vagrant Cascadian
2023-04-23 23:45       ` 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=ZETefUUbMqUnSMvO@jurong \
    --to=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).