#79431 [PATCH] gnu: ngtcp2: Update to 1.15.1.

Message #5 received at submit@debbugs.gnu.org (full text, mbox, reply):

From: Tomas Volf <~@wolfsden.cz>

To: guix-patches@gnu.org

Cc: Tomas Volf <~@wolfsden.cz>

Subject: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Thu, 11 Sep 2025 01:26:33 +0200

* gnu/packages/networking.scm (ngtcp2): Update to 1.15.1.

Change-Id: I793d98dfa2d5a140d342a279eda390d73fbe7c34
---
 gnu/packages/networking.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index ee938b4cb0..36bfc8bd40 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -4749,7 +4749,7 @@ (define-public nbd
 (define-public ngtcp2
   (package
     (name "ngtcp2")
-    (version "1.13.0")
+    (version "1.15.1")
     (source
      (origin
        (method url-fetch)
@@ -4757,7 +4757,7 @@ (define-public ngtcp2
                            "releases/download/v" version "/"
                            "ngtcp2-" version ".tar.gz"))
        (sha256
-        (base32 "1sik0rlpar1dk46ahssv59ik1w360v97hydzari77m8khfjscxd1"))))
+        (base32 "1r3128v6fwn1p7py57frp4ij251z4rv4mfxknhjwylw9i3gr947r"))))
     (build-system gnu-build-system)
     (arguments
      (list
-- 
2.50.1

Message #8 received at 79431@debbugs.gnu.org (full text, mbox, reply):

From: Andreas Enge <andreas@enge.fr>

To: Tomas Volf <~@wolfsden.cz>

Cc: 79431@debbugs.gnu.org

Subject: Re: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Sat, 20 Sep 2025 16:49:30 +0200

This has too many dependents to be applied directly, unfortunately.

Andreas

Message #11 received at 79431@debbugs.gnu.org (full text, mbox, reply):

From: Tomas Volf <~@wolfsden.cz>

To: Andreas Enge <andreas@enge.fr>

Cc: 79431@debbugs.gnu.org

Subject: Re: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Sun, 21 Sep 2025 21:01:15 +0200

Andreas Enge <andreas@enge.fr> writes:

> This has too many dependents to be applied directly, unfortunately.

True ^_^

In the past I was able to send the email with --subject-prefix='PATCH
core-updates' in cases like this, but that branch is now gone with
seemingly no direct replacement.  When I am aware about the excessive
number of dependents, what branch should I mark as target for the patch
in question?  The documentation does not seem to provide a guidance on
this (or I cannot find it).

Tomas

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

Message #14 received at 79431@debbugs.gnu.org (full text, mbox, reply):

From: Andreas Enge <andreas@enge.fr>

To: Tomas Volf <~@wolfsden.cz>

Cc: 79431@debbugs.gnu.org

Subject: Re: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Mon, 22 Sep 2025 10:11:11 +0200

Am Sun, Sep 21, 2025 at 09:01:15PM +0200 schrieb Tomas Volf:
> In the past I was able to send the email with --subject-prefix='PATCH
> core-updates' in cases like this, but that branch is now gone with
> seemingly no direct replacement.

The branch has gone quite some time ago; so in the end adding "core-updates"
to the subject line was more of a social signal to committers not to push
the commit to master.

> When I am aware about the excessive
> number of dependents, what branch should I mark as target for the patch
> in question?  The documentation does not seem to provide a guidance on
> this (or I cannot find it).

Unfortunately this is a hole in our procedures; it depends on someone
picking it up in the context of larger changes.

Andreas

Message #17 received at 79431@debbugs.gnu.org (full text, mbox, reply):

From: Tomas Volf <~@wolfsden.cz>

To: Andreas Enge <andreas@enge.fr>

Cc: 79431@debbugs.gnu.org

Subject: Re: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Mon, 22 Sep 2025 23:02:44 +0200

Andreas Enge <andreas@enge.fr> writes:

>> When I am aware about the excessive
>> number of dependents, what branch should I mark as target for the patch
>> in question?  The documentation does not seem to provide a guidance on
>> this (or I cannot find it).
>
> Unfortunately this is a hole in our procedures; it depends on someone
> picking it up in the context of larger changes.

I see, thank you for the information.  For the time being I will stop
sending patches for packages with lot of dependents, to save you some
time. ^_^  It will save me time as well, -P1 takes a while on ngtcp2.

Tomas

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

Message #22 received at 79431-done@debbugs.gnu.org (full text, mbox, reply):

From: Andreas Enge <andreas@enge.fr>

To: Tomas Volf <~@wolfsden.cz>

Cc: 79431-done@debbugs.gnu.org

Subject: Re: [PATCH] gnu: ngtcp2: Update to 1.15.1.

Date: Wed, 24 Sep 2025 12:17:23 +0200

Am Mon, Sep 22, 2025 at 11:02:44PM +0200 schrieb Tomas Volf:
> I see, thank you for the information.  For the time being I will stop
> sending patches for packages with lot of dependents, to save you some
> time. ^_^  It will save me time as well, -P1 takes a while on ngtcp2.

Well, if you add that you have built all the -P1 already, that would be
a useful information, and maybe enough to merge a package with moderately
many dependents.

For this package, it turns out there is also a pull request on codeberg:
   https://codeberg.org/guix/guix/pulls/1920
so I will close it here.

Andreas

Send a report that this bug log contains spam.