On second (or third...maybe fourth?) thought I have re-read the documentation
for guix gc and it does state:
> Running guix gc with no arguments will collect
> as much garbage as it can, but that is often
> inconvenient: you may find yourself having to
> rebuild or re-download software that is “d
I tried using the procedures text-file* and plain-file but I can't manage to
make it works.
Im trying to define a package that will be used to add files to cups, in the
same ways taht the package brlaser add files. But no luck, every time I try to
create a `plain-file` the build fails.
Help a
"(" writes:
> I don't experience this issue personally, and I use `guix home` for all
> my packages. Very strange.
>
> -- (
Thanks for helping confirm that I may have some sort of problem here. At
the risk of admitting that I depend on non-gnu stuff in order to make my
machine work, here's h
I don't experience this issue personally, and I use `guix home` for all
my packages. Very strange.
-- (
Hey There,
I am not sure if I have some sort of bug, or if this is how guix home is
intended to work. The short problem that I am having is that every time
I do a guix gc, the next time I feel the need to do a guix home
reconfigure for some petty change such as an environment variable, guix
feels
Hi,
On Mon, 27 Jun 2022 at 16:51, Emmanuel Medernach
wrote:
> Thanks, here is the resulting manifest:
>
> (specifications->manifest
> (list "gsl"
> "pcre"
> "icu4c"
> "zlib"
> "cmake"
> "make"
> "gcc-toolchain@4.9"
> "glibc"))
>
Le 27/06/2022 à 16:42, Julien Lepiller a écrit :
It's possible your packages on machine A are from various guix
revisions, if you didn't run "guix update" or didn't use a manifest to
install them.
Yes you are right, that is certainly the case
Eg you run "guix install glibc" at revision A,
Le 27/06/2022 à 16:32, zimoun a écrit :
I guess “guix describe” on ’Machine B’ is not the state specified by
’Machine A’. From my understanding, the easiest workflow is:
machine-A$ guix describe -f channels > state-A.scm
machine-A$ guix package --export-manifest > pkgs-A.scm
exchange these 2
It's possible your packages on machine A are from various guix revisions, if
you didn't run "guix update" or didn't use a manifest to install them.
Eg you run "guix install glibc" at revision A, pull revision B where glibc was
updated to 2.34. When you list your packages, it still mentions glibc
Hi,
On Mon, 27 Jun 2022 at 15:49, Emmanuel Medernach
wrote:
> [Machine A]$ guix package --list-installed | sort | awk '//{ print $1
> "@" $2; }'
> cmake@3.19.2
> gcc-toolchain@4.9.4
> glibc@2.33
> gsl@2.6
> icu4c@68.2
> make@4.3
> pcre@8.44
> zlib@1.2.11
Instead, it seems easier to run:
Hello,
We are trying to replicate guix packages list on another machine. We are
using GUIX on a foreign distro.
Here what we have on machine A:
[Machine A]$ guix describe --format=channels
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git";)
(
11 matches
Mail list logo
