From: Jesse Gibbons <jgibbons2357@gmail.com>
To: 37226@debbugs.gnu.org
Subject: bug#37226: previously working system config fails to build
Date: Fri, 30 Aug 2019 09:03:35 -0600 [thread overview]
Message-ID: <dd771dbe2ab2db4042d58d3eb891ad92c779175a.camel@gmail.com> (raw)
In-Reply-To: <3d0e93327a53916b6945fbb2df1e22121f97ad93.camel@gmail.com>
On Thu, 2019-08-29 at 21:32 -0600, Jesse Gibbons wrote:
> I try to run guix system reconfigure and get this error:
>
> guix system: error: #<<uuid> type: dce bv: #vu8(51 12 55 214 249 221
> 79
> 112 186 51 233 64 103 99 34 57)>: invalid G-expression input
>
>
> Here's the minimum of what I feed it to replicate the error (comments
> and non-essentials removed):
>
> (use-modules (gnu) (gnu system nss))
> (use-service-modules desktop pm virtualization networking cups sound)
> (use-package-modules certs gnome guile-xyz)
>
> (define pureos-root "330c37d6-f9dd-4f70-ba33-e94067632239")
> (define swap-uuid "049a0350-bcce-4920-9816-5fd4ee3c0de1")
>
> (define (other-partition entry-label vmlinuz-version root-uuid
> resume-
> uuid)
> (menu-entry
> (label "pureos")
> (linux (string-concatenate `("/boot/vmlinuz-" ,vmlinuz-version)))
> (linux-arguments
> `(,(string-concatenate `("root=UUID=" ,root-uuid))
> "ro" "quiet" "splash"
> ,(string-concatenate `("resume=UUID=" ,resume-uuid))))
> (initrd (string-concatenate `("/boot/initrd.img-" ,vmlinuz-
> version)))
> (device (uuid root-uuid))))
>
>
> (operating-system
> (host-name "piranhaplant")
> (timezone "America/Boise")
> (locale "en_US.utf8")
> (bootloader (bootloader-configuration
> (bootloader grub-bootloader)
> (target "/dev/sda") ;include my usual OS
> (menu-entries
> (list
> (other-partition
> "pureos"
> "4.19.0-2-amd64"
> pureos-root
> swap-uuid)))))
>
> (file-systems (cons (file-system
> (device (file-system-label "my-root"))
> (mount-point "/")
> (type "ext4"))
> %base-file-systems))
>
> )
>
> ====================
> Please forgive the ugly formatting and quasiquote/unquote abuse. I
> was
> beginning to understand scheme when I wrote the .
>
> It breaks when I add (file-system ...) which is identical to what's
> in
> the manual. I think it might have something to do with the
> bootloader,
> but I don't know what. Where is a G-expression expected?
The menu entry with the other partition is the problem. I'm not sure
what to do to keep the pureos partition, so I will comment it out.
Specifically, I think it's the (device) field of <menu-entry> which
took a uuid as specified in the manual.
Ludo, you wanted to know if anything is out of place when you closed
bug#36876 "guix system delete-generations removes custom boot menu
entries". I think this might be related. Is there anything that might
not be documented that needs to happen differently to add a menu item
to grub?
--
-Jesse
prev parent reply other threads:[~2019-08-30 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 3:32 bug#37226: previously working system config fails to build Jesse Gibbons
2019-08-30 15:03 ` Jesse Gibbons [this message]
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=dd771dbe2ab2db4042d58d3eb891ad92c779175a.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=37226@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).