On 2/18/24 15:23, Carlo Zancanaro wrote:
> I'm not sure if this is considered a bug or not, but the solution to
> your problem is to use --check. Using your test file running:
>
>guix build -f test.scm --check
>
> should run the build one time, and compare the output with what is in
> the
Hello,
Checking a package for reproducibility is one important part of patch
review. Based on the documentation for the `--rounds=N`, I expect that a
line such as `guix build foo --rounds=2` will build the package at least
once and at most twice (assuming that, if the output is already present
On 2/6/24 05:39, Steve George wrote:
> I agreed to organise some 'patch review' online sessions in the next couple of
> weeks.
>
> Organising a basic process is a good topic for that online session. For
> example, elsewhere in the thread someone mentions some tags we could use
> consistently so
On 12/30/23 04:45, Ben Weinstein-Raun wrote:
> Does anyone know why this would happen, or how to fix it? I'm using the
> elogind service on top of %base-services.
>
I was hoping that someone else more knowledgeable might have a better
solution, but since nobody has replied I'll share the
On 7/4/23 12:26, danclm--- via wrote:
> Hello everyone!
>
> My T420 with Guix (no DE, only SDDM + Elogind + Sway) hangs during shutdown
> after running loginctl poweroff/reboot or /sbin/shutdown /sbin/reboot. It
> just sits there and only resolution is hard poweroff. It happens often.
In case
> ==
>
>The reason is that I'm currently using `guix home reconfigure' and
>even though I use the `-L' flag, `guix home' gives higher priority to
>`emacs-subed', so the build process fails and `guix home' can't exit
>successfully due to that
Hi Rodrigo! In a topic adjacent to your second question, I wanted to share
something that I recently learned about using local-file in package
definitions.
I ran through a similar exercise when building a package that largely
consisted
of local file, and came upon a similar solution of adding
I believe I understand what is happening now, and it is the result of the
way guix releases software and not a bug in my configuration. I put all of
the packages in my system configuration into a manifest and ran `guix weather`
against it, and it said that only 85% of packages have substitutes
