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

Git fetch failure in submodule if deeper submodule pointer updated

From
YPYngve N. Pettersen <yngve@vivaldi.com>
Date
Dec 19, 2020, 14:37 UTC
Message-ID
<op.0vvmwohypvqxoc@damia>
Hello all,

Recently we encountered a git fetch issue similar to the one I have reported earlier, <https://marc.info/?l=git&m=158979416620251&w=2>, which AFAICT has not yet been fixed.

In this case we had checked out a submodule, but not the submodule(s) below it.

The full submodule chain was like this:
   top->middle->bottom
The actual checkout was
   top->middle

Because only "middle" was needed for the cron job script used to push updates to "top" and "middle", "bottom" was never checked out (and it should not be necessary to do so, either).

When the pointer to "bottom" was recently updated in "middle", the cron job failed, because Git "could not access submodule bottom".

As I said in my earlier report, this kind of issues should, at most, only trigger a warning, not a fatal error.

The Git version on the system is Git v2.25.1 (Ubuntu 20.4)
This problem is not occuring in Git v2.17 on Windows.
Attached is a zipfile with a script that reproduces the problem.
-- 
Sincerely,
Yngve N. Pettersen
Vivaldi Technologies AS
Next: Philippe Blain
Message 1 of 2 in “Git fetch failure in submodule if deeper submodule pointer updated”
  1. Yngve N. PettersenDec 19, 2020
  2. Philippe BlainDec 21, 2020

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.