git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn troubles with calendarserver SVN repo

From
Jon Seymour <jon.seymour@gmail.com>
Date
Nov 30, 2013, 08:54 UTC
Message-ID
<CAH3Anro=vM2JLLZhdJ4nnO3qLhw4yV2JFT8EwC3jcbbGrj4H=g@mail.gmail.com>
In-Reply-To
<52991FE0.6040503@redhat.com>

I have seen this behaviour, though never determined the root cause .Probably the simplest thing you can do without access to the server is to put your git svn fetch into a bash while loop, like so:

while ! git svn fetch; do :; done;
jon
On Sat, Nov 30, 2013 at 10:14 AM, Matěj Cepl <mcepl@redhat.com> wrote:
Show 32 quoted lines
> Hi,
>
>
>
> I am trying to git-svn clone
> https://svn.calendarserver.org/repository/calendarserver/CalendarServer/
> and I cannot say I am much succesful. Every couple of hundred of commits
> I get this:
>
>
> RA layer request failed: REPORT of
> '/repository/calendarserver/!svn/vcc/default': could not connect to
> server (https://svn.calendarserver.org) at
> /usr/local/share/perl5/Git/SVN/Ra.pm line 290.
>
>
> and git-svn stops. When restarting git svn fetch, it fetches
> another couple of hundred commits and then fails again. Given
> that there are 11000+ commits just in the trunk, I am afraid of
> a long long night. Did anybody managed to clone this repo? Or is
> there some way how to make git-svn more patient (this error
> means the SVN server is a bit flakey, right)?
>
> Best,
>
> Matěj
> --
> http://www.ceplovi.cz/matej/, Jabber: mcepl@ceplovi.cz
> GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
>
> A day without sunshine is like night.
>
Previous: Matěj CeplNext: Matěj Cepl
Message 2 of 5 in “git-svn troubles with calendarserver SVN repo”
  1. Matěj CeplNov 29, 2013
  2. Jon SeymourNov 30, 2013
  3. Matěj CeplDec 2, 2013
  4. Jon SeymourDec 2, 2013
  5. Ramkumar RamachandraDec 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.