[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: lily-git.tcl not working?

From: James Lowe
Subject: RE: lily-git.tcl not working?
Date: Thu, 14 Apr 2011 10:09:22 +0000


)-----Original Message-----
)From: address@hidden
)[mailto:address@hidden On
)Behalf Of Janek Warchol
)Sent: 14 April 2011 10:24
)To: address@hidden; Lilypond Bugreports
)Subject: lily-git.tcl not working?
)I'm afraid lily-git.tcl is broken.
)I've done a fresh install of Lilydev, using VirtualBox 4.0.4 on Win7.
)When i try to use lily-git.tcl, it begins working properly (says
)  Cloning LilyPond (this can take some time) ...
)  |git --git-dir=/home/janek/lilypond-git/.git init 2>@1
)  Initialized empty Git repository in /home/janek/lilypond-git/.git/
)  |git --git-dir=/home/janek/lilypond-git/.git config core.bare false 2>@1
)  |git --git-dir=/home/janek/lilypond-git/.git remote add -t master origin
)git://git.sv.gnu.org/lilypond.git 2>@1
)  |git --git-dir=/home/janek/lilypond-git/.git fetch --depth 1 2>@1
)But then nothing happens. It's been running for more than 30 minutes
)now, and still hasn't done anything (it only created an empty lilypond-git
)directory). I've checked my internet connection in virtual system and it's
)ok, also git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree is available in
)my web browser.
)I remember that when i used lily-git.tcl some time ago (February? it was
)with VirtualBox 4.0.0, also on Win7), everything went smoothly and
)downloading was finished in, let's say, less than 2 minutes? I have a fast
)internet connection.

I use Lilygit.tcl every single day. I've just used it this morning - I can't 
produce patches without it.
I have to admit that I have not had to use lilygit to pull a brand new install 
for a few weeks, but nothing has been added to Lilygit.tcl for a lot longer 
than that.

So this must be very specific to the first time you try to pull the tree or I 
am wondering if you have 'git push' access and have set up a 'ssh' 
login/password that LilyGit is not built to handle that case.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]