Den mån 15 aug. 2022 kl 12:00 skrev Nelskamp-Lukas, Carsten <
c.nelskamp-lu...@prosoz.de>:
> Hello,
>
>
>
> steps to reproduce the issue:
>
>
>
> Given a repository file "PARKMB.csv" with content:
>
> 5
>
> 7
>
> 9
>
> [eof]
>
>
>
> and a patch file "patch.patch" with content:
>
> Index: PARKMB.cs
On Thu, Nov 28, 2019 at 5:11 AM Lukas .. wrote:
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
>
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list
On 2018-08-03 12:46, Daniel Shahaf wrote:
Folker Schamel wrote on Thu, 02 Aug 2018 15:34 +0200:
On 2018-08-01 19:19, Daniel Shahaf wrote:
Folker Schamel wrote on Wed, 01 Aug 2018 17:51 +0200:
Hi Julian,
Draft which may save you some time:
First patch against trunk:
[[[
* site/staging/faq.htm
Folker Schamel wrote on Thu, 02 Aug 2018 15:34 +0200:
> On 2018-08-01 19:19, Daniel Shahaf wrote:
> > Folker Schamel wrote on Wed, 01 Aug 2018 17:51 +0200:
> >> Hi Julian,
> >>
> >> Draft which may save you some time:
> >>
> >> First patch against trunk:
> >> [[[
> >> * site/staging/faq.html:
> >>
Folker Schamel wrote:
> Daniel Shahaf wrote:
>> Folker Schamel wrote:
>>> * site/staging/faq.html:
>>>Add entry for "An error occurred during SSL communication" error.
>>> * site/staging/docs/release-notes/1.10.html:
>>>Add entry for an OpenSSL upgrade causing "An error occurred during
>>
On 2018-08-01 19:19, Daniel Shahaf wrote:
Folker Schamel wrote on Wed, 01 Aug 2018 17:51 +0200:
Hi Julian,
Draft which may save you some time:
First patch against trunk:
[[[
* site/staging/faq.html:
Add entry for "An error occurred during SSL communication" error.
]]]
Second patch against
Folker Schamel wrote on Wed, 01 Aug 2018 17:51 +0200:
> Hi Julian,
>
> Draft which may save you some time:
>
> First patch against trunk:
> [[[
> * site/staging/faq.html:
>Add entry for "An error occurred during SSL communication" error.
> ]]]
>
> Second patch against trunk:
> [[[
> * site/s
Hi Julian,
Draft which may save you some time:
First patch against trunk:
[[[
* site/staging/faq.html:
Add entry for "An error occurred during SSL communication" error.
]]]
Second patch against trunk:
[[[
* site/staging/docs/release-notes/1.10.html:
Add entry for an OpenSSL upgrade causing
Folker Schamel wrote:
> Hi Stefan,
>> That's the catch here. Subversion does not ship with OpenSSL by
>> itself. From Subversion's point of view this is a 3rd-party
>> dependency. [...] It could be something worthwhile adding to the FAQ
>> however, though then in a more general manner like: Trouble
Hi Stefan,
That's the catch here. Subversion does not ship with OpenSSL by
itself. From Subversion's point of view this is a 3rd-party
dependency. You can easily build Subversion 1.9.x/1.10.x with OpenSSL
1.0.x. Whether or not you run into this issue therefore is outside the
scope of Subversio
On 8/1/2018 9:25 AM, Folker Schamel wrote:
On 2018-07-31 21:09, Philip Martin wrote:
Daniel Shahaf writes:
Subversion uses Serf, which uses OpenSSL, which talks to an SSL implementation
on the server. The root cause of the error is known to the SSL implementation
on the server (that's why yo
On 2018-07-31 21:09, Philip Martin wrote:
Daniel Shahaf writes:
Subversion uses Serf, which uses OpenSSL, which talks to an SSL implementation
on the server. The root cause of the error is known to the SSL implementation
on the server (that's why you see it in the error log). It's not obviou
Daniel Shahaf writes:
> Subversion uses Serf, which uses OpenSSL, which talks to an SSL implementation
> on the server. The root cause of the error is known to the SSL implementation
> on the server (that's why you see it in the error log). It's not obvious that
> OpenSSL on the client side eve
Folker Schamel wrote on Tue, Jul 31, 2018 at 17:42:10 +0200:
> On 2018-07-31 17:04, Philip Martin wrote:
> > Folker Schamel writes:
> > > For the broken setup, the client reports:
> > > svn: E120171: Error running context: An error occurred during SSL
> > > communication
> > > And the server Apac
Hi Philip,
this solved it!
Using "openssl s_client" as you described it reported:
error setting certificate
140258270184704:error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca
md too weak:../ssl/ssl_rsa.c:303:
So we created new certificates with sha256 (default in openssl 1.1)
instead of md
Folker Schamel writes:
> After upgrading, Subversion SSL connections with "SSLVerifyClient
> require" seem to be broken.
>
> Broken: SVN Client 1.9.5, Serf 1.3.9-3, Server "SSLVerifyClient require"
> Works: SVN Client 1.9.5, Serf 1.3.9-3, Server "SSLVerifyClient off"
> Works: SVN Client 1.9.5,
Hello everyone,
After upgrading, Subversion SSL connections with "SSLVerifyClient
require" seem to be broken.
Broken: SVN Client 1.9.5, Serf 1.3.9-3, Server "SSLVerifyClient require"
Works: SVN Client 1.9.5, Serf 1.3.9-3, Server "SSLVerifyClient off"
Works: SVN Client 1.9.5, Serf 1.3.8-1, Se
On Fri, Sep 20, 2013 at 08:31:26AM +0200, David Zhang wrote:
> Hello SVN Developers!
>
> I believe i have found a bug in the svn command line client.
>
> I am using Windows 7 OS with this svn client:
>
> D:\> svn --version
> svn, Version 1.8.3-SlikSvn-1.8.3-X64 (SlikSvn/1.8.3) X64
>übersetzt
Hello SVN Developers!
I believe i have found a bug in the svn command line client.
I am using Windows 7 OS with this svn client:
D:\> svn --version
svn, Version 1.8.3-SlikSvn-1.8.3-X64 (SlikSvn/1.8.3) X64
übersetzt am Sep 4 2013, um 16:04:02 auf
x86_64/x86-microsoft-windows6.1.7601
When i r
[David Dyer-Bennet]
> as I said in my initial post, I first discovered this on Windows
> under Cygwin. Avoiding "c:/Program Files" and "c:/Documents and
> Settings/david.dyer-bennet/My Documents" involves contortions and
> leaves you putting things in unusual places.
Well, or calling them C:/PRO
David Dyer-Bennet wrote on Tue, Dec 07, 2010 at 09:30:45 -0600:
> On Tue, December 7, 2010 09:03, Daniel Shahaf wrote:
> > David Dyer-Bennet wrote on Tue, Dec 07, 2010 at 08:44:28 -0600:
> >> And, in any case, VISUAL is a public interface, and I wonder how many
> >> other applications would break i
On Tue, December 7, 2010 09:03, Daniel Shahaf wrote:
> David Dyer-Bennet wrote on Tue, Dec 07, 2010 at 08:44:28 -0600:
>> On Tue, December 7, 2010 04:18, Julian Foad wrote:
>> > On Tue, 2010-12-07, Daniel Shahaf wrote:
>> >> I suppose setting VISUAL="\"/path with spaces/to/editor/binary\"" is
>> t
[David Dyer-Bennet]
> >> I suppose setting VISUAL="\"/path with spaces/to/editor/binary\"" is the
> >> easiest solution --- it requires no code changes so it will work with
> >> any svn binary out there.
> >
> > Yes, I think that's the best solution.
>
> And, in any case, VISUAL is a public inter
David Dyer-Bennet wrote on Tue, Dec 07, 2010 at 08:44:28 -0600:
> On Tue, December 7, 2010 04:18, Julian Foad wrote:
> > On Tue, 2010-12-07, Daniel Shahaf wrote:
> >> I suppose setting VISUAL="\"/path with spaces/to/editor/binary\"" is the
> >> easiest solution --- it requires no code changes so it
On Tue, December 7, 2010 04:18, Julian Foad wrote:
> On Tue, 2010-12-07, Daniel Shahaf wrote:
> I confirmed that there was a bug in that report, but that was on Windows
> and the evidence there was that the arguments were not being parsed
> correctly even when the space was escaped with the "^" c
On Tue, 2010-12-07, Daniel Shahaf wrote:
> CC += dev@
>
> Daniel Näslund wrote on Mon, Dec 06, 2010 at 21:32:39 +0100:
> > On Mon, Dec 06, 2010 at 01:44:23PM -0600, David Dyer-Bennet wrote:
> > > Subversion 1.6.12 running on Centos 5.5
> > >
> > > If the value of the environment variable VISUAL c
CC += dev@
Daniel Näslund wrote on Mon, Dec 06, 2010 at 21:32:39 +0100:
> On Mon, Dec 06, 2010 at 01:44:23PM -0600, David Dyer-Bennet wrote:
> > Subversion 1.6.12 running on Centos 5.5
> >
> > If the value of the environment variable VISUAL contains a space,
> > subversion fails when attempting t
'Daniel Shahaf' wrote on Mon, Oct 18, 2010 at 06:11:56 +0200:
> 'Daniel Shahaf' wrote on Mon, Oct 18, 2010 at 00:24:13 +0200:
> > Paul Maier wrote on Sun, Oct 17, 2010 at 22:30:23 +0200:
> > > Or if a whole directory is copied (from wc or from URL) and our file
> > > is contained somewhere in the d
'Daniel Shahaf' wrote on Mon, Oct 18, 2010 at 00:24:13 +0200:
> Paul Maier wrote on Sun, Oct 17, 2010 at 22:30:23 +0200:
> > svn cp svn://./a b
> > should also leave file b as read-write, doesn't it?
> >
>
> Should, but doesn't.
>
Fixed in r1023647, using the very same approach I originally
Just a note to say that I've filed issue #3601 to track this:
http://subversion.tigris.org/issues/show_bug.cgi?id=3601
--
C. Michael Pilato
CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
On Thu, Feb 25, 2010 at 2:06 PM, Julian Foad wrote:
> Lieven Govaerts wrote:
>> [[[
>> ra_serf: Fix support for international characters in paths.
[..]
>
>> [[[
>> Index: subversion/libsvn_ra_serf/merge.c
>> ===
>> --- subversion/libs
Lieven Govaerts wrote:
> [[[
> ra_serf: Fix support for international characters in paths.
>
> Found by: cmpilato
>
> * subversion/libsvn_ra_serf/property.c
> (end_propfind): Replace call to svn_uri_canonicalize with a call to
>svn_ra_serf__uri_to_internal.
> * subversion/libsvn_ra_serf/mer
> Cc: Subversion Development
>> Subject: Re: bug report: ra_serf gets PROPFIND failure on certain non-
>> ASCII paths
>
>
>> These paths are canonicalized before being used, but
>> svn_uri_canonicalize doesn't touch the encoded characters. Maybe it
>>
> -Original Message-
> From: lieven.govae...@gmail.com [mailto:lieven.govae...@gmail.com] On
> Behalf Of Lieven Govaerts
> Sent: woensdag 24 februari 2010 23:39
> To: C. Michael Pilato
> Cc: Subversion Development
> Subject: Re: bug report: ra_serf gets PROPFIND f
On Tue, Feb 23, 2010 at 3:37 PM, C. Michael Pilato wrote:
> Got the following bug report from one of our CollabNet Asia peers. I've not
> attempted to reproduce the problem myself. This bug was experienced using
> a 1.6.x client, but I don't know exactly which
Got the following bug report from one of our CollabNet Asia peers. I've not
attempted to reproduce the problem myself. This bug was experienced using
a 1.6.x client, but I don't know exactly which 'x'. Anybo
- yeah, that's the capability I miss compared to any other SCM system I know
(which is CVS, Perforce, and now - a little of git).
Add it to other smaller but also annoying things, and I am half the way into
git manual... Git has handy submodules which can be brought together into
any tree configura
On Thu, Jan 14, 2010 at 1:36 PM, Stas Cherkassky wrote:
> Michael,
>
> I think you are right - Subversion just wasn't designed for this
> methodology.
> But I can't believe SVN users don't have the same problem. I wonder how they
> solve it ...
We have the same problem, but our 'solution' is to j
-Original Message-
From: C. Michael Pilato [mailto:cmpil...@collab.net]
Sent: Thursday, January 14, 2010 11:57 PM
To: Stas Cherkassky
Cc: Julian Foad; dev@subversion.apache.org; Strahovsky, Ido
Subject: Re: suspected bug report or feature request - tagging a sparse
directory
I suspect th
I suspect that most folks that have this problem had it long before sparse
checkouts was introduced as a feature. I mean, there's nothing about sparse
checkouts that's specific to the goal you have in mind, right? So I suspect
those that have come before you have taken an additive approach to the
- Great! Make it 'svn cp --sparse --force WC URL' - and we are all set !
[ --force means that we can override file that already exists in the URL,
e.g. by creating a new revision of it, and not issue error message like it
does now ]
On Thu, Jan 14, 2010 at 8:59 PM, Philip Martin
wrote:
> "C. Mic
Michael,
I think you are right - Subversion just wasn't designed for this
methodology.
But I can't believe SVN users don't have the same problem. I wonder how they
solve it ...
In other words, the sparse tag is just a mean to achieve what I need, which
is a communication
between sub-module designe
"C. Michael Pilato" writes:
> Stas, you are quite right that the messaging here is important, if only to
> avoid hurt feelings. Your use-case is a valid one, and we'd all do well not
> to discount it. But Subversion simply wasn't designed to accommodate it.
> And this isn't even a small "oops w
Stas, you are quite right that the messaging here is important, if only to
avoid hurt feelings. Your use-case is a valid one, and we'd all do well not
to discount it. But Subversion simply wasn't designed to accommodate it.
And this isn't even a small "oops we overlooked it" thing. This is a
fun
Julian,
thanks you for your reply.
Your approach may technically work, but, I am afraid, it's not realistic in
real large project.
The [everything except dirA and dirB] part may be quite complicated for
large sparse tree.
The second approach (multiple svn cp WC URL) is also cumbersome and requir
Hi Stas.
Your question raises an important issue: "What are the semantics of
sparse directories?" You expected "svn copy" to copy just the parts that
are present in the WC, whereas in fact it copies the whole logical tree.
There is a reason for that, but I think it is not clear how a user
should e
On Fri, Jan 8, 2010 at 1:31 AM, Stas Cherkassky wrote:
> Julian,
>
> I don't want to remove parts of the tree from the repository.
> What I want is, effectively, a way to independently mark separate
> parts of the tree with the same tag.
> (I tried to explain it in my example). I don't see how you
Julian,
I don't want to remove parts of the tree from the repository.
What I want is, effectively, a way to independently mark separate
parts of the tree with the same tag.
(I tried to explain it in my example). I don't see how your method
(using svn rm) does it.
If a tag is a property of a file
Stas Cherkassky wrote:
[...]
> % svn co $SVNROOT/myproj -–depth empty myproj
> % svn update -–depth infinity myproj/dirA
>
> .. modifies it in some way and tries to tag:
>
> % svn mkdir $SVNROOT/tags/rel_X
> % svn copy myproj $SVNROOT/tags/rel_X/ -m “tagging part A of myproj
> for the next integ
Hi,
I have a problem with tagging a sparse directory.
Suppose I have this structure:
myproj
dirA
...
dirB
...
I want user A to work on dirA, and user B - on dirB.
But both are contributing to the same release-candidate, let's call it rel_X.
(the idea is that integrator would b
51 matches
Mail list logo
