From 386580ccf0127c3fbb24ea4da0bf5703ed493764 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 15 May 2026 22:50:48 -0700 Subject: gnu: ncurses: Update to 6.6.20251230. FIXME: When the core-packages-team branch is rebased this should be squashed into: 2b78cc77a6a1e1cd4e5c7c9034b64f8d7e76e98e gnu: ncurses: Update to 6.6.20260103. 2b78cc77 included a the patch date in the revision without applying the corresponding patches... 6.6 with no patches applied could be versioned 6.6.20251230 (as it is effectively the same as 6.5 with the 20251230 patch applied ... or we could just call it 6.6.0 because the version functions to download the upstream version assume a third digit and effectively throw it out ... which we could not do only to change it back again for the next patch update ... yes, it is confusing... are you still following all this? :) * gnu/packages/ncurses.scm (ncurses): Update to 6.6.20251230. --- gnu/packages/ncurses.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gnu/packages/ncurses.scm b/gnu/packages/ncurses.scm index efeb6272ee8..2ece203f150 100644 --- a/gnu/packages/ncurses.scm +++ b/gnu/packages/ncurses.scm @@ -45,7 +45,7 @@ (define-public ncurses (package (name "ncurses") - (version "6.6.20260103") + (version "6.6.20251230") (source (origin (method url-fetch) (uri (string-append "mirror://gnu/ncurses/ncurses-" -- cgit v1.2.3