Hi,
when system guix produced by the guix-for-channels procedure is
installed, modules in any channel (except in the 'guix) will shadow the
same modules acquired via `guix pull'.
Steps to reproduce:
Have a channels.scm:
--8<---cut here---start->8---
(cons (c
On Sun, 17 Nov 2024 15:16:13 +0800,
Efraim Flashner wrote:
>
> [1 ]
> On Fri, Nov 15, 2024 at 10:30:40PM +0800, Hilton Chain wrote:
> > On Fri, 15 Nov 2024 11:29:10 +0800,
> > Hilton Chain wrote:
> > >
> > > Good news: Thanks to this diff, I know how to add libc to RUNPATH now :)
> > >
> > > Anot
Hi,
Ludovic Courtès writes:
> Hi,
>
> Raphael Gosselin skribis:
>
>> Guix: 1.1.0
>> Guile: 3.0.4
>> Guile-Gcrypt: 0.3.0
>> GnuTLS: 3.6.12
>> Guile-SQLite3: 0.1.3
>> Guile-Git: 0.3.0
>> Guile-JSON: 4.3.2
>> zlib: 1.2.11
>> Make: 4.3
>> Guile-SSH: 0.13.1
>> libgcrypt: 1.8.5
>> sqlite3: 3.31.1
>>
Hi,
Leo Famulari skribis:
> I bisected the package build failure. It began with "gnu: mesa: Update
> to 24.2.2."
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=e00c621cbbf58a54ca2dd0c7075f154af26bcd54
Interesting. The path to Mesa is:
--8<---cut here---start
Simon Tournier writes:
>> For --save-provenance, is your proposal that in addition to saving the
>> additional manifests, the commandline that was used would also be saved?
>
> We could save the command line too using another file. :-)
That would be helpful :)
Given an image generated with --sa
This error shows up for `guix system image
$GUIX_SRC/gnu/system/examples/bare-bones.tmpl` (or any guix system invocation
I've tried) as well. Downgrading to the revision before the commit mentioned as
the cause is a workaround.
TLDR: relevant kernel configs are CONFIG_SYSFB_SIMPLEFB (only on x86?),
CONFIG_DRM_SIMPLEDRM, at the same time it's necessary to disable
CONFIG_FB_EFI and CONFIG_FB_SIMPLE
Hi,
I run Guix System, after upgrading from 1.4 to snapshot gdm refuses to
start even if I disable wayland in its config,
Hello,
I've been using 'mumi send-email', and one annoyance is that it doesn't
seem to reliably (or at all?) detect the created issue in the tracker,
even after the issue was synced to the MUMI database and visible through
the web interface.
For example, the issue https://issues.guix.gnu.org/7439
Hello,
Leo Famulari writes:
> On Thu, Feb 25, 2021 at 02:51:29PM +, Sanne Wouda wrote:
>> I'm seeing two failures when running the guix test suite on HEAD
>> (c1da9829f8b6)
>>
>> publish.scm "with cache" fails on line 456:
>>
>> (= #o644 (stat:perms (lstat nar)))
>>
>> which seems to be
