From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <bavier@cray.com>
Cc: 30879@debbugs.gnu.org
Subject: bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization
Date: Wed, 21 Mar 2018 00:12:02 +0100 [thread overview]
Message-ID: <877eq6ibp9.fsf@gnu.org> (raw)
In-Reply-To: <20180320154302.GL105827@pe06.us.cray.com> (Eric Bavier's message of "Tue, 20 Mar 2018 10:43:02 -0500")
Hello Eric,
Eric Bavier <bavier@cray.com> skribis:
> scheme@(guile-user)> (@@ (gnu tests base) %simple-os)
> $1 = #<<operating-system>
> kernel: #<package linux-libre@4.15.7 ...>
> kernel-arguments: ()
> bootloader: #<<bootloader-configuration> bootloader: ...>
> initrd: #<procedure base-initrd ...>
> initrd-modules: ()
> firmware: "komputilo"
> host-name: #f
> hosts-file: ()
> mapped-devices: (#<<file-system> device: "my-root" ...> #<<file-system> ...> ...)
> file-systems: ()
> swap-devices: (#<<user-account> name: "alice" ...> ...)
> ...
>
> Notice e.g. the "firmware" field has that value that should be in
> "host-name", which has the value "hosts-file" should have, and
> "mapped-devices" has the value "file-systems" should have, etc.
>
> If you explicitely specify the new "initrd-modules" field this commit
> added in (@ (gnu tests) %simple-os), then compilation proceeds as
> expected.
That sounds a lot like regular ABI breakage: a new <operating-system>
field was added but gnu/tests/base.go wasn’t rebuilt, and thus was
expecting the previous struct layout.
Does “rm gnu/tests/base.go && make” suffice to fix this issue?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-03-20 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 15:43 bug#30879: Commit bc499b113 broke guix on guile@2.0.14, improper <operating-system> field initialization Eric Bavier
2018-03-20 23:12 ` Ludovic Courtès [this message]
2018-03-21 15:16 ` Eric Bavier
2018-03-21 21:04 ` Ludovic Courtès
2018-03-21 21:14 ` Eric Bavier
2018-03-21 23:04 ` Ludovic Courtès
2018-03-22 14:45 ` Eric Bavier
2018-03-22 16:19 ` Ludovic Courtès
2018-03-29 17:06 ` Eric Bavier
2018-05-15 9:20 ` Ludovic Courtès
2018-04-11 18:42 ` Eric Bavier
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=877eq6ibp9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30879@debbugs.gnu.org \
--cc=bavier@cray.com \
/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).