thanks, we´ll check that.
On 23 Sep., 12:03, tonemcd <[EMAIL PROTECTED]> wrote:
> Check your ~/.subversion/servers file. Any proxy requirements (such as
> would be in the environment variable 'http_proxy') need to be
> replicated there.
>
> ie
> ...
> ...
> [global]
> # http-proxy-exceptions = *.
Check your ~/.subversion/servers file. Any proxy requirements (such as
would be in the environment variable 'http_proxy') need to be
replicated there.
ie
...
...
[global]
# http-proxy-exceptions = *.exception.com, www.internal-site.org
http-proxy-host = yourcache.yoursite.com
http-proxy-port = 80
we have a server with about 15 customers (vhosts) - every setup is
exactly the same and usually django-updates work fine.
but, when I don´t do an update for about 6 months, it doesn´t work
anymore (it´s the third this happens now).
our system-administrator didn´t find anything.
thanks,
patrick
On 9/21/07, patrickk <[EMAIL PROTECTED]> wrote:
> when I do "svn update" within the django_src directory, I´m getting
> this error:
> svn: PROPFIND request failed on '/'
> svn: PROPFIND of '/': 200 OK (http://code.djangoproject.com)
It's working fine for me. Double-check that things are working o
we have some sites with older versions of django which I´d like to
update:
when I do "svn update" within the django_src directory, I´m getting
this error:
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 200 OK (http://code.djangoproject.com)
svn info gives me this:
Path: .
URL: http://
5 matches
Mail list logo