Mats Erik Andersson <[email protected]> writes: > måndag den 9 maj 2011 klockan 12:36 skrev Simon Josefsson detta: >> >> It works fine here -- although I use --gnulib-srcdir=$HOME/src/gnulib >> --skip-po. Could you try to check out gnulib manually and then point to >> that checkout using --gnulib-srcdir? > > I succeeded once with a manual > > git clone --depth 2 git://git.sv.gnu.org/gnulib.git > > then failed six times in a row with depth two or one, > finally giving up on it. Trying without a depth option, > the cloning grinds to a halt after resolving 51% (49800). > this repeats itself tree times, cuasing full CPU load. > I even tried downgrading to git-1.7.2.3 with some manual > package intervention that followed suite. No success. > > In the only successful case I have never before observed > such timedelay until the cloning could even begin. > The past half a year that step was immediate.
Very strange! Which system are you using? I'm using git 1.7.2.5 from Debian Squeeze and I check out regulary from git.sv.gnu.org and only noticed problems some rare times. I was able to complete a checkout just now: jas@latte:~$ time git clone git://git.sv.gnu.org/gnulib.git Cloning into gnulib... remote: Counting objects: 114667, done. remote: Compressing objects: 100% (19271/19271), done. remote: Total 114667 (delta 95589), reused 114387 (delta 95341) Receiving objects: 100% (114667/114667), 19.08 MiB | 739 KiB/s, done. Resolving deltas: 100% (95589/95589), done. real 1m5.680s user 0m37.166s sys 0m1.420s jas@latte:~$ Hm. Maybe you end up using git over http for some reason? That will be very inefficient for a large repository like gnulib. Maybe you can download a snapshot by clicking 'snapshot' on this page: http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=tree Anyway, if you managed to get a checkout, then all is fine... /Simon
