{"thread":{"id":"6780","subject":"git-svn on a strangely configured (pathwise) subversion repository","startedAt":"2007-02-12T10:36:00Z","lastAt":"2007-02-12T18:47:52Z","messageCount":3,"participants":["AJ Rossini","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"34270","messageId":"200702121136.06382.blindglobe@gmail.com","threadId":"6780","inReplyTo":null,"subject":"git-svn on a strangely configured (pathwise) subversion repository","fromName":"AJ Rossini","fromEmail":"blindglobe@gmail.com","sentAt":"2007-02-12T10:36:00Z","receivedAt":"2007-02-12T10:36:00Z","isPatch":false,"sender":{"key":"blindglobe@gmail.com","avatar":"https://gravatar.com/avatar/d9ce41197180da6d03ab12a6c3e9ff8a030b1677bca88ad65458c2f5566d8550?d=mp&s=160"},"body":"Greetings all -\n\n(paths and names changed, but basically correct)\n\nI'm trying to use git-svn as a svn client on a repository which is not quite \nconfigured in a standard way... i.e. \n\n$ git svn fetch \nRA layer request failed: PROPFIND request failed on '/path/to': PROPFIND \nof '/path/to': 403 Forbidden (https://dummy-host-name.com) \nat /usr/bin/git-svn line 2861\n\n\nwhere as from my working svn copy (no problems from svn, of course, sigh...), \nI'm getting:\n\n$ svn info \nPath: .\nURL: https://dummy-host-name.com/path/to/projects/project\nRepository Root: https://dummy-host-name.com/path/to\nRepository UUID: 97840717-62f2-0310-bead-daafb7b60902\nRevision: 554\nNode Kind: directory\nSchedule: normal\nLast Changed Author: someone\nLast Changed Rev: 514\nLast Changed Date: 2007-01-25 14:20:44 +0100 (Thu, 25 Jan 2007)\n\nThe problem seems to be that the Repository Root directory is not readable, \nwhile the URL is (at least for me, using HTTPS).\n\nThis is using\n$ git --version \ngit version 1.4.4.4\n\n(on debian unstable).\n\nHere is what I'm considering: \n#1 - upgrading to the 1.5.0 RC series\n#2 - trying Eric Wong's git-svn branch at http://git.bogomips.org/git-svn.git\n#3 - getting a dump of the repository from the owner, loading it into a local \nsvn server, and doing a local conversion...\n\nWith respect to #1/#2, I'm a bit cautious with upgrading to something not rock \nsolid (let's just say that except for this, git 1.4.4.4 has been excellent \nfor my needs...).\n\nWith respect to #3 - I'd prefer not to waste the admin's (personal) time if \nnot necessary!\n\nDoes any one have any thoughts? \n\nbest,\n-tony\n\nblindglobe@gmail.com\nMuttenz, Switzerland.\n\"Commit early,commit often, and commit in a repository from which we can \neasily roll-back your mistakes\" (AJR, 4Jan05).\n"},{"id":"34304","messageId":"20070212183202.GB21413@localdomain","threadId":"6780","inReplyTo":"200702121136.06382.blindglobe@gmail.com","subject":"Re: git-svn on a strangely configured (pathwise) subversion repository","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2007-02-12T18:32:02Z","receivedAt":"2007-02-12T18:32:02Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"AJ Rossini wrote:\n> Greetings all -\n> \n> (paths and names changed, but basically correct)\n> \n> I'm trying to use git-svn as a svn client on a repository which is not\n> quite configured in a standard way... i.e. \n\nPerfectly standard on some corporate networks, unfortunately :(\n\n> $ git svn fetch\n> RA layer request failed: PROPFIND request failed on '/path/to': PROPFIND \n> of '/path/to': 403 Forbidden (https://dummy-host-name.com) \n> at /usr/bin/git-svn line 2861\n\n\n\n> The problem seems to be that the Repository Root directory is not\n> readable, while the URL is (at least for me, using HTTPS).\n> \n> This is using\n> $ git --version\n> git version 1.4.4.4\n\nKnown problem. This is fixed in commit\n747fa12cef73b6ca04fffaddaad7326cf546cdea\n\n> Here is what I'm considering: \n> #1 - upgrading to the 1.5.0 RC series\n\nStop after #1 if you want a sure thing the current 1.5.0 RC series\ncontains fixes for repositories with only partial read permissions.\n\n> #2 - trying Eric Wong's git-svn branch at\n> http://git.bogomips.org/git-svn.git\n\nRead access in your case *should* continue to work here. More testing\nwould be good. This branch may not work well if your write access is\nnot the same as as your read access; which is something I keep\nforgetting to fix...\n\n> #3 - getting a dump of the repository from the owner, loading it into\n> a local svn server, and doing a local conversion...\n> \n> With respect to #1/#2, I'm a bit cautious with upgrading to something\n> not rock solid (let's just say that except for this, git 1.4.4.4 has\n> been excellent for my needs...).\n> \n> With respect to #3 - I'd prefer not to waste the admin's (personal)\n> time if \n\n#3 is definitely not necessary.\n\nJunio has done a wonderful job of keeping the 1.5.0-rc* series stable\nand usable, so #1 is the safest. I'll try to fix things today so #2\nwill work better.\n\n-- \nEric Wong\n"},{"id":"34305","messageId":"200702121947.59154.blindglobe@gmail.com","threadId":"6780","inReplyTo":"20070212183202.GB21413@localdomain","subject":"Re: git-svn on a strangely configured (pathwise) subversion repository","fromName":"AJ Rossini","fromEmail":"blindglobe@gmail.com","sentAt":"2007-02-12T18:47:52Z","receivedAt":"2007-02-12T18:47:52Z","isPatch":false,"sender":{"key":"blindglobe@gmail.com","avatar":"https://gravatar.com/avatar/d9ce41197180da6d03ab12a6c3e9ff8a030b1677bca88ad65458c2f5566d8550?d=mp&s=160"},"body":"On Monday 12 February 2007 19:32, Eric Wong wrote:\n> AJ Rossini wrote:\n> > Greetings all -\n> >\n> > (paths and names changed, but basically correct)\n> >\n> > I'm trying to use git-svn as a svn client on a repository which is not\n> > quite configured in a standard way... i.e.\n>\n> Perfectly standard on some corporate networks, unfortunately :(\n>\n> > $ git svn fetch\n> > RA layer request failed: PROPFIND request failed on '/path/to': PROPFIND\n> > of '/path/to': 403 Forbidden (https://dummy-host-name.com)\n> > at /usr/bin/git-svn line 2861\n>\n> \n>\n> > The problem seems to be that the Repository Root directory is not\n> > readable, while the URL is (at least for me, using HTTPS).\n> >\n> > This is using\n> > $ git --version\n> > git version 1.4.4.4\n>\n> Known problem. This is fixed in commit\n> 747fa12cef73b6ca04fffaddaad7326cf546cdea\n>\n> > Here is what I'm considering:\n> > #1 - upgrading to the 1.5.0 RC series\n>\n> Stop after #1 if you want a sure thing the current 1.5.0 RC series\n> contains fixes for repositories with only partial read permissions.\n\nBingo! Thanks, Eric! Drop by for a beverage of your choice the next time \nyou pass through Basel, Switzerland....\n\n> > #2 - trying Eric Wong's git-svn branch at\n> > http://git.bogomips.org/git-svn.git\n>\n> Read access in your case *should* continue to work here. More testing\n> would be good. This branch may not work well if your write access is\n> not the same as as your read access; which is something I keep\n> forgetting to fix...\n \nI'll try this in a dummy directory and try to report back in the hopefully \nnear future...\n\nbest,\n-tony\n\nblindglobe@gmail.com\nMuttenz, Switzerland.\n\"Commit early,commit often, and commit in a repository from which we can \neasily\nroll-back your mistakes\" (AJR, 4Jan05).\n"}]}