--- Begin Message ---
Subject: |
guix system init broken on non GuixSD |
Date: |
Fri, 9 Mar 2018 18:35:30 +0100 |
User-agent: |
NeoMutt/20170912 (1.9.0) |
`guix system init` seems to be broken for non GuixSD distirbutions:
When I tried it on openSUSE:
# guix system --no-bootloader init /Devel/git/guix-config/config.scm /mnt/mnt/
;;; note: source file /Devel/extra/gnu/packages/connman.scm
;;; newer than compiled /root/.config/guix/latest/gnu/packages/connman.go
;;; note: source file /Devel/extra/gnu/packages/connman.scm
;;; newer than compiled
/usr/lib64/guile/2.2/site-ccache/gnu/packages/connman.go
;;; note: source file /Devel/extra/gnu/packages/connman.scm
;;; newer than compiled
/usr/lib64/guile/2.2/site-ccache/gnu/packages/connman.go
guix system: error: open-file: No such file or directory:
"/run/booted-system/kernel/lib/modules/4.15.6-1-default/modules.alias"
4.15.6-1-default is version of my running kernel, but not defined as package -
it is not expected to be used for guix call.
/run/booted-system/ is specific for GuixSD.
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#30760: guix system init broken on non GuixSD |
Date: |
Sat, 10 Mar 2018 00:19:52 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Danny Milosavljevic <address@hidden> skribis:
> [huge build]
>> The current tradeoff is to make that diagnostic based on the running
>> kernel, even if it’s an approximation.
>
> Ah, good point.
>
>> If that’s fine with you I’d like to fix this bug with the conservative
>> patch below.
>
> Sure, looks good.
Pushed as 8d5c14edf5a6d01f859b1aa00c836ffdb5ddecf4.
> While we are approximating we could also in a later version fall back to
> (the host system's) "`cat /proc/sys/kernel/modprobe` --showconfig" - it
> could be used to find aliases.
>
> But maybe that would make it brittle. Hmm...
Yeah, I don’t think it’d make a big difference.
BTW, we should add a ‘--skip-checks’ option to ‘guix system’ so that
users can skip those checks. That’d provide an escape hatch in case
‘check-device-initrd-modules’ makes the wrong diagnostic.
Thoughts?
Ludo’.
--- End Message ---