On 14/04/2008, Frank Warmerdam <warmerdam@pobox.com> wrote:
Yann Chemin wrote:
> Hi,
>
> While doing a couple of updates this afternoon, suddenly svn refused
updates,
> saying this:
>
> # svn ci -m "fix bug"
> svn: Commit failed (details follow):
> svn: Unrecognized URL scheme for
> 'https://svn.osgeo.org/grass/grass-addons/gipe/r.out.vic’
>
> Anybody could check the server please?
>
Yann,
Is this still a problem for you? Have you heard if it happens to others
too?
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam,
warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
I just tried a commit in this area and it seems to work fine. I suspect
your svn client does not support https (compiled without it), though I
can't think of any reason this would have recently changed.
I did:
warmerda@gdal64[26]% svn checkout https://svn.osgeo.org/grass/grass-addons/gipe/
r.out.vic
A r.out.vic/main.c
A r.out.vic/description.html
A r.out.vic/veg_lib.c
A r.out.vic/Makefile
Checked out revision 30991.
warmerda@gdal64[27]% ls
r.out.vic
warmerda@gdal64[28]% cd r.out.vic/
warmerda@gdal64[29]% ls
description.html main.c Makefile veg_lib.c
warmerda@gdal64[30]% svn status
warmerda@gdal64[31]% vi Makefile
warmerda@gdal64[32]% svn status
M Makefile
warmerda@gdal64[33]% svn commit -m "test commit" Makefile
Authentication realm: <https://svn.osgeo.org:443> GRASS Subversion Repository
Password for 'warmerda':
Authentication realm: <https://svn.osgeo.org:443> GRASS Subversion Repository
Username: warmerdam
Password for 'warmerdam':
Sending Makefile
Transmitting file data .
Committed revision 30992.
Forgive me for the rather pointless commit.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
if I put a typo in the addons dir structure I get the error:
svn: URL '.../grass/grass-addon/...' doesn't exist
if I put a typo in the project name I the less helpful error:
svn: PROPFIND request failed on '/gras/grass-addons/...'
svn: PROPFIND of '/gras/grass-addons/...': 405 Method Not Allowed
(https://svn.osgeo.org)
maybe try the checkin with full path and filename from the grass-addons
"root" dir? try with a fresh checkout?
if I put a typo in the addons dir structure I get the error:
svn: URL '.../grass/grass-addon/...' doesn't exist
if I put a typo in the project name I the less helpful error:
svn: PROPFIND request failed on '/gras/grass-addons/...'
svn: PROPFIND of '/gras/grass-addons/...': 405 Method Not Allowed
(https://svn.osgeo.org)
maybe try the checkin with full path and filename from the grass-addons
"root" dir? try with a fresh checkout?
I suppose that svn got allergic to https as you suggested, but I did
not see that subversion got upgraded recently in my box... Definitely
not while I was working.
Still not clear...
On 15/04/2008, Frank Warmerdam <warmerdam@pobox.com> wrote:
Yann Chemin wrote:
> Hi,
>
> just woke up,
> yes still a problem. Same problem.
>
...
I just tried a commit in this area and it seems to work fine. I suspect
your svn client does not support https (compiled without it), though I
can't think of any reason this would have recently changed.
I did:
warmerda@gdal64[26]% svn checkout https://svn.osgeo.org/grass/grass-addons/gipe/
r.out.vic
A r.out.vic/main.c
A r.out.vic/description.html
A r.out.vic/veg_lib.c
A r.out.vic/Makefile
Checked out revision 30991.
warmerda@gdal64[27]% ls
r.out.vic
warmerda@gdal64[28]% cd r.out.vic/
warmerda@gdal64[29]% ls
description.html main.c Makefile veg_lib.c
warmerda@gdal64[30]% svn status
warmerda@gdal64[31]% vi Makefile
warmerda@gdal64[32]% svn status
M Makefile
warmerda@gdal64[33]% svn commit -m "test commit" Makefile
Authentication realm: <https://svn.osgeo.org:443> GRASS Subversion
Repository
Password for 'warmerda':
Authentication realm: <https://svn.osgeo.org:443> GRASS Subversion
Repository
Username: warmerdam
Password for 'warmerdam':
Sending Makefile
Transmitting file data .
Committed revision 30992.
Forgive me for the rather pointless commit.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam,
warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
If you just use svn diff on a local file or directory, it just
compares the working copy with the local original copy, so network
access doesn't come into it.
I suppose that svn got allergic to https as you suggested, but I did
not see that subversion got upgraded recently in my box... Definitely
not while I was working.
Note that the svn libraries rely upon the Neon library for HTTP/WebDAV
access, which in turn relies upon OpenSSL for SSL.
It's possible that the problem could be caused by an update to either
of those libraries, or a configuration change for OpenSSL (Neon
doesn't appear to have any configuration).
that must be something in this line that happened,
I do not record all the time if such software gets upgraded.
I'll check that up after work today,
Thanks for the help !
Yann
On 15/04/2008, Glynn Clements <glynn@gclements.plus.com> wrote:
Yann Chemin wrote:
> I tried a fresh check out and it seems that it runs into the same problem...
>
> # svn co https://svn.osgeo.org/grass/grass-addons/
> svn: Unrecognized URL scheme for 'https://svn.osgeo.org/grass/grass-addons’
> #
>
> I suppose that svn got allergic to https as you suggested, but I did
> not see that subversion got upgraded recently in my box... Definitely
> not while I was working.
Note that the svn libraries rely upon the Neon library for HTTP/WebDAV
access, which in turn relies upon OpenSSL for SSL.
It's possible that the problem could be caused by an update to either
of those libraries, or a configuration change for OpenSSL (Neon
doesn't appear to have any configuration).