On 02/07/2012 02:49 PM, TheBlueSky .Net wrote:
> Hello,
>
> I was checking out a Git repository
> (https://github.com/NuGet/PoliteCaptcha.git) when I encountered the
> following error near the end of getting all the files:
>
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
> you were trying to do.
> But please first search the mailing list archives for the error message
> to avoid reporting the same problem repeatedly.
> You can find the mailing list archives at
> http://subversion.apache.org/mailing-lists.html
>
> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C):
>
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\wc_db.c'
> line 1588: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))
>
> And if someone is wondering, checking out from github using SVN client is
> supported.
Well, supported by whom? :-)
This community has only signed up to support Subversion's command-line
client checking out from a Subversion mod_dav_svn or svnserve server. I
must assume that github has put together their own Subversion-esque server
software which communicates with git repositories. Obviously, we expect our
client to behave properly against any server that wields our protocols
correctly, but first we need to establish that GitHub's server is such a server.
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.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2012-02-07 21:20:46 CET