search

SitePen / dojo-amd-converter

A legacy dojo to AMD conversion utility.
Other
11 stars 5 forks source link

fatal: reference is not a tree: b78b0764905164c139cc6a78bd818be9d2a06bd9 #35

Closed claudiopro closed 10 years ago

claudiopro commented 10 years ago

Hi, Looks like the Dojo submodule tree b78b0764905164c139cc6a78bd818be9d2a06bd9 doesn't resolve anymore. The repo can't be recursively cloned as advertised and requires non trivial manual intervention.

Here's a printout from the command line:

$ git clone --recursive https://github.com/SitePen/dojo-amd-converter
Cloning into 'dojo-amd-converter'...
remote: Reusing existing pack: 106, done.
remote: Total 106 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (106/106), 70.13 KiB | 23.00 KiB/s, done.
Resolving deltas: 100% (19/19), done.
Checking connectivity... done
Checking out files: 100% (49/49), done.
Submodule 'dojo' (https://github.com/dojo/dojo.git) registered for path 'dojo'
Submodule 'esprima' (https://github.com/ariya/esprima.git) registered for path 'esprima'
Cloning into 'dojo'...
remote: Reusing existing pack: 26427, done.
remote: Total 26427 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (26427/26427), 9.15 MiB | 375.00 KiB/s, done.
Resolving deltas: 100% (16632/16632), done.
Checking connectivity... done
fatal: reference is not a tree: b78b0764905164c139cc6a78bd818be9d2a06bd9
Cloning into 'esprima'...
remote: Reusing existing pack: 4832, done.
remote: Counting objects: 4, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4836 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (4836/4836), 6.56 MiB | 507.00 KiB/s, done.
Resolving deltas: 100% (2851/2851), done.
Checking connectivity... done
Submodule path 'esprima': checked out '2326e8361ae9ac3d8e49b874e8d59243326907ad'
Unable to checkout 'b78b0764905164c139cc6a78bd818be9d2a06bd9' in submodule path 'dojo'

If you click on the Dojo submodule linked in the repo, this URL returns 404: https://github.com/dojo/dojo/tree/b78b0764905164c139cc6a78bd818be9d2a06bd9

Cheers, Claudio

claudiopro commented 10 years ago

From the docs:

One common problem happens when a developer makes a change locally in a submodule but 
doesn’t push it to a public server. Then, they commit a pointer to that non-public state
and push up the superproject. When other developers try to run git submodule update, the
submodule system can’t find the commit that is referenced, because it exists only on the
first developer’s system. If that happens, you see an error like this.

Looks like the submodule reference was last updated by @mmaxwell with commit 28d9bf35e72e0359dff6f96e46ad08eeedf1723d.

mmaxwell commented 10 years ago

This was a year ago, so it's hard to say, but I don't think I would have directly modified the dojo repository. Is it possible this particular branch was removed at some point in time?

@csnover

claudiopro commented 10 years ago

Thanks to both for the quick response!