[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Error While Checking out Git Repository

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 8 Feb 2012 15:41:47 -0500

The GitHub server is definitely trying to transmit the svn:entry: property
set ("svn:entry:committed-rev", "svn:entry:committed-date",
"svn:entry:last-author"), as can be seen in your output below. But there
are some places where it fails to do so.

For example, the directory
"/home/cmpilato/tests/PoliteCaptcha.git/tags/v0.1" is coming down the pipe
without any "svn:entry:" properties at all. Now, it's permissible for the
author and date to be missing, because that scenario can occur normally
within Subversion due to the user lacking certain access privileges. But
the 1.7 client codebase now requires that the last-changed revision be valid.

On 02/08/2012 03:34 PM, Nick Hengeveld wrote:
> Thanks for checking - we want to be fully compatible so any information like
> this helps.
>
> The checkout URL is the same as the HTTP clone URL, and the .git suffix is
> optional for both git and svn clients.
>
> I may have misunderstood what's up with the ra_serf library, I thought that
> was related to HTTP protocol changes introduced in 1.7 and that 1.7 clients
> would fall back to old behavior for <1.7 servers. I'll read up on this, if
> you have any pointers to documentation related to ra_serf that would be helpful.
>
> I'm seeing this XML (sans txdelta) in a debug session with a copy of that repo:
>
> <S:add-file name="packages.config" >
>
> <D:checked-in><D:href>/NuGet/PoliteCaptcha/!svn/ver/25/tags/v0.1/Sample/packages.config</D:href></D:checked-in>
> <S:set-prop name="svn:entry:committed-rev">25</S:set-prop>
> <S:set-prop
> name="svn:entry:uuid">73fd378b-872a-2eee-a48e-ce57b7db7bff</S:set-prop>
> <S:set-prop
> name="svn:entry:committed-date">2012-02-07T16:47:44.000000Z</S:set-prop>
> <S:set-prop name="svn:entry:last-author">anglicangeek</S:set-prop>
> <S:txdelta>...</S:txdelta>
>
> <S:prop><V:md5-checksum>f0315b5b2e0ba6a4cb3cde943d8ae9df</V:md5-checksum></S:prop>
> </S:add-file>
>
> It's possible that production is returning something different, I'll look
> into that next.
>
> On Wed, Feb 8, 2012 at 11:47 AM, C. Michael Pilato <cmpilato_at_collab.net
> <mailto:cmpilato_at_collab.net>> wrote:
>
> 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.)
>
>
> --
> For a successful technology, reality must take precedence over public
> relations, for nature cannot be fooled.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2012-02-08 21:42:29 CET

This is an archived mail posted to the Subversion Dev mailing list.