From: Vagrant Cascadian <vagrant@debian.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Josselin Poiret <dev@jpoiret.xyz>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Leo Famulari <leo@famulari.name>,
guix-devel@gnu.org
Subject: Re: Should commit signing always be required for local work? [was Re: bug#63261: Recent changes to git config cause errors for non-committers]
Date: Wed, 24 May 2023 15:02:45 -0700 [thread overview]
Message-ID: <87sfblgzga.fsf@wireframe> (raw)
In-Reply-To: <CAFHYt57CSL97rm9mz=C=NSM431punEtPn2Sn_XzT2pFpYLKHSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]
On 2023-05-24, Felix Lechner via "Development of GNU Guix and the GNU System distribution." wrote:
> On Wed, May 24, 2023 at 2:01 PM Vagrant Cascadian <vagrant@debian.org> wrote:
>>
>> Please revert ASAP.
>
> I am not affected, but if I understood Maxim's message from 5/18
> correctly, the signature requirement was already reverted:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=03b453cfe54756bcec6b7c7dfaf71566d84c7a75
True! Figured this out, but wow it was circuitous!
So, the very non-obvious behavior was triggered by using git worktrees
with a mix of updated and not very updated checkouts...
So I have ~/src/guix and a ~/src/guix-workspace which is a worktree from
~/src/guix...
When I ran "./configure && ./bootstrap ... && make" from
~/src/guix-workspace it installed a rule in ~/src/guix/.git/config:
[include]
path = ../etc/git/gitconfig
So there was no obvious entry for [commit] in the configuration
file... so on a glance I missed that. Manually adding:
[commit]
gpgsign=false
Did work around the problem.
My initial check for ~/src/guix-workspace/.git/config was wrong, as it
was a worktree and .git is a file... so it obviously did not show any
configuration at a non-resolvable path.
Also updating the git checkout at ~/src/guix fixed the issue, even
though I was *working* from ~/src/guix-workspace and my working
directory etc/git/gitconfig had the fix...
Having an [include] entry pointing to files that were not in my working
directory from some arbitrary checkout (I will reiterate my working
directory actually *did* have the fix!) kind of broke my mind a bit.
I get it now. I think. :)
This is not the first time I have been burned by using worktrees, but it
was certainly the most convoluted!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-05-24 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 10:47 bug#63261: Recent changes to git config cause errors for non-committers Brian Cully via Bug reports for GNU Guix
2023-05-04 13:38 ` Maxim Cournoyer
2023-05-04 14:06 ` bug#63261: [PATCH] Makefile.am: Only auto-configure Git when available Maxim Cournoyer
2023-05-07 3:34 ` bug#63261: Recent changes to git config cause errors for non-committers Maxim Cournoyer
2023-05-13 19:03 ` Leo Famulari
2023-05-15 13:38 ` Maxim Cournoyer
2023-05-18 16:59 ` Should commit signing always be required for local work? [was Re: bug#63261: Recent changes to git config cause errors for non-committers] Leo Famulari
2023-05-19 3:24 ` Maxim Cournoyer
2023-05-19 9:34 ` Josselin Poiret
2023-05-19 16:22 ` Simon Tournier
2023-05-24 21:00 ` Vagrant Cascadian
2023-05-24 21:17 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-24 22:02 ` Vagrant Cascadian [this message]
2023-05-26 17:54 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfblgzga.fsf@wireframe \
--to=vagrant@debian.org \
--cc=dev@jpoiret.xyz \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.