On 22.11.2018 17:39, Nico Kadel-Garcia wrote: > On Wed, Nov 21, 2018 at 9:54 AM Branko Čibej <br...@apache.org> wrote: >> On 21.11.2018 15:23, Thorsten Schöning wrote: >>> Guten Tag Branko Čibej, >>> am Donnerstag, 15. November 2018 um 18:21 schrieben Sie: >>> >>>> Has there been any further update from them on this issue? >>> News: >>> >>>> Thanks for following up. Our engineers have been able to reproduce >>>> the error on our CI system and are working on a fix. >>>> This issue is already a focus for our SVN team. However people who >>>> are experiencing this issue can feel free to write in to >>>> supp...@github.com to report their own experience and we'll also let >>>> them know when the issue is fixed. >> >> Oh, that's nice. >> >> -- Brane > Can this be entirely sidestepped by using svn+ssh:// access instead of > HTTPS:// ? I'm not currently using any Subversion based access to > github, but it might provide a short-term workaround if it's > supported.
Only if GitHub provides that service. I doubt they do -- they're not converting Git repositores to Subversion repositories, they're emulating a Subversion HTTP server that gets information directly from git repositories plus (presumably) some additional data to maintain stable commit-id->revision mappings. To support svn+ssh:// they'd have to emulate a second Subversion protocol. -- Brane P.S.: Clearly, the cause of the issue discussed in this thread is that the emulation is incomplete.
