On 1/3/06, Ximon Eighteen <email@example.com> wrote:
> Ignacio Parra wrote:
> > Hi,
> > I need to acces a svnserve that is listening on other port than the
> > Until yesterday, the server was listening on the 3690, and the
> > was working correctly, but the IT people has installed a firewall on the
> > server, and the only port available to this server is not the original
> > When I tried to connect to the server directly, the repo-browser gets
> > perfectly the new url (svn://fisico:8000/SQL) and coneects to the
> > but when I change the entries file on the .svn folder to view this
> change on
> > a checkedout folder, it appears the next error:
> > Error: Commit failed (details follow):
> > Error: Unrecognized URL scheme for ''
> > Looks like that the commit subcommand does not understand the new port.
> > can I make this works?
> > The server is on a win xp sp2, svn version 1.2.3. The client is also a
> > xp sp2, svn version 1.2.3.
> > I will appreciate very much any help that you can offer me.
> I'm guessing here but I imagine that the repo-browser uses the svn ls
> command which does not involve a working copy but that commit uses the
> working copy which is why you see different behaviour.
> Furthermore I suggest that you might need to "relocate" your working
> copy because the URL to your repository has changed (it now contains
> :8000 and presume that before it did not).
> Using TortoiseSVN a "relocate" can be performed like this:
> 1. In Windows Explorer right click on the folder that is your working
> 2. In the popup menu that appears click the submenu TortoiseSVN.
> 3. In the sub popup menu that appears click "Relocate...".
> 4. In the "To URL" field change the URL so that the first part that
> changed when you changed ports is changed. I'm guessing again but I
> guess before the firewall change you had something like this:-
> And now you have something like this:-
> So in the "To URL" field add in the missing ":8000" and hit OK.
This has solved my problem. Next time I will read the entire tortoiseSVN
help file instead of searching the question that I think that describes the
Thanks a lot Ximon,
Received on Tue Jan 3 21:30:00 2006