From: "Yngve N. Pettersen" <yngve@vivaldi.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git fetch failure in submodule if deeper submodule pointer updated
Date: Sat, 19 Dec 2020 15:37:26 +0100 [thread overview]
Message-ID: <op.0vvmwohypvqxoc@damia> (raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
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
[-- Attachment #2: generate_test.zip --]
[-- Type: application/zip, Size: 548 bytes --]
next reply other threads:[~2020-12-19 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 14:37 Yngve N. Pettersen [this message]
2020-12-21 1:08 ` Git fetch failure in submodule if deeper submodule pointer updated Philippe Blain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.0vvmwohypvqxoc@damia \
--to=yngve@vivaldi.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).