Michael Schierl wrote on Thu, Apr 07, 2011 at 20:26:18 +0200:
> [ Please CC: me since I am not subscribed to the list. Thank you. ]
>
> Hi,
>
> I'd like to report what I think is a bug in SVN 1.6.16.
>
Thanks for the detailed bug report. I haven't looked at all the details
in your post yet, bu
On Thu, Apr 7, 2011 at 9:16 AM, Stutz Oliver wrote:
> Hello Everybody,
>
> I have a problem, i have installed SVN from the Repository or at least
> tried. Is this a normal Message? It is not very Informative can somebody
> tell me what i'am supposed to do in this situation, can this message be
> i
If I happen to have duplicated a previous proposal, I would appreciate
a redirect; but my search-fu hasn't been adequate to find any.
The reasons for not supporting the equivalent of the CVS $Log$ keyword
in Subversion are well-documented, in the FAQ: I would also note that
such global comments
> -Original Message-
> From: Danne, Ratnakar [mailto:dan...@schneider.com]
> Sent: 07 April 2011 15:29
> To: Cooke, Mark; users@subversion.apache.org
> Subject: RE: Subversion question
>
> Hi Mark.
>
> Thanks for your response.
> Presently I am on 1.4.4, planning to upgrade to 1.6. Is th
Hi Mark.
Thanks for your response.
Presently I am on 1.4.4, planning to upgrade to 1.6. Is there any documentation
available on how to upgrade to 1.6?
Danne, Ratnakar
Technology Services
920-592-8345
The information contained in this e-mail is privileged and confidential, and
for use only of t
On Thu, Apr 07, 2011 at 03:16:36PM +0200, Stutz Oliver wrote:
> Hello Everybody,
>
> I have a problem, i have installed SVN from the Repository or at least tried.
> Is this a normal Message? It is not very Informative can somebody tell me
> what i'am supposed to do in this situation, can this m
[ summary for dev@: bug in trunk that doesn't reproduce in 1.6.16;
I can reproduce it with trunk/ra_serf but not with trunk/ra_neon ]
Aleksandr Platonov wrote on Thu, Apr 07, 2011 at 17:52:13 +0400:
>
> I build Subversion as a part of TortoiseSVN (see
> http://tortoisesvn.googlecode.com/svn/trunk
I build Subversion as a part of TortoiseSVN (see
http://tortoisesvn.googlecode.com/svn/trunk/ext/build/subversion.build)
This problem happens when I try to checkout following url:
http://svn.webdav.org/repos/projects/neon/tags/0.29.5
Also I reproduced this problem on our internal host with mod_d
Hello Everybody,
I have a problem, i have installed SVN from the Repository or at least tried.
Is this a normal Message? It is not very Informative can somebody tell me what
i'am supposed to do in this situation, can this message be ignored and option 1
to be considered as a professional solut
Hi all,
I am building subversion 1.6.16 with swig (actually I try
swig 2.0.3). Build and install works fine (even "make swig-pl"),
but "make check-swigl-pl" fails:
cd /sw/src/subversion-1.6.16/subversion/bindings/swig/perl/native; make test
[...]
# Failed test 'use SVN::Core;'
# at ../../../
Thanks for the report. Having more information would help:
* Does this happen with neon, serf, or both?
* Can you build in debug mode (pass --debug to gen-make.py, if you're
using the build method from our INSTALL) to get some more information?
* Are any of those repositories public? (so tha
Hi.
Sometimes at checkouts and updates via TortoiseSVN which built with
latest Subversion code
(http://svn.apache.org/repos/asf/subversion/trunk) I get "XML parsing
error (200:OK)" and "Checksum mismatch" errors. This happens on
different repositories (e.g. XML parsing error
could happen at Subvers
Hi.
Sometimes at checkouts and updates via TortoiseSVN which built with
latest Subversion code
(http://svn.apache.org/repos/asf/subversion/trunk) I get "XML parsing
error (200:OK)" error. This happens on different repositories (e.g. this
could happen at Subversion code update).
This problem is not
13 matches
Mail list logo
