Re: git-svn clone --stdlayout causes "fatal: refs/remotes/trunk: not a valid SHA1"

Jonathan Nieder· Nov 1, 2010, 17:11 UTC · lore

Hi Klaus,

Klaus wrote:

Show 22 quoted lines

> this works ok.
>        git svn clone svn://localhost/MyPrj MyPrj  --username=MyUserName
>     
> this causes the error (I added "--stdlayout")
>        git svn clone svn://localhost/MyPrj MyPrj  --stdlayout --username=MyUserName
>     
> last line of error output
> …
>         M       Wiki/MyPrj_wiki/MyPrjHistory.wiki
> W: -empty_dir: MyPrjAll/trunc/MyPrjGui/DotNet11MainMenu.cs
> r141 = ad4166b68d89c4b795fb74a4fc09168160b2f60e 
> (refs/remotes/tags/LastGuiMonolit_071207@142)
> W: +empty_dir: MyPrjAll/trunc/MyPrj.Gui
> r142 = 0decd283bb36f9296172970eeab377b6f93777ba 
> (refs/remotes/tags/LastGuiMonolit_071207@142)
> Found branch parent: (refs/remotes/tags/LastGuiMonolit_071207) 0decd283bb36f9296172970eeab377b6f93777ba
> Following parent with do_switch
> Successfully followed parent
> r143 = a4861b50a5f1c067210b30951dc06012a7d2da25 
> (refs/remotes/tags/LastGuiMonolit_071207)
> fatal: refs/remotes/trunk: not a valid SHA1
> update-ref refs/heads/master refs/remotes/trunk: command returned error: 128

Is your repository public? If not, could you give a sketch of the project history, for example by running

 $ git log --oneline --name-status

from a successful (non-stdlayout) clone?

> note: although i am using ms-windows7 i mailed this report to the debian 
> mailing-list because i think that

Redirecting discussion to the git mailing list; maybe someone there will have other ideas for debugging.

Thanks for reporting, Jonathan

Jonathan Nieder· Nov 1, 2010, 18:14 UTC · re: Jonathan Nieder · lore

Jonathan Nieder wrote:

Show 6 quoted lines

> Is your repository public?  If not, could you give a sketch of the project
> history, for example by running
>
>  $ git log --oneline --name-status
>
> from a successful (non-stdlayout) clone?

Since your trunk directory is called "trunc" rather than "trunk", it seems stdlayout is not appropriate for the import.

There is also a tag named "trunc".  Not sure how that will work out. :(

Anyway, hopefully that information can help interested people to reproduce this problem, document it, and make it fail with a better error message.

For your import, perhaps

	--trunk=<trunk dir> \
	--tags=<tags dir>

would give better results?

If this is a one-time conversion (i.e., it will not need to be updated with later changes from svn), then you might also find some of the methods described in

 http://thread.gmane.org/gmane.comp.version-control.git/158940/focus=159054

helpful (especially use of "git filter-branch" to extract subdirectories from a simple whole-tree import).

Hope that helps, Jonathan