Re: URL problem when committing files over network

On Mon, Jun 2, 2008 at 4:23 PM, Ryan Schmidt <
subversion-2008b_at_ryandesign.com> wrote:

> On Jun 2, 2008, at 15:24, Michael Lapchuk wrote:
>
> I have subversion set up so I can access my repository over a local
>> network. I can checkout and update my working copies no problem but I run
>> into an error when I try to commit my working copies to the repository.
>> I have tried to commit my files using the following command:
>> >>> svn commit -m "comment"
>> And from this I got the following error:
>> >svn: Commit failed (details follow)
>> >svn: Authorization failed
>> I am not sure if this error is caused because I did not specify the
>> location on the other computer where the repository is actually stored or if
>> it is something else.
>>
>> I have also tried another form of the commit command:
>> >>>svn commit svn//***IP***//root/svn/repos -m "comment"
>> And from this I got the following error:
>> >svn: Can't check path 'svn:\\***IP***\root\svn\repos': The filename,
>> directory name, or volume label syntax is incorrect.
>> I have no idea what could be wrong with the path that I provided as that
>> is the same path that I use to checkout the working copy and it works to
>> check it out. Also all of the cases of the letters are the proper case
>> (lower instead of upper) so it is not a problem with case-(in)sensitivity.
>>
>
> The URL of the repository is stored within the working copy at the time
> that you check it out. It's not necessary (or possible) to specify the
> repository URL in the commit command itself.
>
> I would assume that the first error message you got is telling you the
> truth: that you aren't authorized to commit to the repository. Is
> authorization set up on the repository? What username and password are you
> logging in with, or if you did not specify a username and password when
> committing, then it's already cached in ~/.subversion/auth so check the
> appropriate file there, maybe even remove that file and commit again (which
> will now prompt you again for the username and password).
>
>
Ya I was a little stupid when I altered the svnserve.conf file to allow
anon-users to write to the repository. I removed the comment (#) but I left
in the space and that was where my problem came from. On a side note
however, do you know how long the user's credentials are cached in
~/.subversion/auth? And would that file be located on the server box or on
the client box?

--Michael

-- 
"Those who are ignorant of history are doomed to repeat it"