Not sure if this is the best place to ask. Apologies in advance. Will this update include core-packages-team branch? I am waiting for https://codeberg.org/guix/guix/commit/79d1d3d58209cfb3e7d690e92ff54efab7ca0a62 reaching master.
Many thanks! On Wed, May 13, 2026 at 11:24 AM Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution. <[email protected]> wrote: > > Hi, > > On 2026-05-12 at 23:52-07:00, Vagrant Cascadian wrote: > > Should I submit a pull request for this > > against the misc-world-rebuild branch? > > On 2026-05-13 at 10:55+00:00, Ashish SHUKLA wrote: > > I just rebased my submission [...] > > to be based off misc-world-rebuild branch, instead of master. > > On 2026-05-13 at 09:24+02:00, Hugo Buddelmeijer wrote: > > I'll rebase it if you want to include it. > > Let's use master as the base since misc-world-rebuild > changes (guix build utils) and nothing can be built there > locally (within a couple hours). > > On 2026-05-12 at 23:52-07:00, Vagrant Cascadian wrote: > > 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. :) > > > > 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)? > > > On 2026-05-12 at 23:52-07:00, Vagrant Cascadian wrote: > > On 2026-05-13, Nguyễn Gia Phong wrote: > > > My call for help still stand as well, please let me know > > > if you want to join the effort. > > > > Admittedly intimidated at guiding such a large rebuild, but could maybe > > help a bit! > > Thanks, and I think it's a good idea to both merge the with-info variant > and update ncurses, in separate commits so the latter could be drop > in case we can't figure out how to fix some dependent(s). > > On 2026-05-13 at 09:24+02:00, Hugo Buddelmeijer wrote: > > I've this change to valgrind: https://codeberg.org/guix/guix/pulls/5860 > > > > It was intended as just a fix to the shebangs of valgrind, but it turned > > out that this leads to a 1000+ package rebuilt. We therefore also > > ensured that "valgrind/pinned" is properly used everywhere so that > > future changes to valgrind itself can be done more easily. > > If team C++ is not doing a team branch in the foreseeable future, > let's do it here. Could you ping them on that PR with a reference > to this Debbugs issue <https://issues.guix.gnu.org/80782>? > > BTW Valgrind 3.27 is out now! > > On 2026-05-13 at 10:55+00:00, Ashish SHUKLA wrote: > > kmod update[0] (kernel-team's domain) [has] tonnes of dependents. > > > > [0] https://codeberg.org/guix/guix/pulls/8468 > > Thanks! It is beyond my capability to review that patch though, > so we still need inputs from the kernel team. I also think > it's their place to decide which topic branch to merge it. > Could you please mention this Debbugs message on the PR? > > On 2026-05-13 at 15:48+02:00, pinoaffe wrote: > > I think inkscape and/or inkscape/pinned might be well-suited candidates > > to update on misc-world-rebuild, I've opened a PR to update inkscape > > (which is yet to be reviewed), how should I proceed? > > I think misc-world-rebuild could be a good topic branch for it > (<https://codeberg.org/guix/guix/pulls/8248> right?). > > On 2026-05-13 at 09:24+02:00, Hugo Buddelmeijer wrote: > > I somehow missed your earlier announcement. > > It's not you, it's me, I only posted to guix-patches > as required for a topic branch merge request, so probably > most people are not aware of it. > > Best wishes, > Phong
