git/list[1] front-page[2] threads[3] people[4] search[5] about
 

issue upgrading git from 1.8.2.1 to 2.8.0

From
GTGennaro Torre <gtorre@tumblr.com>
Date
Apr 22, 2016, 22:44 UTC
Message-ID
<CA+UAp04e9-CcUJ+2fheHGw1q6MS6smyHhvyw34NeoT7HbKgnnQ@mail.gmail.com>
Hi,

Last week we upgraded git from 1.8.2.1 to 2.8.0. We saw some very weird behavior where git clones and pushes were working, but git fetch was not.

Here is our setup:

We have 10+ nodes caching a few repositories, the repos were originally cloned via git 1.8.2.1 with `git clone --mirror <repo>`

We have 3000+ nodes that take deploys using the git protocol, via `git fetch`, the existing repositories were also cloned via git 1.8.2.1 from the caching nodes.

When we upgraded to 2.8.0, all nodes received the upgrade.

We observed that when we tried to deploy code to the nodes (they run `git fetch` to update the repository) this would fail.

The fix: we deleted the repositories originally cloned via git 1.8.2.1, and did a `git clone <repo>` dropping a fresh repository that was cloned using git 2.8.0. Everything started working correctly. Our running theory here is that there was some incompatibility with the repositories cloned with the old version of git, and trying to run `git fetch` with the newest version of git.

Thanks, Gennaro

Next: Stefan Beller
Message 1 of 6 in “issue upgrading git from 1.8.2.1 to 2.8.0”
  1. Gennaro TorreApr 22, 2016
  2. Stefan BellerApr 22, 2016
  3. Junio C HamanoApr 22, 2016
  4. Jeff KingApr 22, 2016
  5. Jeff KingApr 23, 2016
  6. Jeff KingApr 23, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.