What did you do before the bug happened? (Steps to reproduce your issue)
I created a local SVN repository and checked out a working branch. After a few versionings in SVN, I decided to migrate to Git. Using git svn clone to clone the SVN repository to a local folder, I ran into the bug.
What did you expect to happen? (Expected behavior)
Create a folder with repo cloned
What happened instead? (Actual behavior)
Show me the message: ``` D:\_ARQUITETURA\MigracaoSvn2Git_20261001>git svn clone file:///D:/_ARQUITETURA/MigracaoSvn2Git_20261001/SvnServerSample/Projeto/Trunk/2026.4.0.0.SaaS testeGit Initialized empty Git repository in D:/_ARQUITETURA/MigracaoSvn2Git_20261001/testeGit/.git/ Can't create session: Unable to connect to a repository at URL 'file:///D:/_ARQUITETURA/MigracaoSvn2Git_20261001/SvnServerSample/Projeto/Trunk/2026.4.0.0.SaaS': Unable to open repository 'file:///D:/_ARQUITETURA/MigracaoSvn2Git_20261001/SvnServerSample/Projeto/Trunk/2026.4.0.0.SaaS' at D:/Ferramentas/Git/mingw64/share/perl5/Git/SVN.pm line 148. ```
What's different between what you expected and what actually happened?
+ Expected a git repo folder with the files of SVN - Error message and a empty git repo
Anything else you want to add: * All setup is local * Windows path url
[System Info] git version: git version 2.51.0.windows.1 cpu: x86_64 built from commit: 4d21a77b98af5cf479d8b6f863c2aa94257cd4e1 sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh feature: fsmonitor--daemon libcurl: 8.15.0 OpenSSL: OpenSSL 3.2.4 11 Feb 2025 zlib: 1.3.1 SHA-1: SHA1_DC SHA-256: SHA256_BLK default-ref-format: files default-hash: sha1 uname: Windows 10.0 19045 compiler info: gnuc: 15.2 libc info: no libc information available $SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
Atenciosamente,
Ramyres P Aquino 💼 Empresário, 👨💻Desenvolvedor e 👨🏫Professor ☎️ (62) 9 9936-3640 📍 Goiânia, GO, Brasil