I'm happy to try it with 1.7, too, but couldn't easily figure out the correct checkout URL:
$ svn co https://github.com/NuGet/PoliteCaptcha.git svn: E175009: Unable to connect to a repository at URL 'https://github.com/NuGet/PoliteCaptcha.git' svn: E175009: XML parsing failed: (411 Length Required) $ Ah!! That was with ra_serf. With ra_neon, I get the reported behavior: $ svn co https://github.com/NuGet/PoliteCaptcha.git A PoliteCaptcha.git/branches A PoliteCaptcha.git/tags A PoliteCaptcha.git/tags/v0.1 [...] A PoliteCaptcha.git/tags/v0.1/Sample/Web.Release.config A PoliteCaptcha.git/tags/v0.1/Sample/Web.config A PoliteCaptcha.git/tags/v0.1/Sample/packages.config svn: E235000: In file 'subversion/libsvn_wc/wc_db.c' line 1608: assertion failed (SVN_IS_VALID_REVNUM(changed_rev)) Aborted $ I'll take a peek with Neon's debugging enabled and see what I can see. (But please do note that it appears GitHub appears to be incompatible with Subversion clients which use the newer ra_serf library.) On 02/08/2012 02:10 PM, Nick Hengeveld wrote: > C. Michael Pilato <cmpilato <at> collab.net> writes: > >> >> Well, supported by whom? >> >> At first blush, it would appear that the GitHub server didn't transmit a >> valid svn:entry:committed-rev property value for one of the directories your >> checkout is attempting to register with Subversion's working copy >> administration library. If this problem is repeatable, it would be great to >> get a network trace of the failing checkout. >> > > > I'm happy to take a look at this from the GitHub side - can the person who > reported this contact supp...@github.com? > > FWIW, I just tried a checkout with a 1.6.16 client and didn't have any > problems. I'll see if I can reproduce it with a 1.7 client. > > --Nick > -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
