Em qui., 20 de jun. de 2024 às 16:15, Daniel Sahlberg
escreveu:
>
> Have you seen the FAQ item about reverse proxies:
Yes, I have.
> I have absolutely no experience with Nginx but this seems to set the
> Destination header, much like the examples in the FAQ for IIS. But it seems
> it keep the
I have a Subversion vesion 1.14.1 running behind a reverse proxy
implemented by nginx version 1.18.0 on a Ubuntu 22.04 server.
I'm having problems renaming files in it. I came up with the following
procedure to reproduce the problem:
> $ export LANG=C.UTF-8
> $ export LANGUAGE=en
> $ REPO=https:/
I got a "segmentation fault" while performing a "svn resolve" to resolve a
conflict in a file with the svn:mime-type property set to
application/octet-stream. I got the same error using the WANdisco packages
for svn-1.9.4 at RHEL and using Ubuntu 16.04 native package for svn-1.9.3.
I was able to r
2015-08-22 21:22 GMT-03:00 :
> Can you confirm that the file is locked after the command? (E.g. by
> running svn status on the target)
>
> Does it lock the file when the hook blocks it… or does ‘svn lock’ return
> success?
>
No, it doesn't.
Look at these comnands, using svn 1.9, first without a h
Hi there,
It seems that svn 1.9 changed the behaviour of the "svn lock" and the "svn
unlock" commands with regards to the fate of the corresponding
pre-lock/pre-unlock hooks.
Up to svn 1.8, when those hooks failed (exit code != 0) the commands (svn
lock/unlock) failed too.
Now, on svn 1.9, the c
On 5 dez, 09:13, Philip Martin wrote:
> Your problem with POST requests is not yet understood. It's might be
> some overlap between Subversion directives in your apache config, or
> between Subversion directives and non-Subversion directives. Only you
> can really identify the problem at presen
On 5 dez, 05:59, Konstantin Kolinko wrote:
> 2011/12/4 Gustavo Chaves :
>
> There are known problems with handling of POST requests in 1.7.0 an 1.7.1.
>
> In 1.7.2 changes list that is mentioned as
> * make mod_dav_svn ignore non-Subversion POST requests (r1187695)
>
> T
Just one more information. I was using the packages
CollabNetSubversion-extras and CollabNetSubversion-server version
1.7.0-2. I've just upgrade them to version 1.7.1-1 but the problems
remain.
--
Gustavo.
I straced the httpd daemon to try to get any hint. The last syscalls
before the error are these:
17748 read(18, "POST /admin/!svn/me HTTP/1.1\r\nUs"..., 8000) = 441
17748 stat("/l/home1/svn/admin/htdocs/admin/!svn/me", 0x7fffce99c130)
= -1 ENOENT (No such file or directory)
17748 lstat("/l", {st_m
On 1 dez, 22:29, Mark Phippard wrote:
>
> Subversion Edge does not have the location block for SVN in the
> httpd.conf file. Have you customized the configuration files beyond
> this? There is no reason you should have to add that directive
> anyway.
>
> Assuming you are using the default config
10 matches
Mail list logo
