Re: No more releases: savannah sometimes does not like git fetch --depth

[Phil Holmes]

----- Original Message ----- 
From: "Graham Percival" <address@hidden>
To: <address@hidden>
Sent: Thursday, June 09, 2011 12:03 PM
Subject: No more releases: savannah sometimes does not like git 
fetch --depth


> I would like to highlight this bug:
> http://code.google.com/p/lilypond/issues/detail?id=1615
>
> After releasing 2.14.0 and 2.15.0, I deleted my GUB download/
> directory -- I thought it would be good to test that all the
> automatic download links were still valid, the whole system would
> work from scratch, etc.
>
> My attempt to build lilypond failed.  I have tried it half a dozen
> times, letting it idle for 5-10 minutes before cancelling the
> attempt and starting it again.  Every attempt fails.
>
> As per comment #1:
>  mkdir new-lilypond-dir
>  cd new-lilypond-dir
>  git init
>  git config core.bare false
>  git remote add -t master origin git://git.sv.gnu.org/lilypond.git
>  git fetch --depth 1
>
> fails every time.  Until this is fixed,
>  *** I CANNOT MAKE ANY MORE LILYPOND RELEASES. ***
>
>
> Past discussion suggests that this is a network-specific bug or
> something, which absolutely sucks for debugging.  Unfortunately my
> desktop is only accessible through 2 (yes, literally two!)
> intermediate ssh servers.  But I am hoping that somebody out there
> with a server can reproduce this problem, and then we can hand out
> ssh accounts to knowledgeable git people who can look at this.
>
> Cheers,
> - Graham


Just to be clear - you use SSH to log in to your desktop, which is the 
machine you use for GUB builds.  You're not suggesting that this is the 
problem, rather it's an inconvenience for anyone trying to work out why you 
have the problem?  The problem appears to be between your desktop (in the 
Uni?) and the savannah server?

--
Phil Holmes