GNU bug report logs - #79099
[PATCH 00/34] git-version rewrite

Previous Next

Full log

View this message in rfc822 format

From: Nicolas Graves <ngraves <at> ngraves.fr>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: 79099 <at> debbugs.gnu.org
Subject: [bug#79099] [PATCH 00/34] git-version rewrite
Date: Fri, 22 Aug 2025 18:46:14 +0000 (UTC)

-----Original Message-----
From: Nicolas <ngraves <at> ngraves.fr>
To: Simon <zimon.toutoune <at> gmail.com>
Cc: Nicolas <guix-patches <at> gnu.org>; 79099 <79099 <at> debbugs.gnu.org>
Date: Friday, 22 August 2025 8:16 PM CEST
Subject: Re: [bug#79099] [PATCH 00/34] git-version rewrite



> I guess this issue is the counter-part of [1].

> Therefore, how is it going on QA?

The issue is that since the scope of changes is huge, both times I tried to evaluate that through QA resulted in a failure to merge, because while patches were processed, changes in the source code happened.

I tried asking for opening a branch on CI, which would be another way to check that there are no rebuilds (if no rebuilds are necessary compared to master). I can update the -dev branch, but not until Sunday afternoon at least. If you can rebase it (simply always select the upstream version, the worst case is a CLI warning) on master and create a branch, we can see / check if there are some unexpected rebuilds.

Cheers,
Nicolas

1: https://codeberg.org/guix/guix/pulls/1571#issuecomment-5994862

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.