Efraim Flashner <efr...@flashner.co.il> skribis: > On Mon, Feb 17, 2025 at 02:48:59PM +0100, Andreas Enge wrote: >> Hello, >> >> I think something we need to do urgently is to run an ungrafting >> process - grafting takes a considerable amount of time when updating my >> system now, and I suppose it will also waste a bit of space. We should >> not burden the installation process with it. >> >> Did we not have a jobset on ci to automate this? >> >> As said in Brussels, I would be happy to test a new installation image >> on a further x86_64 I would like to get running Guix. > > We do have an ungrafting job, but it needs to be tweaked to exclude the > glibc graft.
I had to turn off that jobset shortly after activating it because the ‘glibc’ graft landed and it would have caused massive rebuilds without a clear way to get things merged (in fact, the glibc change is not “ungraftable” in the trivial way because it uses ‘git-fetch’, which would cause circular dependencies on old daemons). > I agree that we need to do an ungrafting run before a release but I'm > not sure we're at the pre-release ungraft yet. An ungraft run in > general would be a good thing. Yes. The way I see it, this can be done on ‘core-packages-team’ this time. Ludo’.
