On 3/20/24 14:53, David Elsing wrote:
> I meant to reply to this issue, but accidentally opened a new issue with
> the patch fixing it:
> https://issues.guix.gnu.org/69923
> Should we close this one (69922)?
That's OK, since you have a patch sending it to the patches mailing list made
sense (thi
Hello,
> While reviewing https://issues.guix.gnu.org/69866, I noticed that
> arcan-sdl is failing. I'm recording some notes from looking at the CI
> pages here.
I meant to reply to this issue, but accidentally opened a new issue with
the patch fixing it: https://issues.guix.gnu.org/69923
Should
Hello,
While reviewing https://issues.guix.gnu.org/69866, I noticed that
arcan-sdl is failing. I'm recording some notes from looking at the CI
pages here.
The package started failing in March of 2023
(https://ci.guix.gnu.org/search?query=arcan-sdl%20spec:master&border-high-id=635295).
Around
Christopher Baines skribis:
> I believe I sorted access for Ludo, but nothing was found when looking
> at the logs.
I’m closing it. Let’s reopen if we stumble upon a similar issue.
Ludo’.
Hi Einar,
Einar Largenius skribis:
> I am setting up shepherd for use by my user account on a foreign distro. I
> setup as described in the manual in the section "(shepherd) Managing User
> Services". When I try to run it using shepherd, it crashes on the line:
>
> ;; Send shepherd into t
Hi,
Attila Lendvai skribis:
> this log file is with my shepherd branch, i.e. it contains much more log.
Could you check whether it happens with current ‘main’?
The test is quite sensitive to anything that would open file
descriptors, as you can imagine.
Thanks,
Ludo’.
Hi Richard and all,
Richard Sent skribis:
> However, when fish is in charge of executing on-first-login, stdout and
> stderr for the user shepherd get directed to a pipe instead of
> /dev/null.
>
> fish fds, both stdout and stderr point to a pipe:
>
> $ ls -l /proc//fd)
> lr-x-- 1 richar
Possibly related to bug#69753.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
I've encountered this issue myself, so it's not an isolated incident. I
observed that it only occured when building packages from a custom
channel (or perhaps with -L, I don't recall for sure.)
The issue seemed to disappear after a while.
--
Take it easy,
Richard Sent
Making my computer weirder
Hi Roman,
Sorry for the delay.
Roman Frołow skribis:
> guix system image --system=aarch64-linux --image-type=uncompressed-iso9660
> /gnu/store/dgiaqzxx743na0fd88a0mzj7f8jmcj5n-guix-29c94dd52-modules/share/guile/site/3.0/gnu/system/install.scm
[...]
> I was able to install guix.
>
> After rest
Using the following:
(use-modules (gnu packages)
(gnu packages cross-base)
(gnu packages gcc)
(guix packages))
(packages->manifest
(append
(list
(cross-gcc-toolchain "x86_64-w64-mingw32"
#:base-gcc gcc-13)
)))
and guix build -m win.scm:
gcc-13.2.0/g
11 matches
Mail list logo
