guix_mirror_bot pushed a commit to branch core-packages-team in repository guix.
commit 38740c07971a6d9a63765f9f66c6adec39280d5e Author: Vagrant Cascadian <[email protected]> AuthorDate: Fri May 15 22:50:48 2026 -0700 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 efeb6272ee..2ece203f15 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-"
