# Error with git svn show-ignore: forbidden access

3 messages from 2009-09-01 to 2009-09-14. Participants: Yann Simon, Eric Wong.
Thread: https://gitlist.dev/t/20807

## Yann Simon, 2009-09-01 09:46

Subject: Error with git svn show-ignore: forbidden access
Message-ID: <551f769b0909010246u524599bcoc5b227f4a6279259@mail.gmail.com>
URL: https://gitlist.dev/e/551f769b0909010246u524599bcoc5b227f4a6279259%40mail.gmail.com

```
Hi,

with git version 1.6.4:

$ git svn show-ignore > .gitignore
RA layer request failed: Server sent unexpected return value (403
Forbidden) in response to PROPFIND request for
'/repos/XXX/YYY/ZZZ/trunk/aaa' at /usr/lib/git-core/git-svn line 2243

Is git svn show-ignore making request to the svn server?

I tried also with the --no-minimize-url option but get as answer:
$ git svn --no-minimize-url show-ignore
Unknown option: no-minimize-url

Thanks for the help

Yann

```

## Eric Wong, 2009-09-05 05:57

Subject: Re: Error with git svn show-ignore: forbidden access
Message-ID: <20090905055708.GA22272@dcvr.yhbt.net>
URL: https://gitlist.dev/e/20090905055708.GA22272%40dcvr.yhbt.net
In-Reply-To: <551f769b0909010246u524599bcoc5b227f4a6279259@mail.gmail.com>

```
Yann Simon <yann.simon.fr@gmail.com> wrote:
> Hi,
> 
> with git version 1.6.4:
> 
> $ git svn show-ignore > .gitignore
> RA layer request failed: Server sent unexpected return value (403
> Forbidden) in response to PROPFIND request for
> '/repos/XXX/YYY/ZZZ/trunk/aaa' at /usr/lib/git-core/git-svn line 2243
> 
> Is git svn show-ignore making request to the svn server?

Hi Yann,

Yes, git svn has to read the svn:ignore property remotely since it
doesn't do anything with it when it fetches.  Do you have read
permissions to /repos/XXX/YYY/ZZZ/trunk/aaa on that repo?

> I tried also with the --no-minimize-url option but get as answer:
> $ git svn --no-minimize-url show-ignore
> Unknown option: no-minimize-url
> 
> Thanks for the help

For everything besides initialization/clone, git svn reads the url in
your $GIT_CONFIG.  --minimize-url is only used for the initial setup.

You can edit it to move the URL down/up a level if you edit your
corresponding fetch/branches/tags lines:

before:

	[svn-remote "svn"]
		url = http://example.com/
		fetch = project/trunk:refs/remotes/trunk
		branches = project/branches/*:refs/remotes/*
		tags = project/tags/*:refs/remotes/tags/*

after:

	[svn-remote "svn"]
		url = http://example.com/project
		fetch = trunk:refs/remotes/trunk
		branches = branches/*:refs/remotes/*
		tags = tags/*:refs/remotes/tags/*

-- 
Eric Wong

```

## Yann Simon, 2009-09-14 07:30

Subject: Re: Error with git svn show-ignore: forbidden access
Message-ID: <551f769b0909140030l6d4c46c1r30fb8b8a4313b741@mail.gmail.com>
URL: https://gitlist.dev/e/551f769b0909140030l6d4c46c1r30fb8b8a4313b741%40mail.gmail.com
In-Reply-To: <20090905055708.GA22272@dcvr.yhbt.net>

```
Hi Eric,

2009/9/5 Eric Wong <normalperson@yhbt.net>:
> Yann Simon <yann.simon.fr@gmail.com> wrote:
>> with git version 1.6.4:
>>
>> $ git svn show-ignore > .gitignore
>> RA layer request failed: Server sent unexpected return value (403
>> Forbidden) in response to PROPFIND request for
>> '/repos/XXX/YYY/ZZZ/trunk/aaa' at /usr/lib/git-core/git-svn line 2243
>>
>> Is git svn show-ignore making request to the svn server?
>
> Yes, git svn has to read the svn:ignore property remotely since it
> doesn't do anything with it when it fetches.  Do you have read
> permissions to /repos/XXX/YYY/ZZZ/trunk/aaa on that repo?

No I do not have permissions to /repos/XXX/YYY/ZZZ/trunk/aaa.
I did some more tests and found out that git svn fetch could care with
this and checkout every folders in trunk except aaa.
Git svn fetch and git svn ignore do not have similar behavior?

> For everything besides initialization/clone, git svn reads the url in
> your $GIT_CONFIG.  --minimize-url is only used for the initial setup.
>
> You can edit it to move the URL down/up a level if you edit your
> corresponding fetch/branches/tags lines:
> [...]

I tried that and it works. Tanks a lot!

It was easy in my case because there are only 2 folders in trunk, one
I can access, and one I cannot.
But let's suppose there are x folders in 'trunk', and only one of them
cannot be accessed.
In that case, the configuration could be very complex, is not it?
But that latter configuration is probably unlikely to be used. If
someone wants to restrict access, he/she would use one folder for
every one, and one folder for restricted access.

---
Yann

```