arm image ; daemon-socket error
after manually installing guixsd via the current guix-install.sh script on an arm--beaglebone black--i attempted to create an image using the string from Mathieu Othacehe's Porting GuixDS to ARMv7, December 22, 2017. Namely: # guix system disk-image --system=armhf-linux -e "(@ (gnu system install) beaglebone-black-installation-os)" it ended with the following: Guix System: Error: fails to connect to '/var/guix/daemon-socket/socket' no such file or directory * * * any thoughts as to why the error occured and what i need to do for it to complete without error?
Re: Maybe I made a mistake?
I'm aware that binaries packaged for Debian and derivatives like Ubuntu don't work. However, not being a coder or good with reading or writing scheme code, I'm having to work around a few of these issues. Regarding documentation, I feel as if the manual expects a certain familiarity with writing scheme code, and there isn't a lot of documentation for diagnosing little problems like there is with Debian and Ubuntu. I guess that comes down to how widespread those distros are in the GNU/Linux community. On 08.06.2019 10:12, Julien Lepiller wrote: Le 8 juin 2019 09:18:39 GMT+02:00, Ricardo Wurmus a écrit : Hi, Some simple packaged software that work on those distros like Debian don't work with Guix System […] Do you mean binaries that were packaged for Debian won’t work unchanged on Guix System? This is expected as Guix does not provide libraries and the loader at the location where a Debian binary would expect them. You would need to package the software for Guix to use it there. Packaging software is not as hard as you think it is, but if you lack the time to learn, you can still add your sohtware to that list: https://libreplanet.org/wiki/Group:Guix/Wishlist It's not guaranteed that someone will work on it, as we are all volunteers. and I also find the documentation to be really hard for the non-tech savvy like me to understand. I'm confused when I should mess with my configuration file or when to do things manually, like adding a supplementary group for my primary account. All of this should be done via the configuration file as the system is mostly stateless, i.e. when you reboot your system is essentially set up from scratch using the files that were generated when you last ran “guix system reconfigure”. I really want to like Guix, but for now I might have to switch to something easier until the documentation gets fleshed out and more packages that aren't in yet are added to avoid frustration. Can you point to specific problems you have with the documentation? -- Ricardo
PCI Sound Card SB0240 is installed but not visible in Audio Mixer
I cannot make my music card to work. The model is Creative Labs Sound Blaster Audigy 2 PCI Sound Card SB0240. It works on Debian but GuixSD. When I click Volume and Audio mixer on my Xfce Desktop, in an Output Devices tab an information is displayed: No output devices available. But the system apparently sees the card: s@s ~$ lspci |grep EMU 01:00.0 Multimedia audio controller: Creative Labs EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster Audigy Series] (rev 04) s@s ~$ sudo dmesg |grep EMU [4.416002] gameport gameport0: EMU10K1 is pci:01:00.1/gameport0, io 0xcc00, speed 874kHz s@s ~$ guix describe Generation 2Jun 09 2019 21:58:21(current) guix 597ab33 repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 597ab33d6ba19a8754da265e6b19ba6ad69d0144 s@s ~$ So how to fix it?
custom hwdb settings
Hi, I want to add a custom hwdb date to udev. I couldn't find a standard way in the documentation to do this the way for example custom udev rules are added. I'm not sure how to approach this. Fore more context, I want to achieve this: https://wiki.archlinux.org/index.php/map_scancodes_to_keycodes#Example_for_custom_hwdb
Re: package definition: unbound variable ungexp
Hi,
> can do is add an input with that code:
>
> (inputs `(("test-plugin.yaml" ,(plain-file …
>
> Then inside your build phase, simply install this input with:
>
> (install-file (assoc-ref inputs "test-plugin.yaml") regpath)
>
> Alternatively, you can write to the file directly in the phase:
>
> (with-output-to-file (string-append regpath "/test-plugin.yaml")
> (lambda _
> (format #t "…")))
>
Thanks, adding the file as an input solved the issue.
Regards,
Reza
Re: package definition: unbound variable ungexp
Le 9 juin 2019 08:26:24 GMT+02:00, Reza Alizadeh Majd a
écrit :
>Hello Guix,
>
>I want to create a plain file during package build and copy it to
>output.
>but using following definition, I receive error on during package
>installation:
>
>--- CODE:
>-
>(add-after 'install 'register-plugin
> (lambda* (#:key outputs #:allow-other-keys)
> (let* ((out (assoc-ref outputs "out"))
> (regpath (string-append out "/etc/px/accounts/plugins"))
> (plugin-data (string-append "plugin:\n"
> " name: " ,name "\n"
> " version: " ,version "\n"
> " type: python\n")))
>
>(install-file #$(plain-file "test-plugin.yaml" plugin-data) regpath
>--
>
>and error that I received during package build:
>
>--- ERROR:
>
>starting phase `register-plugin'
>Backtrace:
> 8 (primitive-load "/gnu/store/fpj6577yfiiz40ci39bw8zzycsy…")
>In ice-9/eval.scm:
> 191:35 7 (_ #f)
>In srfi/srfi-1.scm:
> 863:16 6 (every1 # …)
>In
>/gnu/store/4r04fsfcryy5h4v2h3g6lzlibafmmdjm-module-import/guix/build/gnu-build-system.scm:
> 799:28 5 (_ _)
>In ice-9/eval.scm:
>619:8 4 (_ #(#(#(#(#(#(#(#) …) …) …) …) …) …))
>159:9 3 (_ #(#(#(#(#(#(#(#) …) …) …) …) …) …))
> 182:19 2 (proc #(#(#(#(#(#(#(#) …) …) …) …) …) …))
> 142:16 1 (compile-top-call _ (7 . ungexp) ((10 (13 15 7 . #) # …)))
>In unknown file:
> 0 (%resolve-variable (7 . ungexp) #)
>
>ERROR: In procedure %resolve-variable:
>Unbound variable: ungexp
>--
>
>does any one knows which package do I have to add in order to solve
>this issue?
>
>
>Best,
>Reza
Hi,
I think the issue is that the builder doesn't use (guix gexp). And you're not
inside a gexp either, so you can't ungexp. I think what you can do is add an
input with that code:
(inputs `(("test-plugin.yaml" ,(plain-file …
Then inside your build phase, simply install this input with:
(install-file (assoc-ref inputs "test-plugin.yaml") regpath)
Alternatively, you can write to the file directly in the phase:
(with-output-to-file (string-append regpath "/test-plugin.yaml")
(lambda _
(format #t "…")))
Re: package definition: unbound variable ungexp
Hi, > I believe you are looking for (guix gexp) module. I already added `(guix gexp)` to #:use-module part of my module definition, but this problem was not fixed. Regards, Reza
Re: package definition: unbound variable ungexp
Hello, Reza Alizadeh Majd ezt írta (időpont: 2019. jún. 9., V, 8:26): > Hello Guix, > > I want to create a plain file during package build and copy it to output. > but using following definition, I receive error on during package > installation: > > --- CODE: > - > (add-after 'install 'register-plugin >(lambda* (#:key outputs #:allow-other-keys) > (let* ((out (assoc-ref outputs "out")) > (regpath (string-append out > "/etc/px/accounts/plugins")) > (plugin-data (string-append "plugin:\n" > > " name: " ,name "\n" > > " version: " ,version "\n" > > " type: python\n"))) > > (install-file #$(plain-file "test-plugin.yaml" > plugin-data) regpath > > -- > > and error that I received during package build: > > --- ERROR: > > starting phase `register-plugin' > Backtrace: >8 (primitive-load "/gnu/store/fpj6577yfiiz40ci39bw8zzycsy…") > In ice-9/eval.scm: >191:35 7 (_ #f) > In srfi/srfi-1.scm: >863:16 6 (every1 # …) > In > /gnu/store/4r04fsfcryy5h4v2h3g6lzlibafmmdjm-module-import/guix/build/gnu-build-system.scm: >799:28 5 (_ _) > In ice-9/eval.scm: > 619:8 4 (_ #(#(#(#(#(#(#(#) …) …) …) …) …) …)) > 159:9 3 (_ #(#(#(#(#(#(#(#) …) …) …) …) …) …)) >182:19 2 (proc #(#(#(#(#(#(#(#) …) …) …) …) …) …)) >142:16 1 (compile-top-call _ (7 . ungexp) ((10 (13 15 7 . #) # …))) > In unknown file: >0 (%resolve-variable (7 . ungexp) #) > > ERROR: In procedure %resolve-variable: > Unbound variable: ungexp > > -- > > does any one knows which package do I have to add in order to solve this > issue? > > > Best, > Reza > > I believe you are looking for (guix gexp) module. Best regards, g_bor -- OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
