Andy Tai writes:
> Hi, I wonder if I have multiple Guix channels, and the same package is
> defined in multiple channels, of different versions, what would happen
> if I do guix pull? Would the first package definition encountered in
> the first channel containing the definition of this
Andy Tai writes:
> Hi, thanks. What if it is the case of the same package, same version, but
> say j\ust differs in configure, compile or link flags (from
> multiple definitions)?
The convention I’ve seen is to define such package variants under different
names, e.g emacs and emacs-xwidgets.
Dear all,
Even though a substitute is available [1], one of my Guix system does
not want to use this:
[kodi@watson ~]$ guix package -u kodi
The following packages will be upgraded:
kodi (dependencies or package changed)
kodi-cli (dependencies or package changed)
substitute: updating
On Tue, Feb 13, 2024 at 11:31:28AM +0100, Ludovic Courtès wrote:
> Hello Guix!
>
> Has anyone succeeded in building a Docker image suitable for use in
> GitLab-CI? I haven’t. Here’s what I tried.
In the past I used a script to install guix using the shell script and
then ran guix pull before
On 2024-02-14, 10:47 +0300, Oleg Pykhalov wrote:
> Libvirt has been working perfectly for me on my Guix System for years!
Hey Oleg,
Thanks for getting back to me and sharing your experience. It really
helps.
Yeah, libvirt seems like the best option, I think I'll go for it.
Thanks, best
Am Tue, Feb 13, 2024 at 11:31:28AM +0100 schrieb Ludovic Courtès:
> Has anyone succeeded in building a Docker image suitable for use in
> GitLab-CI? I haven’t. Here’s what I tried.
A colleague of mine just found this:
https://gitlab.com/daym/guix-on-docker/
:-)
Andreas
Ludovic Courtès writes:
> Initially, I built an image with ‘guix system image -t docker …’ but
> that doesn’t work because then the image’s “entry point” is shepherd,
> but shepherd never returns.
Did you try resetting the entrypoint in .gitlab-ci.yml using the
image:entrypoint keyword? [1]
