unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: core-updates summer 2017
Date: Tue, 18 Jul 2017 15:45:34 +0200	[thread overview]
Message-ID: <87fudtyi2p.fsf@gnu.org> (raw)
In-Reply-To: <87fudv8aa9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 17 Jul 2017 15:26:06 +0200")

Hi!

ludo@gnu.org (Ludovic Courtès) skribis:

> Leo Famulari <leo@famulari.name> skribis:
>
>> On Mon, Jul 10, 2017 at 04:47:06PM -0400, Leo Famulari wrote:
>>> Let's use this thread to discuss the state of the branch.
>>
>> I've reconfigured and rebooted my x86_64-linux GuixSD system based on
>> the latest core-updates (2f0d1b9dd2d75c5501767a15cf9b87fc057711c0).
>>
>> There are some new warnings / errors during early boot, that read like
>> this:
>>
>> ------
>> ;;; WARNING: loading compiled file /gnu/store/...-module-import-compiled/gnu/build/linux-boot.go failed:
>> ;;; ERROR: In procedure make_objcode_from_file: bad header on object file: "\x7fELF\x02\x01\x01ÿ\x00\x00\x00\x00\x00\x00\x00\x00"
>> ------
>>
>> This seems reminiscent of the object format change between Guile 2.0 and
>> Guile 2.2, but I'm not sure what's going on. I've attached photos of my
>> screen, which provide some more context.
>
> It looks like the initrd is still running Guile 2.0 but getting 2.2
> modules.

This is fixed as of ef03d8dc3724caf59c7ea4a551084ddc601e4597.  I can
build and run my GuixSD config with ‘guix system vm’ at this point.  \o/

Ludo’.

  parent reply	other threads:[~2017-07-18 13:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 20:47 core-updates summer 2017 Leo Famulari
2017-07-11  0:13 ` Kei Kebreau
2017-07-12  5:56   ` Leo Famulari
2017-07-12  5:47 ` Leo Famulari
2017-07-14 16:50 ` core-updates failing packages Leo Famulari
2017-07-19 23:09   ` Ben Woodcroft
2017-07-20  6:17     ` Ricardo Wurmus
2017-07-23  1:34       ` Ben Woodcroft
2017-07-23 11:05         ` Ricardo Wurmus
2017-07-20 12:17     ` Staging [was Re: core-updates failing packages] Leo Famulari
2017-07-20 15:01       ` Ludovic Courtès
2017-07-24 15:44   ` core-updates failing packages Ludovic Courtès
2017-07-24 17:59     ` Leo Famulari
2017-07-25 22:16       ` Marius Bakke
2017-07-24 20:17     ` Leo Famulari
2017-07-26  6:36   ` revert perl-5.26.0 update? Efraim Flashner
2017-07-27  9:03     ` Ludovic Courtès
2017-07-27  9:22       ` Efraim Flashner
2017-07-27 17:34       ` Leo Famulari
2017-07-27 18:11       ` Leo Famulari
2017-07-27 18:31         ` Efraim Flashner
2017-07-27 22:07       ` Leo Famulari
2017-07-27 23:07         ` Leo Famulari
2017-07-28 21:26         ` Ludovic Courtès
2017-07-30 20:23           ` Leo Famulari
2017-07-30 22:56             ` core-updates: biber Leo Famulari
2017-07-31  7:26               ` Ricardo Wurmus
2017-08-04 15:24                 ` Leo Famulari
2017-08-05 19:26                 ` Leo Famulari
2017-08-05 22:38                   ` Leo Famulari
2017-08-06  9:44                     ` Ricardo Wurmus
2017-08-06 20:37                       ` Leo Famulari
2017-08-07 18:47                       ` Ricardo Wurmus
2017-08-07 18:59                         ` Leo Famulari
2017-08-06 10:14                     ` Andreas Enge
2017-08-06 20:36                       ` Leo Famulari
     [not found] ` <20170713002237.GA16753@jasmine.lan>
2017-07-13  3:10   ` core-updates summer 2017 Leo Famulari
2017-07-17 13:26   ` Ludovic Courtès
2017-07-17 20:59     ` Leo Famulari
2017-07-18  9:59       ` Ludovic Courtès
2017-07-18 13:45     ` Ludovic Courtès [this message]
2017-07-18 18:56       ` Leo Famulari

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=87fudtyi2p.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).