gnu: xkeyboard-config: Upgrade to 2.41.

9ed36ee6ea9479007108e696afa389d5030c2280 Mon Sep 17 00:00:00 2001 From: "B. Wilson" Date: Fri, 31 May 2024 08:58:07 +0900 Subject: [PATCH] gnu: xkeyboard-config: Upgrade to 2.41. * gnu/packages/xorg.scm (xkeyboard-config): Upgrade to 2.41. --- gnu/packages/xorg.scm | 6 +++--- 1 file changed, 3 insertions(+), 3

Re: Help packaging ArrayFire

Adam Faiz wrote: > On 8/20/23 19:35, B. Wilson wrote: > > Hello Guix, > > > > Knee deep in CMake hell here and would appreciate a helping hand. ArrayFire > > build is defeating me: > > > > CMake Error at > > /gnu/store/ygab8v4ci9iklaykapq52bfss

Help packaging ArrayFire

e's a 2016 thread where Dennis Mungai claims to have successfully gotten ArrayFire packaged on Guix: https://issues.guix.gnu.org/23055. However, that appears to have never resulted in a patch. Thoughts? ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2023 B. Wilson ;;; ;;;

Re: Shepherd erroring on guix system reconfigure

Tobias Geerinckx-Rice wrote: > On 17 April 2022 09:27:04 UTC, Tobias Geerinckx-Rice wrote: > >There's only a warning here, not an error. > > > >Is the swap file already swapon'd? If it previously worked, the warning is > >likely (pun unintended) transient. > > > >Kind regards, > > > >T G-R > >

Shepherd erroring on guix system reconfigure

Hey Guix, After pulling about an hour ago and attempting to reconfigure, it looks like shepherd is falling over, even though the reconfigure command finishes: activating system... The following derivation will be built:

Error pulling custom channel that includes another third-party channel

Hey Guix, In my channels.scm, in addition to the primary guix channel I have my-channel and other-channel. This has worked just fine, until I added a commit in my-channel which use-modules something from other-channel. Now guix pull fails when attempting to build my-channel: (exception

Re: Do we want versioned symbols in ncurses?

Thanks for the quick turnaround. > Debian has identifier some potential problems, quoted from > : Ah, yes. The version script also sets a bunch of symbols to local scope. Good catch. Off the top of my head, the only sanity-check I can

Do we want versioned symbols in ncurses?

Hey Guix, Is there any particular reason why our current ncurses packages builds without versioned symbols? Upstream specifies only default versions (i.e. via @@), no forced ones, so IIUC that should make the library drop-in replaceable for everything we have so far. Am I missing something?