Subject: Re: [PATCH] gnu: nghttp3: Update to 1.10.1.

From: Tomas Volf <[email-masked]>
Date: Thu, 05 Jun 2025 19:14:28 +0200

Andreas Enge <[email-masked]> writes:

> QA again shows libnode as failing:
>    https://qa.guix.gnu.org/issue/78674/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
>
> I wonder if this is just some fragility in libnode; could you build it
> locally?

Hm, not sure what is going on.  Builds for me locally just fine, same as
last time.

--8<---------------cut here---------------start------------->8---
$ g show
commit 1dca4ac7d1086f0ac16ee416dac9094228b2647f (HEAD -> bug/78674/update-nghttp3)
Author: Tomas Volf <[email-masked]>
Date:   Thu Apr 17 14:33:11 2025 +0200

    gnu: nghttp3: Update to 1.10.1.
    
    * gnu/packages/web.scm (nghttp3): Update to 1.10.1.
    
    Change-Id: Ib249a3c559285931db8c43d345cdff461f5d494f

diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
index 63daa59dbf..8807b6485e 100644
--- a/gnu/packages/web.scm
+++ b/gnu/packages/web.scm
@@ -8738,7 +8738,7 @@ (define-public nghttp2
 (define-public nghttp3
   (package
     (name "nghttp3")
-    (version "1.9.0")
+    (version "1.10.1")
     (source
      (origin
        (method url-fetch)
@@ -8747,7 +8747,7 @@ (define-public nghttp3
                            "nghttp3-" version ".tar.gz"))
        (sha256
         (base32
-         "1gai6j4nlp79gf9p8qsid27s9qjz6irf0pqykr1qhizsbngaviyv"))))
+         "18lik57yb3zc5g17s18ymd268p037wly0hgvw6n9h48l09jqqv68"))))
     (build-system gnu-build-system)
     (native-inputs
      (list pkg-config))
$ guix shell -CWD guix -- ./pre-inst-env guix build -P1 nghttp3
guix build: computing dependents of package [email-masked]...
/gnu/store/sd888ijdb3yglav83j3srpdls6vi3wkl-nghttp3-1.10.1
/gnu/store/v1bkcxn6cj86r8vm80daxmv6n4jhp75x-node-22.14.0
/gnu/store/bqb6rkxqvzvd3h8kqwwsqgvds5jydrd8-libnode-22.14.0
$ guix shell -CWD guix -- ./pre-inst-env guix build libnode
/gnu/store/bqb6rkxqvzvd3h8kqwwsqgvds5jydrd8-libnode-22.14.0
--8<---------------cut here---------------end--------------->8---

But yeah, I see it is failing in the CI...  Did we hear anything back
from node team last time?

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.