Why Can't I Commit My Changes to the Subversion Server Using 'git svn' from OS X's Terminal?

[Bryce Glover]

I keep getting the following error message when I try to commit to the SVN repository using 'git svn' from Terminal:  

ERROR from SVN:

URL access forbidden for unknown reason: Access to '/public/fltk/fltk/!svn/me' forbidden

W: 7d7949557bdf8725e8db8ec74e59ab2b0ebdd19a and refs/remotes/git-svn differ, using rebase -v --merge:

:040000 040000 ef7af311ce09bd5697e005ecc2c9d36d08cdd8ee 7fd6d5bb7c5658c6c4a4401dc8fb0d1ef11806e9 M ide

Current branch master is up to date.

ERROR: Not all changes have been committed into SVN, however the committed

ones (if any) seem to be successfully integrated into the working tree.

Please see the above messages for details.

What's going on?  

[Greg Ercolano]

On 07/30/14 18:41, Bryce Glover wrote:
> I keep getting the following error message when I try to commit to the SVN repository using 'git svn' from Terminal:
> ERROR from SVN:
> URL access forbidden for unknown reason: Access to '/public/fltk/fltk/!svn/me' forbidden

Public access is read only.
Only FLTK developers have commit access.

If you'd like to submit code changes to FLTK, you can submit patches
using an RFE (Request For Enhancement) in the STR form:
http://www.fltk.org/str.php?U+P0+S-2+C0+I0+E0+Q

[MacArthur, Ian (Selex ES, UK)]

> I keep getting the following error message when I try to commit to the
> SVN repository using 'git svn' from Terminal:

> ERROR from SVN:
> URL access forbidden for unknown reason: Access to
> '/public/fltk/fltk/!svn/me' forbidden

That's the answer, right there....


> What's going on?

You do not have commit rights on the server, so you can not write to it; you can read from it of course.

Did you think that you had commit rights?

If not, but you need them, you can apply for them.

But in the meantime, posting any changes as STR's and engaging the active devs in discussions about them will help get changes in, and also makes it substantially more likely that a subsequent request for commit access will be favourably viewed.

However, note that svn is not git, and the fltk servers are not github; if you are running experimental branches, you can not store those on the fltk servers, you store them locally.

Note that the core server is "sacrosanct"; we do not (we hope!) commit any experimental patches, nor any patches that introduce regressions, or are incompatible across host platforms.

As a result, write access to the core is somewhat constrained.

You can of course do whatever you like in your own copies, and that's a good way to do testing and to generate patches...

In the meantime, if you have patches; post the STR's and engage the active devs, to see if they are suitable for adding into the core.







Selex ES Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

[Bryce Glover]

On Thursday, July 31, 2014 5:17:55 AM UTC-4, MacArthur, Ian (Selex ES, UK) wrote:

> I keep getting the following error message when I try to commit to the
> SVN repository using 'git svn' from Terminal:  

> ERROR from SVN:
> URL access forbidden for unknown reason: Access to
> '/public/fltk/fltk/!svn/me' forbidden

That's the answer, right there....

Actually, 'URL access forbidden for unknown reason' is kind of an obscure error, don't you think?   

> What's going on?

You do not have commit rights on the server, so you can not write to it; you can read from it of course.

Did you think that you had commit rights?

Well, since I could read the repository, I assumed that I could write to it.   

If not, but you need them, you can apply for them.

But in the meantime, posting any changes as STR's and engaging the active devs in discussions about them will help get changes in, and also makes it substantially more likely that a subsequent request for commit access will be favourably viewed.

What's an 'STR?'  

However, note that svn is not git, and the fltk servers are not github; if you are running experimental branches, you can not store those on the fltk servers, you store them locally.

I know that you guys are using Subversion, so I'm using 'git svn' to fetch from your guys's repository.   

Note that the core server is "sacrosanct"; we do not (we hope!) commit any experimental patches, nor any patches that introduce regressions, or are incompatible across host platforms.

As a result, write access to the core is somewhat constrained.

You can of course do whatever you like in your own copies, and that's a good way to do testing and to generate patches...

In the meantime, if you have patches; post the STR's and engage the active devs, to see if they are suitable for adding into the core.

Ah, I see. Well, then; I guess I'll just have to file a bug report and ask for the devs to add support for Xcode 5 (and maybe even Xcode 6 for when it comes out while they're at it) to FLTK.  In the meantime, I'll keep an Xcode 5 project file down here on my end.  

[Alvin Beach]

On 31/07/14 18:57, Bryce Glover wrote:
> But in the meantime, posting any changes as STR's and engaging the active devs in discussions
> about them will help get changes in, and also makes it substantially more likely that a
> subsequent request for commit access will be favourably viewed.
>
>
> What's an 'STR?'

To me (I'm just a FLTK user not a dev), STR means Software Test Report. FLTK uses them to track bug
and feature requests. FLTK uses a custom bug tracking system.

Before you can submit a report, you need to create an account:

http://www.fltk.org/login.php


Once you have an account, go to the FLTK main page. There you will see "Bugs & Features" at the
top-centre. Click on "Submit Bug or Feature Request" just below "Bugs & Features". That will take
you to where you can submit a report (and add attachments). If you haven't logged in, you will be
given a chance to do so before continuing on to the STR submission form.

Cheers,

Alvin