Hi Leo, On Thu, 04 Mar 2021 at 14:07, Leo Famulari <[email protected]> wrote: > On Thu, Mar 04, 2021 at 10:41:34AM +0100, zimoun wrote: >> On Wed, 03 Mar 2021 at 13:51, Leo Famulari <[email protected]> wrote: >> > * Update tzdata >> >> “guix refresh tzdata -l” provides couple of dependants. Is it >> reasonable to update it for the next release? > > For me, I see 1765 dependents (a "couple" is 2). We have the capacity to > rebuild them in this timeframe.
I should have had emphasized «couple». ;-) Ah, I miss something because I thought this kind of upgrade was a candidate for core-updates or staging. Anyway. :-) Added to the TODO. :-) > The staging branch has been completed, along with the previous > ungrafting. But now there are new grafts and, in my opinion, we don't > have time to do another staging round before April 18. Ungrafting as an instance of «Sisyphus stone». ;-) >> From my point of view, the whole “ungrafting” process is unclear on two >> sides: 1. how to effectively ungraft a package? i.e., what are the >> typical steps? and 2. what is the list of packages to ungraft? > > 1) Move the changes of the replacement packages into the packages that > were being replaced. For example, we should move the patch > 'python-2.7-CVE-2021-3177.patch' from the origin of python-2.7/fixed to > the origin of python-2.7. > > 2) Grep on the master branch in gnu/packages for '(replacement'. That > will show you every graft. Thanks for the explanations. I will try to contribute to the effort in the next days. Does it exist a way to list the grafts? I mean there is “guix build --no-grafts” but I do not know how to get what grafts which will be applied beforehand. Cheers, simon
