Guten Tag Dave Steckler,
am Dienstag, 25. Juni 2013 um 00:35 schrieben Sie:
> How would one upgrade to svn 1.8.1 as it exists within TortoiseSVN?
> [...]For example, I have no idea what "serf",
> amongst all the libraries used by svn, even is.
Simply wait for the next release of TortoiseSVN or d
---
Subversion Exception!
---
Subversion遇到了一个严重的问题。
麻烦您花点时间将这个问题报告给Subversion
请尽量详细的描述您之前尝试的操作。
不过希望您先在邮件存档中搜索一下同样的问题，避免重复提交。
您可以登录下面的地址搜索邮件存档：
http://subversion.apache.org/mailing-lists.html
Subversion产生的报告如下
(您可以用Ctrl-C快捷键复制
本对话框的内容到剪切板)：
文件
“D:
How would one upgrade to svn 1.8.1 as it exists within TortoiseSVN?
That is, I simply run TortoiseSVN, check stuff in and out of my unfuddle
repository, and am deliberately and blissfully unaware of all the
machinations that happen when I right click in Explorer and choose "SVN
Commit". For exampl
0x18 is ^X, the ASCII control code for CANCEL. Seems to be working as
designed. ;-)
No more seriously though, it sure looks like a bug. 0x18 is a perfectly
legal UTF-8 encoding of the unicode character U+0018. Every US-ASCII
character is encoded as itself in UTF-8 and the first 128 Unicode code
po
On Mon, Jun 24, 2013 at 12:00 PM, Daniel Shahaf wrote:
> Branko Čibej wrote on Mon, Jun 24, 2013 at 16:32:56 +0200:
>> On 24.06.2013 11:46, Daniel Shahaf wrote:
>> > Branko Čibej wrote on Sat, Jun 22, 2013 at 18:02:32 +0200:
>> >> On 22.06.2013 17:46, Nico Kadel-Garcia wrote:
>> >>> # Canonicalize
svnsync 1.8.0 fails if there is a non-printable characters in the commit message
Error message:
svnsync: E22: Safe data 'MFC r251249, r251251, r251252, r' was followed by
non-ASCII byte 24: unable to convert to/from UTF-8
No issue with svnsync 1.7.10 (neon based)
Parts of the file (synced w
Branko Čibej wrote on Mon, Jun 24, 2013 at 16:32:56 +0200:
> On 24.06.2013 11:46, Daniel Shahaf wrote:
> > Branko Čibej wrote on Sat, Jun 22, 2013 at 18:02:32 +0200:
> >> On 22.06.2013 17:46, Nico Kadel-Garcia wrote:
> >>> # Canonicalize path to python, correctly
> >>> for name in tools/server-side
On 24.06.2013 11:46, Daniel Shahaf wrote:
> Branko Čibej wrote on Sat, Jun 22, 2013 at 18:02:32 +0200:
>> On 22.06.2013 17:46, Nico Kadel-Garcia wrote:
>>> # Canonicalize path to python, correctly
>>> for name in tools/server-side/svnpubsub/*.py; do
>>> sed -i 's|#!/usr/local/bin/python|#!/usr/
On Sun, Jun 23, 2013 at 02:46:29PM +0200, Stefan Sperling wrote:
> On Sun, Jun 23, 2013 at 04:28:25PM +0400, Lev Serebryakov wrote:
> > Hello, Lev.
> > You wrote 21 июня 2013 г., 22:08:44:
> >
> > LS> Here is way to crash subversion 1.8.0 release on FreeBSD -- try to
> > LS> update WC which is s
That is the problem here as well. We are using hosted svn from atlassian, so
this may be affecting a lot of users. Here is the output with our server name
changed:
$ curl -i -X PROPFIND https://ourserver.atlassian.net/svn/OurRepo
HTTP/1.1 401 Authorization Required
Server: nginx
Date: Mon, 24 J
Philip Martin writes:
> Is there an nginx proxy in front of Apache? I suspect this is another
> case of the proxy not supporting chunked Transfer-Encoding, coupled with
> the bug in 1.8.0 that causes the client to treat a 411 error as success.
> When this happens svn_ra_serf__fetch_node_props wi
CyberMew writes:
> Error: The PROPFIND response did not include the requested properties
>
> Just updated from latest 1.7.x to 1.8.0 on Windows 7 64bit machine. Receive
> the above error message through tortisesvn. Using svn command line doesn't
> make a difference.
>
> Happens to all my repos.
Philip Martin writes:
> If you run something like:
>
>curl -H - http://server/repository
>
> the Server line might identify the proxy.
Oops! Wrong option.
curl -I http://server/repository
or perhaps
curl -i -X PROPFIND http://server/repository
or perhaps visit
http://server/
Josh Geller writes:
> Get this message when attempting to commit either through svn command
> line (1.8.0) or TortoiseSVN 1.8.0. This is a working set that was
> upgraded from svn 1.7, and the server is a hosted svn on atlassian.net
> which is Subversion version 1.6.11 (r934486). Others are havin
Branko Čibej wrote on Sat, Jun 22, 2013 at 18:02:32 +0200:
> On 22.06.2013 17:46, Nico Kadel-Garcia wrote:
> > # Canonicalize path to python, correctly
> > for name in tools/server-side/svnpubsub/*.py; do
> > sed -i 's|#!/usr/local/bin/python|#!/usr/bin/env python|g' $name
> > done
>
> The abo
This quite resembles an issue reported last week which is intended to be
fixed in serf 1.2.2. It's possible you could upgrade just your serf
libraries, not svn as well (though, since you likely use a binary
package, just upgrading to svn 1.8.1 packages that include serf 1.2.2
might be easiest).
S
> -Original Message-
> From: Bartosz Fabianowski [mailto:free...@chillt.de]
> Sent: 23 June 2013 20:21
> To: users@subversion.apache.org
> Subject: ra_serf PROPFIND refused by Nginx
>
> Hi list,
>
> I recently switched from svn 1.7 to 1.8 and with it, from
> neon to serf.
> I am now get
17 matches
Mail list logo
