Hi, On Wed, 07 Oct 2026 15:29:43 -0700 Vagrant Cascadian <[email protected]> wrote:
> On 2026-10-03, Denis 'GNUtoo' Carikli wrote: > > - I managed to backport patches on top of Guix 1.5.0. > > > > They are in the guix-1.5.0-backports branch in > > https://git.sr.ht/~gnutoo/guix. > > I tried applying those patches, but could not get the test suites to > pass, or even when ignoring the test suites, failed to actually get > guix-daemon 1.5.0 to work correctly... lots of issues with corrupt > substitutes. That's exactly my point. Here I need help and I can't do everything. So my goal is to get help from people from the future backports Guix team during the review. And the Linux documentation that explains how to learn to backport patches also says that involving people that made these patches in the review would be a good thing, but this can only happen in Guix because these people are not expected to be Debian contributors. Another issue is that in my backports there were conflicts and I've tried to resolve them as best as I could, but I learned later on (in that documentation) that it was a good idea to investigate more deeply merge conflicts, by finding and reading the patches that got in the way, instead of just trying to resolve them like I'm used to. I've started posting patches (https://codeberg.org/guix/guix/pulls/11832) for the Guix documentation on creating a team for backports and I'll try to see if tomorrow I can gather more help at Guix @ Paris, a monthly Guix meeting. Since "test that don't pass" seem to be a real concern for downstream distributions, I've also modified slightly my plan to make sure this is in scope for backporting patches. Denis.
pgp4t5QH_qMC4.pgp
Description: OpenPGP digital signature
