GNU bug report logs -
#78672
[PATCH] gnu: ngtcp2: Update to 1.13.0.
Previous Next
Reported by: Tomas Volf <~@wolfsden.cz>
Date: Mon, 2 Jun 2025 17:50:02 UTC
Severity: normal
Tags: patch
Done: Andreas Enge <andreas <at> enge.fr>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sat, 14 Jun 2025 15:27:32 +0200
with message-id <aE14xEirj67AeB9u <at> jurong>
and subject line Re: [PATCH] gnu: ngtcp2: Update to 1.13.0.
has caused the debbugs.gnu.org bug report #78672,
regarding [PATCH] gnu: ngtcp2: Update to 1.13.0.
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
78672: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78672
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
* gnu/packages/networking.scm (ngtcp2): Update to 1.13.0.
Change-Id: Ie83ea3dc6920c80b246cffd7678d53dbaba5f228
---
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 e2d8f271b7..27c7d8ae8f 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -4691,7 +4691,7 @@ (define-public nbd
(define-public ngtcp2
(package
(name "ngtcp2")
- (version "1.12.0")
+ (version "1.13.0")
(source
(origin
(method url-fetch)
@@ -4699,7 +4699,7 @@ (define-public ngtcp2
"releases/download/v" version "/"
"ngtcp2-" version ".tar.gz"))
(sha256
- (base32 "047glkg71rikj7s46jb9aaipqn13arzz0pvph5kg66f0pz4zb2n0"))))
+ (base32 "1sik0rlpar1dk46ahssv59ik1w360v97hydzari77m8khfjscxd1"))))
(build-system gnu-build-system)
(arguments
(list
--
2.49.0
[Message part 3 (message/rfc822, inline)]
Am Fri, Jun 13, 2025 at 10:06:05PM +0200 schrieb Tomas Volf:
> Andreas Enge <andreas <at> enge.fr> writes:
> > the update breaks vlang:
> Well, as usual, builds for me:
Ah, I see, it also does for me (after spending ages building node);
so I have just pushed; if these are random failures, I do not think the
situation will be worse after that.
> Maybe I should just stop touching these two libraries unless necessary.
> It seems I have picked somewhat fragile part of Guix to send patches
> for. :/
Ah, your choice! :-) But what can we do, we also need to update brittle
software shipped with Guix.
Andreas
This bug report was last modified 68 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.