{"thread":{"id":"21222","subject":"Bad URL passed to RA lay","startedAt":"2009-10-13T07:35:08Z","lastAt":"2009-10-14T07:07:24Z","messageCount":2,"participants":["m.skoric@web.de","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"124820","messageId":"1952825702@web.de","threadId":"21222","inReplyTo":null,"subject":"Bad URL passed to RA lay","fromName":"","fromEmail":"m.skoric@web.de","sentAt":"2009-10-13T07:35:08Z","receivedAt":"2009-10-13T07:35:08Z","isPatch":false,"sender":{"key":"m.skoric@web.de","avatar":null},"body":"Hi List,\n\ni have a problem with git-svn clone / fetch. I get following error while doing one of previous command -> \"Bad URL passed to RA lay\"\nThis happens because a branch doesn't exists in svn anymore and git wants to retrieve data from it. Here is the complete error message\n\nInitializing parent: Abo-Uebernahme (Bug #994)@341\nFound possible branch point: \"quoted\"..trunk => \"quoted\"...Abo-Uebernahme (Bug #994), 203\nFound branch parent: (Abo-Uebernahme (Bug #994)@341) bb831869748c98bf97d105c5894ae65331c95c08\nBad URL passed to RA layer: Malformed URL for repository at /usr/bin/git-svn line 4311\n\ngit version 1.6.3.3\n\nAynone else has this Problem?\nCan anyone help me?\n\nThanks in advance\n\nMajk\n______________________________________________________\nGRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!\nJetzt freischalten unter http://movieflat.web.de\n"},{"id":"124948","messageId":"20091014070724.GA18600@dcvr.yhbt.net","threadId":"21222","inReplyTo":"1952825702@web.de","subject":"Re: Bad URL passed to RA lay","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2009-10-14T07:07:24Z","receivedAt":"2009-10-14T07:07:24Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"m.skoric@web.de wrote:\n> Hi List,\n> \n> i have a problem with git-svn clone / fetch. I get following error\n> while doing one of previous command -> \"Bad URL passed to RA lay\" This\n> happens because a branch doesn't exists in svn anymore and git wants\n> to retrieve data from it. Here is the complete error message\n> \n> Initializing parent: Abo-Uebernahme (Bug #994)@341\n> Found possible branch point: \"quoted\"..trunk => \"quoted\"...Abo-Uebernahme (Bug #994), 203\n> Found branch parent: (Abo-Uebernahme (Bug #994)@341) bb831869748c98bf97d105c5894ae65331c95c08\n> Bad URL passed to RA layer: Malformed URL for repository at /usr/bin/git-svn line 4311\n> \n> git version 1.6.3.3\n> \n> Aynone else has this Problem?\n\nHi,\n\nUnlikely, not many people use URIs as weird as yours :)\nThe existing test case (t9118) we have was also inspired by you,\non the same branch, even.\n\n> Can anyone help me?\n\nWhat exactly is the \"quoted\" you refer to?  That's not an actual branch\nname, is it?\n\nCan you try it with v1.6.5?  You might need to edit your $GIT_CONFIG,\nbut commit 5268f9edc3c86b07a64fcc2679e5ffe39be28d97 was the last\nfix for URI-escaping problems:\n\n  Author: Eric Wong <normalperson@yhbt.net>\n  Date:   Sun Aug 16 14:22:12 2009 -0700\n\n    svn: assume URLs from the command-line are URI-encoded\n    \n    And then unescape them when writing to $GIT_CONFIG.\n    \n    SVN has different rules for repository URLs (usually the root)\n    and for paths within that repository (below the HTTP layer).\n    Thus, for the request URI path at the HTTP level, the URI needs\n    to be encoded.  However, in the body of the HTTP request (the\n    with underlying SVN XML protocol), those paths should not be\n    URI-encoded[1].  For non-HTTP(S) requests, SVN appears to be\n    more flexible and will except weird characters in the URL as\n    well as URI-encoded ones.\n    \n    Since users are used to using URLs being entirely URI-encoded,\n    git svn will now attempt to unescape the path portion of URLs\n    while leaving the actual repository URL untouched.\n    \n    This change will be reflected in newly-created $GIT_CONFIG files\n    only.  This allows users to switch between svn(+ssh)://, file://\n    and http(s):// urls without changing the fetch/branches/tags\n    config keys.  This won't affect existing imports at all (since\n    things didn't work before this commit anyways), and will allow\n    users to force escaping into repository paths that look like\n    they're escaped (but are not).\n    \n    Thanks to Mike Smullin for the original bug report and Björn\n    Steinbrink for summarizing it into testable cases for me.\n    \n    [1] Except when committing copies/renames, see\n        commit 29633bb91c7bcff31ff3bb59378709e3e3ef627d\n\n\nAnd if git v1.6.5 doesn't work, would you mind looking at (and possibly\nmodifying) the t9118 test in git to reproduce since it's already got your\noddly-named branch in it?   Thanks!\n\n-- \nEric Wong\n"}]}