Hi Marius,
Marius Bakke skribis:
> I have included a system configuration that works fine on 'master' but
> not on 'core-updates'. It consistently fails to `guix system build`
> across multiple machines, including "berlin".
Oh I see. This is fixed by cherry-picking
96783ed6275cd2818ff56916274
Christopher Howard writes:
> Thank you. It is now building fine for me.
I'm glad I could help. I'm closing this bug now.
Regards,
Diego
Jan Nieuwenhuizen writes:
> Jan Nieuwenhuizen writes:
>
>> Bengt Richter writes:
>>> I tried
>>> guix build bootstrap-tarballs
>>
>> Yes, sadly that's not supported on current master. It should work on
>> core-updates. So I tried that and found it fails in similar ways.
>
> The attached patc
Marius Bakke writes:
> Jan Nieuwenhuizen writes:
>> I stumbled upon this while working to fix #37549. Where should this
>> patch land?
>
> This patch should be safe for 'core-updates'. Please double check that
> it does not rebuild the world, though. :-)
I was hesitating and re-checked on a f
I went looking for the pid to answer Ludo's question and didn't find strace,
and the ssh command line was wrong so I got suspicious.
After searching a bit, I found the problem: I'm an idiot. 'make' apparently
did not succeed after all and I simply failed to catch it. I went back and
re-execut
On Sun, 29 Sep 2019 14:27:59 +0200
Wiktor Żelazny wrote:
> The last thing that comes to my mind is the line:
>
>(use-service-modules desktop xorg)
>
> Have you got these in your config.scm?
>
> WŻ
Yes I have. I wouldn't be able to run Mate DE, if I didn't have
these two.
Jan Wielkiewicz
On Sat, Sep 28, 2019 at 01:22:27PM +0200, Jan Wielkiewicz wrote:
> set-xorg-configuration doesn't work with slim though, would be nice
> if someone fixed it and the fact (keyboard-layout (keyboard-layout
> "pl,cz" "legacy,ucw")) works on your machine, but not on mine is
> strange.
The last thing
Jan Nieuwenhuizen writes:
> Running
>
> ./pre-inst-env guix build --target=i686-unknown-linux-gnu hello
>
> on core-updates (and similarly on core-updates-next) fails with
>
> --8<---cut here---start->8---
> checking for i686-unknown-linux-gnu-gcc...
> /tm
RAUL H C LOPES writes:
> Hi Marius,
>
> I've managed to install GuixSD by chossing msdos instead of gpt.
> Coincidence? Is the gpt setup tested?
Can you share the steps required to reproduce the error?
> I've running the system for a few days.
>
> I need now a good manual> I'm suffering for:
Ludovic Courtès writes:
> Hi Marius!
>
> Marius Bakke skribis:
>
>> Here is a manifest that reproduces this failure:
>>
>> (use-modules (guix channels)
>> (guix inferior)
>> (srfi srfi-1))
>>
>> (define channels
>> (list (channel
>> (name 'guix)
>> (
Jan Nieuwenhuizen writes:
> Bengt Richter writes:
>> I tried
>> guix build bootstrap-tarballs
>
> Yes, sadly that's not supported on current master. It should work on
> core-updates. So I tried that and found it fails in similar ways.
The attached patches resurrect the creation of bootstrap
Running
./pre-inst-env guix build --target=i686-unknown-linux-gnu hello
on core-updates (and similarly on core-updates-next) fails with
--8<---cut here---start->8---
checking for i686-unknown-linux-gnu-gcc...
/tmp/guix-build-gcc-cross-sans-libc-i686-unkno
Bengt Richter writes:
> I tried
> guix build bootstrap-tarballs
Yes, sadly that's not supported on current master. It should work on
core-updates. So I tried that and found it fails in similar ways.
> ERROR: In procedure lstat:
> In procedure lstat: No such file or directory:
> "/gnu/stor
Regarding openconnect, no workarounds are necessary anymore for me on
core-updates, which uses a more recent network-manager@1.14.4 and will
soon be on Guix master.
Regards,
Florian
I tried
guix build bootstrap-tarballs
and it seems to have worked the whole way until then end,
(though I thought I saw warnings about exit and abort being undefined)
leaving the following on the screen:
8<--->8
PASS: lib/tests/scaffold/
15 matches
Mail list logo
