Lazygit: Unable to run on CentOS 7

[JoeKlemmer]

Describe the bug
Whenever I try to run it, it will immediately crash with the error "panic: fatal: unknown field name: HEAD"

To Reproduce
Steps to reproduce the behavior:

1. Go to any directory with a git repo
2. Run lazygit
3. Immediate crash.

Expected behavior
lazygit to run.

Screenshots
This is a screenshot of the ssh session. It's the only way I could get the full error output. (Apologies for the dark color combination)

Desktop (please complete the following information):

• OS: CentOS Linux release 7.8.2003 (Core)
• Lazygit Version 0.20.9

Additional context
This has been happening since at least v0.20.4, but I have had no problems on my WIn10 box.

[kylepollina]

I think this is a duplicate of #719 , I would suggest upgrading git to version 2 as centos only comes with git version 1. Or downgrade to lazygit v 16.2. There are more detailed solutions in #719 so take a look at that

[JoeKlemmer]

That was it. I upgraded to git 2.24 and thighs work just fine.

FWIW, the easiest way to do this was to uninstall git 1.13 then use the
Inline with Upstream Stable ( https://ius.io ) repo.

On Mon, Aug 17, 2020 at 4:05 PM kylepollina [e-mail]
wrote:

I think this is a duplicate of #719
https://github.com/jesseduffield/lazygit/issues/719 , I would suggest
upgrading git to version 2 as centos comes with git version 1. Or downgrade
to lazygit v 16.2

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jesseduffield/lazygit/issues/905#issuecomment-675085398,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRYUXLHIZ6OIHUODBBSNWTSBGEQ5ANCNFSM4O7225NA
.

--

Joe Klemmer

[image: https://]about.me/joeklemmer
https://about.me/joeklemmer?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=plaintext

[jesseduffield]

Glad you got it running in the end @JoeKlemmer :) I've just merged https://github.com/jesseduffield/lazygit/pull/980 which will now show a proper error when the git version is below 2.0. I might put more effort in at some point for more backwards compatibility but 2.0 was made in 2014 so I think we're already fairly backwards compatible. Closing :)