Version: Subversion (using KDE 4.5.4) OS: Linux I have set kdesrc-build to checkout KDE branch 4.6 and qt-copy branch 4.6-stable-patched. But no matter what branch of qt-copy I use, I get this error: # kdesrc-build running: 'git' 'clone' '-v' '--' 'git://gitorious.org/+kde-developers/qt/kde-qt.git' '/home/steven/kdesrc/qt-copy' Initialized empty Git repository in /home/steven/kdesrc/qt-copy/.git/ fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I've currently skipped down to the first module-set and I can clone all those perfectly. It's just qt-copy I have an issue with - even with the master branch. Reproducible: Always
I hate to say this but I'm 99% sure this is a problem with gitorious.org, which has always had trouble with cloning large modules (such as Qt ;) The fact that you see git output at all for qt-copy is an example of the one workaround that has had some success for kdesrc-build (leaving the git output going to stdout with the -v flag keep the gitorious.org end from dying as quickly). If even that workaround doesn't help I'm not sure there's much else that can be done except for trying again later. If gitorious.org supports tarball snapshots let me know and I'll see if I can cook up a system using those instead, since that supports resuming.
I also forgot to add that the terminal says: "Can't checkout qt-copy: no such file or directory at ./kdesrc-build line 2190." I tried adding the -v flag but the connection drop just as fast. >"I'm not sure there's much else that can be done except for trying again >later." So this could be a issue with gitorious' server(s) being overloaded? Or is it a bug/issue at their end that I should talk to them about? >"If gitorious.org supports tarball snapshots let me know" Going to ask them right now .)
> > "I'm not sure there's much else that can be done except for trying again later." > So this could be a issue with gitorious' server(s) being overloaded? Or is it a bug/issue at their end that I should talk to them about? My understanding is that they use a custom git protocol daemon on their website to support some of their extra features, merge requests, etc. If the site is heavily loaded then it can take a while for that daemon to transmit data to the client (i.e. your computer waiting for 'git clone') and eventually the Internet socket hits a timeout and the entire attempt is aborted. This was about a year ago when I instituted the current workaround IIRC so I'd like to think they fixed it, but I'm honestly not sure.
Created attachment 55708 [details] Copy of emails with Gitorious help
I attached a copy of the email discussions I've been having on Gitorious' Google Groups page. I hope I didn't make it seem that I was in charge of making the script to the person I was talking too, since you deserve all the credit, Michael. But, how Gitorious works with tarballs is all there. You can jump into the discussion by emailing gitorious@googlegroups.com I'm still struggling to get qt-copy to download, I hope eventually this can help out kdesrc-build!
Maybe I should just stop being passive-aggressive and actually converse with them directly with the issue I (and other users) have. ;)
http://lists-archives.org/git/700614-cannot-clone-redirecting-stdout.html This is one of the more relevant message on the git list which describes why kdesrc-build has its current workaround of outputting gitorious.org git-clones to stdout. I've also sent a message to the Google group and we'll see what happens.
Michael did you get the email from Marius who is from Gitorious Support? I tested his solution (using git://gitorious.org/qt/kde-qt.git as the repo address), but I still can't get it working. I don't think I ever had this problem with the last stable version of your script, so I'll test v1.12 (stable)
I saw the email, I'm simply waiting to see if you can confirm whether it fixes the issue or not. :-/
Neither the default repo address or the one provided by Marius works in the trunk version of kdesrc-build (I checked out the trunk version today). For the stable version, with the default repo address and the one provided by Marius, the script works perfectly. So its got to be something in the trunk version of kdesrc-build.
Hmm, that's unfortunate then. Only change I can think of is the change to the output of the git clone process. But I'm pretty sure I had only changed the output for non-Qt git modules.
You did change the output for qt cloning. It now says "cloning qt-copy" (at which point the script waits, then fails). In stable, the script immediately counts the remote objects and then compresses them, etc until the cloning is over. I'll give a comparison tomorrow... I need sleep :)
SVN commit 1214740 by mpyne: Re-enable git-clone output for qt-copy. I thought that using the -v flag to git would be sufficient to keep gitorious.org's git daemon running right when cloning qt-copy, but that output also *must* be redirected to the tty. This restores the kdesrc-build 1.12 behavior of outputting git modules clone status to the tty, but only for qt-copy since otherwise gitorious.org's git daemon will fail for some strange reason. This hopefully should fix bug 262145, thanks to the reporter for being so proactive in reporting the bug (including to gitorious) and testing changes and older versions of kdesrc-build. BUG:262145 M +3 -3 kdesrc-build WebSVN link: http://websvn.kde.org/?view=rev&revision=1214740
Thank you for the fix Michael. It just tested it and it works! This is why I love kdesrc-build :)