On Wed, Aug 17, 2011 at 08:47:45PM +0400, Anton Korobeynikov wrote:> Hello Kurt, > > > lidl at hydra-146: svnsync sync file:///p/llvm/svn > > Transmitting file data ....... > > [...] > > ......svnsync: REPORT of 'http://llvm.org/svn/llvm-project/llvm': Could not read chunk size: connection was closed by server (http://llvm.org) > You cannot checkout the whole llvm repository. Only trunk or separate > tags/branches.Why can't I mirror the whole tree? I'm not doing a "checkout" of the tree (i.e. svn co .../head), but rather using the svnsync command (packaged with svn) to mirror the entire repository. I've done it with FreeBSD's SVN tree, which is very handy for having lots of different branches checked out locally on a variety of different machines. The entire FreeBSD SVN repository for that is about 5.3GB, and has 224948 revisions in it. (My mirror last updated yesterday.) Outside of the LLVM SVN server choking on revision 67358 of the tree (which appears to be size related and nothing else), the mirroring of the entire repository was working just fine. I got the first half (by revision count) before this problem cropped up. -Kurt
On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote:> Why can't I mirror the whole tree?The original reason for this limitation was that complete checkouts put a lot of stress on the server. We upgraded the server hardware since but I'm not sure whether we can lift the restriction. However, we have official git mirrors of most of the projects on llvm.org, would using them instead of svnsync be an option for you? - Ben
On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote:> On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server.While I agree bootstrapping a new mirror from scratch is time and resource consuming, this can be largely avoided by making a seed of the svn tree available. (Basically, I think that looks like a compressed tar file of the svn repository.) Or, a svnadmin dump of the repo could be made available for the adventurous. I was under the impression that the overhead to synsync a mirror of a complete svn repository wasn't too great. svnsync keeps track of the last revision in a repo that it has successfully fetched, and after that, will only ever request the changes newer than that.> We upgraded the server hardware > since but I'm not sure whether we can lift the restriction. > > However, we have official git mirrors of most of the projects on > llvm.org, would using them instead of svnsync be an option for you?Well, if the authoritative source code control system for all the llvm projects is svn, I'd just as soon use svn as the tool at my end. Having multiple source code control systems pulling and converting to their own internal storage formats doesn't gain me a lot. I suppose I can look into using the git mirror of the llvm tree. However, I think if the resources on the apache server were increased modestly, the svnsync would work just fine too. -Kurt
On Wed, Aug 17, 2011 at 3:47 PM, Benjamin Kramer <benny.kra at googlemail.com> wrote:> However, we have official git mirrors of most of the projects on > llvm.org, would using them instead of svnsync be an option for you?The page at http://llvm.org/docs/GettingStarted.html says that the git mirrors only include svn trunk. Is that still the case? If so, it's not a particularly good option for anyone who is interested in tracking more than just the single line of development. -- Brett Neumeier (bneumeier at gmail.com)