Thread (2 messages) 2 messages, 2 authors, 2020-12-21

Git fetch failure in submodule if deeper submodule pointer updated

From: Yngve N. Pettersen <hidden>
Date: 2020-12-19 14:44:33

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

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help