git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeppe Øland" <joland@gmail.com>
To: git@vger.kernel.org
Subject: 2.46 submodule breakage
Date: Mon, 5 Aug 2024 13:31:59 +0200	[thread overview]
Message-ID: <CA+osTZVApTAMogBDMaPDEVViJHrFT=BOer=Py4fjTvpsifzfKA@mail.gmail.com> (raw)

Hi there,

I just upgraded from Git 2.45.2 to Git 2.46 (Git for Windows, but I
don't think this has anything to do with that), and it seems to have
broken some submodule stuff for me.

Specifically, when I do a recursive pull, I get the following error
from one of the submodules:
    fatal: Unable to find current revision in submodule path 'path/to/sub'

There are other submodules in the repo that work fine.
The only difference with this one is that it was added using the
--name option, so internally it's just known as "sub".

Looks like the problem happens in the final pull stage when it executes:
    git submodule--helper update --recursive --rebase --

A recursive clone with 2.46 works fine, but any subsequent recursive
pull gives the error.
So far I haven't been able to fix it, except by downgrading to 2.45.2.

Any ideas?

Regards,
-Jeppe

             reply	other threads:[~2024-08-05 11:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 11:31 Jeppe Øland [this message]
2024-08-06 13:18 ` 2.46 submodule breakage Jeppe Øland
2024-08-06 18:26   ` Eric Sunshine
2024-08-07  6:40     ` Patrick Steinhardt
2024-08-07  7:38       ` Patrick Steinhardt
2024-08-07 16:09         ` Junio C Hamano
2024-08-07 12:43 ` [PATCH 0/6] Improvements for ref storage formats with submodules Patrick Steinhardt
2024-08-07 12:43   ` [PATCH 1/6] builtin/submodule: allow cloning with different ref storage format Patrick Steinhardt
2024-08-07 14:45     ` [PATCH 0/6] Improvements for ref storage formats with submodules Jeppe Øland
2024-08-07 22:55     ` [PATCH 1/6] builtin/submodule: allow cloning with different ref storage format Junio C Hamano
2024-08-08  7:00       ` Patrick Steinhardt
2024-08-08 16:08         ` Junio C Hamano
2024-08-08 16:19           ` Patrick Steinhardt
2024-08-08 17:26             ` Junio C Hamano
2024-08-07 12:43   ` [PATCH 2/6] builtin/clone: propagate ref storage format to submodules Patrick Steinhardt
2024-08-07 23:07     ` Junio C Hamano
2024-08-07 12:43   ` [PATCH 3/6] refs: fix ref storage format for submodule ref stores Patrick Steinhardt
2024-08-07 12:44   ` [PATCH 4/6] submodule: fix leaking fetch tasks Patrick Steinhardt
2024-08-07 12:44   ` [PATCH 5/6] submodule: fix leaking seen submodule names Patrick Steinhardt
2024-08-07 12:44   ` [PATCH 6/6] object: fix leaking packfiles when closing object store Patrick Steinhardt
2024-08-07 13:18   ` [PATCH 0/6] Improvements for ref storage formats with submodules Patrick Steinhardt
2024-08-08  1:09   ` Junio C Hamano
2024-08-08  7:00     ` Patrick Steinhardt
2024-08-08  7:35 ` [PATCH v2 0/8] " Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 1/8] git-submodule.sh: break overly long command lines Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 2/8] builtin/submodule: allow cloning with different ref storage format Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 3/8] builtin/clone: propagate ref storage format to submodules Patrick Steinhardt
2024-08-08  8:03     ` Kristoffer Haugsbakk
2024-08-08 13:29       ` Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 4/8] refs: fix ref storage format for submodule ref stores Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 5/8] builtin/submodule: allow "add" to use different ref storage format Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 6/8] submodule: fix leaking fetch tasks Patrick Steinhardt
2024-08-08  7:35   ` [PATCH v2 7/8] submodule: fix leaking seen submodule names Patrick Steinhardt
2024-08-08  7:36   ` [PATCH v2 8/8] object: fix leaking packfiles when closing object store Patrick Steinhardt
2024-08-08 16:24   ` [PATCH v2 0/8] Improvements for ref storage formats with submodules Junio C Hamano

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='CA+osTZVApTAMogBDMaPDEVViJHrFT=BOer=Py4fjTvpsifzfKA@mail.gmail.com' \
    --to=joland@gmail.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).