From: Vagrant Cascadian <vagrant@debian.org>
To: 30021@debbugs.gnu.org
Subject: bug#30021: system build: unable to parse multi-line device-mapping
Date: Sun, 07 Jan 2018 19:24:27 -0800 [thread overview]
Message-ID: <87efn11190.fsf@aikidev.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
After several weeks of not using a machine, and updating guix to
guix (GNU Guix) c04ffadbed7412545555b8be6b78f23eed150d26
Running "guix build system /etc/config.scm" resulted in:
guix system: error: failed to load '/etc/config.scm':
/etc/config.scm:23:9: /etc/config.scm:23:9: In procedure allocate-struct: Wrong type argument in\
position 2: 3
This roughly corresponded to my mapped device section in
/etc/config.scm:
(mapped-devices
(list (mapped-device
(source (uuid "c106e43e-0479-4135-a1a8-b5221312bf74"))
(target "cryptic")
(type luks-device-mapping))))
Moving it all into a single line worked around the issue, but is a good
deal harder to read:
(mapped-devices (list (mapped-device (source (uuid "c106e43e-0479-4135-a1a8-b5221312bf74")) (target "cryptic") (type luks-device-mapping))))
My guess is it has something to do with some commits relating to
validating mapped devices:
42ff7d3be642d66ba567f64882a1f2301b1a7bd9
mapped-devices: 'luks-device-mapping' checks its source device.
4ca90ff5976434a2b6e758df38df54387ae70c1b
mapped-devices: Add 'location' and 'check' fields.
Hope that helps!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-01-08 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 3:24 Vagrant Cascadian [this message]
2018-01-08 5:46 ` bug#30021: system build: unable to parse multi-line device-mapping Mark H Weaver
2018-01-08 5:49 ` Mark H Weaver
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=87efn11190.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=30021@debbugs.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).