# git-svn on a strangely configured (pathwise) subversion repository 3 messages from 2007-02-12 to 2007-02-12. Participants: AJ Rossini, Eric Wong. Thread: https://gitlist.dev/t/6780 ## AJ Rossini, 2007-02-12 10:36 Subject: git-svn on a strangely configured (pathwise) subversion repository Message-ID: <200702121136.06382.blindglobe@gmail.com> URL: https://gitlist.dev/e/200702121136.06382.blindglobe%40gmail.com ``` Greetings all - (paths and names changed, but basically correct) I'm trying to use git-svn as a svn client on a repository which is not quite configured in a standard way... i.e. $ git svn fetch RA layer request failed: PROPFIND request failed on '/path/to': PROPFIND of '/path/to': 403 Forbidden (https://dummy-host-name.com) at /usr/bin/git-svn line 2861 where as from my working svn copy (no problems from svn, of course, sigh...), I'm getting: $ svn info Path: . URL: https://dummy-host-name.com/path/to/projects/project Repository Root: https://dummy-host-name.com/path/to Repository UUID: 97840717-62f2-0310-bead-daafb7b60902 Revision: 554 Node Kind: directory Schedule: normal Last Changed Author: someone Last Changed Rev: 514 Last Changed Date: 2007-01-25 14:20:44 +0100 (Thu, 25 Jan 2007) The problem seems to be that the Repository Root directory is not readable, while the URL is (at least for me, using HTTPS). This is using $ git --version git version 1.4.4.4 (on debian unstable). Here is what I'm considering: #1 - upgrading to the 1.5.0 RC series #2 - trying Eric Wong's git-svn branch at http://git.bogomips.org/git-svn.git #3 - getting a dump of the repository from the owner, loading it into a local svn server, and doing a local conversion... With respect to #1/#2, I'm a bit cautious with upgrading to something not rock solid (let's just say that except for this, git 1.4.4.4 has been excellent for my needs...). With respect to #3 - I'd prefer not to waste the admin's (personal) time if not necessary! Does any one have any thoughts? best, -tony blindglobe@gmail.com Muttenz, Switzerland. "Commit early,commit often, and commit in a repository from which we can easily roll-back your mistakes" (AJR, 4Jan05). ``` ## Eric Wong, 2007-02-12 18:32 Subject: Re: git-svn on a strangely configured (pathwise) subversion repository Message-ID: <20070212183202.GB21413@localdomain> URL: https://gitlist.dev/e/20070212183202.GB21413%40localdomain In-Reply-To: <200702121136.06382.blindglobe@gmail.com> ``` AJ Rossini wrote: > Greetings all - > > (paths and names changed, but basically correct) > > I'm trying to use git-svn as a svn client on a repository which is not > quite configured in a standard way... i.e. Perfectly standard on some corporate networks, unfortunately :( > $ git svn fetch > RA layer request failed: PROPFIND request failed on '/path/to': PROPFIND > of '/path/to': 403 Forbidden (https://dummy-host-name.com) > at /usr/bin/git-svn line 2861 > The problem seems to be that the Repository Root directory is not > readable, while the URL is (at least for me, using HTTPS). > > This is using > $ git --version > git version 1.4.4.4 Known problem. This is fixed in commit 747fa12cef73b6ca04fffaddaad7326cf546cdea > Here is what I'm considering: > #1 - upgrading to the 1.5.0 RC series Stop after #1 if you want a sure thing the current 1.5.0 RC series contains fixes for repositories with only partial read permissions. > #2 - trying Eric Wong's git-svn branch at > http://git.bogomips.org/git-svn.git Read access in your case *should* continue to work here. More testing would be good. This branch may not work well if your write access is not the same as as your read access; which is something I keep forgetting to fix... > #3 - getting a dump of the repository from the owner, loading it into > a local svn server, and doing a local conversion... > > With respect to #1/#2, I'm a bit cautious with upgrading to something > not rock solid (let's just say that except for this, git 1.4.4.4 has > been excellent for my needs...). > > With respect to #3 - I'd prefer not to waste the admin's (personal) > time if #3 is definitely not necessary. Junio has done a wonderful job of keeping the 1.5.0-rc* series stable and usable, so #1 is the safest. I'll try to fix things today so #2 will work better. -- Eric Wong ``` ## AJ Rossini, 2007-02-12 18:47 Subject: Re: git-svn on a strangely configured (pathwise) subversion repository Message-ID: <200702121947.59154.blindglobe@gmail.com> URL: https://gitlist.dev/e/200702121947.59154.blindglobe%40gmail.com In-Reply-To: <20070212183202.GB21413@localdomain> ``` On Monday 12 February 2007 19:32, Eric Wong wrote: > AJ Rossini wrote: > > Greetings all - > > > > (paths and names changed, but basically correct) > > > > I'm trying to use git-svn as a svn client on a repository which is not > > quite configured in a standard way... i.e. > > Perfectly standard on some corporate networks, unfortunately :( > > > $ git svn fetch > > RA layer request failed: PROPFIND request failed on '/path/to': PROPFIND > > of '/path/to': 403 Forbidden (https://dummy-host-name.com) > > at /usr/bin/git-svn line 2861 > > > > > The problem seems to be that the Repository Root directory is not > > readable, while the URL is (at least for me, using HTTPS). > > > > This is using > > $ git --version > > git version 1.4.4.4 > > Known problem. This is fixed in commit > 747fa12cef73b6ca04fffaddaad7326cf546cdea > > > Here is what I'm considering: > > #1 - upgrading to the 1.5.0 RC series > > Stop after #1 if you want a sure thing the current 1.5.0 RC series > contains fixes for repositories with only partial read permissions. Bingo! Thanks, Eric! Drop by for a beverage of your choice the next time you pass through Basel, Switzerland.... > > #2 - trying Eric Wong's git-svn branch at > > http://git.bogomips.org/git-svn.git > > Read access in your case *should* continue to work here. More testing > would be good. This branch may not work well if your write access is > not the same as as your read access; which is something I keep > forgetting to fix... I'll try this in a dummy directory and try to report back in the hopefully near future... best, -tony blindglobe@gmail.com Muttenz, Switzerland. "Commit early,commit often, and commit in a repository from which we can easily roll-back your mistakes" (AJR, 4Jan05). ```