On 2026-05-12, Vagrant Cascadian wrote: > On 2026-05-13, Nguyễn Gia Phong via "Development of GNU Guix and the GNU > System distribution." wrote: >> On 2026-04-09 at 00:07+09:00, Nguyễn Gia Phong wrote: >>> This branch is for queuing world rebuild changes >>> not under the scope of any existing team (or under too many). ... >> If you have been holding off any package update because it has >> many dependents but has not been adopted by any team, doing that >> in the next week or two might be a good idea. > > I think ncurses-with-tinfo could be merged into regular ncurses with > very low risks... which would trigger over 9000 rebuilds... originally > introduced ncurses-with-tinfo around 2022 or so as some packages needed > the tinfo parts and did not want to trigger a world rebuild at the > time... and here we are, 4 years later. :) > > Should I submit a pull request for this against the misc-world-rebuild > branch? > > It sort of makes sense at the same time, but possibly higher risk, to > actually update ncurses... from 6.2.x (~2021) to 6.6.x (2025)?
Submitted ncurses/tinfo (a.k.a. "ncurses-with-tinfo") merge into ncurses, and ncurses update to 6.6 as: https://codeberg.org/guix/guix/pulls/8662 There are numerous patches that need applying to get up to the currently published patchsets for ncurses up to 6.6.20260509: https://invisible-mirror.net/archives/ncurses/6.6/ Help figuring out a clean way to import all those patches would be appreciated, as they need to be applied in sequence.
signature.asc
Description: PGP signature
