smudge error after updating GIT to Upgrading Git for Windows to 2.52.0.windows.1

[skumar146190]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

Git for Windows to 2.52.0.windows.1

Windows version

Other

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Options set during installation

NA

Other interesting things

The error is coming when the GIT for Windows is updated to version 2.52.0.windows.1 on the Windows remote agent which runs the Bamboo build and checks out the source code.

Terminal/shell

Other

Commands that trigger the issue

Git clone

Expected behaviour

The clone should be successful on the Machine

Actual behaviour

error: invalid key: filter.lfs.smudge
fatal: unable to write parameters to config file

1. The permissions are correct on the config file
2. The same works in the GIT is downgraded to 2.51.2

Repository

No response

[dscho]

error: invalid key: filter.lfs.smudge 
fatal: unable to write parameters to config file

1. The permissions are correct on the config file
2. The same works in the GIT is downgraded to 2.51.2

This is a bit dubious, given that standard Git for Windows already has that set without problems.

Maybe you can re-run the command after setting GIT_TRACE=1 to see which Git command causes that error, then try to run that command manually?

It is possible that Git LFS' post-checkout hack has problems with newer Git behavior, but I somehow doubt it.

[rimrul]

This looks like the same issue as https://lore.kernel.org/git/CALnO6CBJppT3ELyu54rJvP+uqcMomJS9Nr_JTgfssn8iqG7MWA@mail.gmail.com/T/#me236ebc6c19e3bffb6db9e9a569f7895b84e7865

[dscho]

@rimrul indeed, good catch! Thank you for paying attention to the Git mailing list!