gh-151365: Temporarily downgrade Git to prevent fatal error

[hugovk]

Downgrading takes 7 seconds.

Upgrading via build from source (+cache) or Homebrew are likely to take longer.

• Issue: GitHub Actions: Docs/Docs CI fails randomly with "fatal: shallow file has changed since we read it" error (git 2.54.0 regression) #151365

[webknjaz]

Is it possible to explicitly declare the version limit in the command, plz?

[vstinner]

LGTM.

It works as expected. For example, I see "git version 2.43.0" in the "Downgrade Git" step of Docs/Docs CI job.

[vstinner]

I didn't know this /noble-updates syntax. I understand that it's a way to request the git version of Ubuntu 24.04.

[hugovk]

Is it possible to explicitly declare the version limit in the command, plz?

Something like this?

sudo apt-get install -y --allow-downgrades 'git=1:2.43.*' 'git-man=1:2.43.*'

[webknjaz]

@hugovk yep, something along those lines. I was hoping for a <= broken_version.

[vstinner]

I suppose that this change should be backported to stable branches (3.13 to 3.15).

[webknjaz]

@vstinner I've already labeled it for 3.15, but one of the workflow files doesn't exist in 3.14 so automatic backporting will fail farther back. Once it's ported into 3.15, somebody needs to look into picking it back into older branches manually.

[vstinner]

I've already labeled it for 3.15

The "needs backport to 3.15" label is better for that: it backports automatically the change to 3.15.

[miss-islington-app]

Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15.
🐍🍒⛏🤖

[bedevere-app]

GH-155532 is a backport of this pull request to the 3.15 branch.

[webknjaz]

@vstinner oops, for some reason I thought I did that but confused the two labels 🤦‍♂️ sry