GNU bug report logs - #67570
[PATCH] gnu: kubo: Fix build.

Previous Next

Package: guix-patches;

Reported by: "Artyom V. Poptsov" <poptsov.artyom <at> gmail.com>

Date: Fri, 1 Dec 2023 19:10:01 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: "Artyom V. Poptsov" <poptsov.artyom <at> gmail.com>
Cc: 67570 <at> debbugs.gnu.org
Subject: [bug#67570] [PATCH] gnu: kubo: Fix build.
Date: Sat, 02 Dec 2023 11:04:56 +0100
Hi,

I spoke too fast…

"Artyom V. Poptsov" <poptsov.artyom <at> gmail.com> skribis:

> +     (let ((p (package-input-rewriting
> +               `((,go-golang-org-x-sys . ,go-golang-org-x-sys-0.8))
> +               #:deep? #true)))
> +       (cons go-golang-org-x-sys-0.8
> +             (map p
> +                  (list go-github-com-alecthomas-units
> +                        ;; TODO: needs to be updated first
> +                        ;; go-github-com-blang-semver
> +                        go-github-com-cespare-xxhash

It does fix the build, but it’s a bit heavy-handed: every time we
compute the kubo derivation, we go through that graph rewriting, which
is quite expensive.

Can you think of another way this could be fixed?  What if we don’t
replace go-golang-org-x-sys everywhere?  Or perhaps there’s a trick that
would allow us to build with go-golang-org-x-sys 0.4?

In parallel perhaps we should work on upgrading go-golang-org-x-sys
altogether?

WDYT?

Ludo’.




This bug report was last modified 1 year and 193 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.