On Fri, Jun 21, 2024 at 8:09 PM Tommy Murphy <tommy_mur...@hotmail.com> wrote:
> > The root cause is that .gitmodules entry for jimtcl was changed but > > not the submodule itself and that the required checkout was not > > available at the old repository. > > Sorry, but I'm still confused. > > After a clean checkout I see this in .gitmodules: > > [submodule "jimtcl"] > path = jimtcl > url = https://github.com/msteveb/jimtcl.git > > And if I execute git submodule init I get this: > > git submodule init > Submodule 'jimtcl' (https://github.com/msteveb/jimtcl.git) registered for > path 'jimtcl' > Submodule 'src/jtag/drivers/libjaylink' ( > https://gitlab.zapb.de/libjaylink/libjaylink.git) registered for path > 'src/jtag/drivers/libjaylink' > Submodule 'tools/git2cl' (https://git.savannah.nongnu.org/git/git2cl.git) > registered for path 'tools/git2cl' > > So where is the reference to the outdated https://repo.or.cz/jimtcl.git repo > coming from? > Tommy, a clean clone does not cause any issue. The issue comes from old clones that still keep the reference to the old submodule repo (if bootstrap was already called once). The local working tree I daily use has been cloned on June 2014! $ ls -l .git/description -rw-r--r-- 1 borneoa borneoa 73 Jun 16 2014 .git/description and I keep more than 100 local branches with devs and test plus 10 worktrees for independent checkout and builds. I'm not used at re-cloning fresh repositories, apart for some dedicated check. As I already said, I faced the issue of submodules repo URL out of sync after we changed all the repositories. I don't know how common the issue could be, but adding 'sync' fixes it. The instructions I posted a few e-mails before forces the out-of-sync repository to trigger the issue and to show that the 'sync' commands works fine. Regards, Antonio
