Re: svn warning

2018-12-23 Thread Branko Čibej
On 23.12.2018 09:54, Руслан Самигуллин wrote:
> Hello!
>
> I have a problem with svn. The problem appears when I run svn. I have two 
> computers on Windows 10 x64, and on Win10 x32 [Version 10.0.17763.195]. This 
> problem appears on both computers.
>
> The text from the console window is reduced below:
>
> svn: warning: cannot set LC_CTYPE locale
> svn: warning: environment variable LANG is not set
> svn: warning: please check that your locale name is correct
>
> I tried to set LANG=en_US.UTF-8 but it doesn`t work.
> Please help me. How can I fix this problem?


You haven't replied to my last message on the other thread about this
issue that you started. Please don't just repeat questions, follow up on
that thread instead.

-- Brane



svn warning

2018-12-23 Thread Руслан Самигуллин
Hello!

I have a problem with svn. The problem appears when I run svn. I have two 
computers on Windows 10 x64, and on Win10 x32 [Version 10.0.17763.195]. This 
problem appears on both computers.

The text from the console window is reduced below:

svn: warning: cannot set LC_CTYPE locale
svn: warning: environment variable LANG is not set
svn: warning: please check that your locale name is correct

I tried to set LANG=en_US.UTF-8 but it doesn`t work.
Please help me. How can I fix this problem?

Best regards, 
Ruslan Samigullin 




Re: Improve svn warning/error message to faciliate troubleshooting

2016-05-11 Thread Daniel Shahaf
[moving to dev@, please drop users@ on followups]

Cosmere Infahm wrote on Wed, May 11, 2016 at 14:40:53 +0200:
> Could you please improve the warning/error to include the external involved
> so that troubleshooting is easier?

I think this patch will do the trick:

[[[
Index: subversion/libsvn_client/externals.c
===
--- subversion/libsvn_client/externals.c(revision 1743389)
+++ subversion/libsvn_client/externals.c(working copy)
@@ -497,8 +497,10 @@ switch_file_external(const char *local_abspath,
 if (!svn_dirent_is_ancestor(wcroot_abspath, def_dir_abspath))
 return svn_error_createf(
 SVN_ERR_WC_BAD_PATH, NULL,
-_("Cannot insert a file external defined on '%s' "
+_("Cannot insert a file external '%s' defined on '%s' "
   "into the working copy '%s'."),
+svn_dirent_local_style(local_abspath,
+   scratch_pool),
 svn_dirent_local_style(def_dir_abspath,
scratch_pool),
 svn_dirent_local_style(wcroot_abspath,
]]]

I don't have time to check if it passes tests, though.  I'd be glad if
someone else could pick it up...

Cheers,

Daniel
(Finding the code location generating the error message isn't black
magic; I simply grepped subversion/po/de.po for the error message.)


Re: Improve svn warning/error message to faciliate troubleshooting

2016-05-11 Thread Stefan Hett

Hi Cosmere,

Hello,

I am using svn version 1.8.9 on Centos and I get the following warnings

svn: warning: W155022: Cannot insert a file external defined on 
'/home/cosm/svn/parser/packages' into the working copy 
'/home/cosm/svn/parser/packages/src'.
svn: warning: W155022: Cannot insert a file external defined on 
'/home/cosm/svn/parser/packages' into the working copy 
'/home/cosm/svn/parser/packages/src'.
svn: E205011: Failure occurred processing one or more externals 
definitions


Could you please improve the warning/error to include the external 
involved so that troubleshooting is easier?


Thanks

You might wanna upgrade your SVN version to the latest 1.8 build (which 
is 1.8.16 at the time of writing this).
There are multiple client fixes impacting the handling of externals. For 
instance 1.8.13:

"better error message if an external is shadowed (r1655712, r1655738)"

While I'm not sure whether that's helping in your case, I take it that 
chances are not that bad. .-)


--
Regards,
Stefan Hett



Re: Improve svn warning/error message to faciliate troubleshooting

2016-05-11 Thread Branko Čibej
On 11 May 2016 2:40 p.m., "Cosmere Infahm" <infinic...@gmail.com> wrote:
>
> Hello,
>
> I am using svn version 1.8.9 on Centos and I get the following warnings
>
> svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
> svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
> svn: E205011: Failure occurred processing one or more externals
definitions
>
> Could you please improve the warning/error to include the external
involved so that troubleshooting is easier?

Can you please describe the structure of your working copy in a bit more
detail, such as where the svn:externals property is defined and what its
value is?

-- Brane


Improve svn warning/error message to faciliate troubleshooting

2016-05-11 Thread Cosmere Infahm
Hello,

I am using svn version 1.8.9 on Centos and I get the following warnings

svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
svn: E205011: Failure occurred processing one or more externals definitions

Could you please improve the warning/error to include the external involved
so that troubleshooting is easier?

Thanks


Re: svn: warning: W120171: Error running context: An error occurred during SSL communication

2013-09-25 Thread Lieven Govaerts
Hi,

On Tue, Sep 24, 2013 at 4:33 PM, Niemann, Hartmut
hartmut.niem...@siemens.com wrote:
 Hello!



 What is going wrong if I get

 svn: warning: W120171: Error running context: An error
 occurred during SSL communication

 five out of six times I try to update a repository or to do some other
 subversion command?


the error code comes from the serf library, more specifically this is
error SERF_ERROR_SSL_COMM_FAILED.
It indicates that the OpenSSL library reported an error during ssl/tls
communication. It should be unrelated to certificate validation as
that's another error code.


 (This is Tortoise SVN/64

 TortoiseSVN 1.8.2, Build 24708 - 64 Bit , 2013/08/27 19:20:39

 Subversion 1.8.3, -release

 apr 1.4.8
 apr-util 1.5.2
 serf 1.3.1
 OpenSSL 1.0.1e 11 Feb 2013
 zlib 1.2.8



 and it’s command line tool


 svn, version 1.8.3 (r1516576)

compiled Aug 27 2013, 22:13:03 on x86-microsoft-windows [...]

 * ra_serf : Module for accessing a repository via WebDAV protocol using
 serf.

   - using serf 1.3.1
   - handles 'http' scheme
   - handles 'https' scheme
 on Windows 7)



 The problems started yesterday (tsvn 1.8.1, about 3 out of 4 tries failed),
 today nothing works.


Was something in the server configuration related to ssl/tls modified?
Or, do you use a proxy server that was changed recently?

 I upgraded to 1.8.3, tried both the gui and the command line version.

 Where do I have to look for the cause of this failure?


First of all check the apache access and error logs, if the server
raised an ssl alert it should be in the logs.
Second, run wireshark.
  If you're using a proxy, check that the ssl tunnel setup was done
correctly. Also check that the proxy is not configured to close the
connection after the first request (Connection:Close header on the
response to the CONNECT request).
  Check if there are ssl alerts, check if it's the client or the
server that closed the connection, check if session initialisation was
successful.
Third, get yourself a build of serf with logging activated (#define
SSL_VERBOSE 1), send the logs to the list or to me privately, should
give us a lot of info to analyse what's wrong.

Lieven


 Mit freundlichen Grüßen
 Dr. Hartmut Niemann

 Siemens AG
 Infrastructure  Cities Sector
 Rail Systems Division
 Locomotives and Components
 IC RL LOC EN LE 8
 Werner-von-Siemens-Str. 67
 91052 Erlangen, Deutschland
 Tel: +49 9131 7-34264
 Fax: +49 9131 7-26254
 mailto:hartmut.niem...@siemens.com

 Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme;
 Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Brigitte Ederer, Klaus
 Helmrich, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y.
 Solmssen, Michael Süß; Sitz der Gesellschaft: Berlin und München,
 Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB
 6684; WEEE-Reg.-Nr. DE 23691322


svn: warning: W120171: Error running context: An error occurred during SSL communication

2013-09-24 Thread Niemann, Hartmut
Hello!

What is going wrong if I get
svn: warning: W120171: Error running context: An error occurred 
during SSL communication
five out of six times I try to update a repository or to do some other 
subversion command?

(This is Tortoise SVN/64
TortoiseSVN 1.8.2, Build 24708 - 64 Bit , 2013/08/27 19:20:39
Subversion 1.8.3, -release
apr 1.4.8
apr-util 1.5.2
serf 1.3.1
OpenSSL 1.0.1e 11 Feb 2013
zlib 1.2.8

and it's command line tool

svn, version 1.8.3 (r1516576)
   compiled Aug 27 2013, 22:13:03 on x86-microsoft-windows [...]
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.1
  - handles 'http' scheme
  - handles 'https' scheme
on Windows 7)

The problems started yesterday (tsvn 1.8.1, about 3 out of 4 tries failed), 
today nothing works.
I upgraded to 1.8.3, tried both the gui and the command line version.

Where do I have to look for the cause of this failure?

Mit freundlichen Grüßen
Dr. Hartmut Niemann

Siemens AG
Infrastructure  Cities Sector
Rail Systems Division
Locomotives and Components
IC RL LOC EN LE 8
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Tel: +49 9131 7-34264
Fax: +49 9131 7-26254
mailto:hartmut.niem...@siemens.com

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; 
Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Brigitte Ederer, Klaus 
Helmrich, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, 
Michael Süß; Sitz der Gesellschaft: Berlin und München, Deutschland; 
Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; 
WEEE-Reg.-Nr. DE 23691322


Re: svn warning when checkout.

2012-06-20 Thread Nico Kadel-Garcia
On Wed, Jun 20, 2012 at 1:15 AM, Ryan Schmidt
subversion-20...@ryandesign.com wrote:

 On Jun 20, 2012, at 00:01, dhanushka ranasinghe wrote:

 i have svn repo that can be checkout from both http and https, but commits 
 are only allowed via https.  issue is when we checking out svn form http ... 
 i get following waring ...

 is there any reason for that

 Fetching external item into 'modules/'
 svn: warning: 'http://svn.khc.com/repos/home/tests'
 is not the same repository as
 'https://svn.khc.com/repos/home'

 It sounds like your externals are using absolute https URLs, and Subversion 
 complains that this does not match the URL you checked out the rest of the 
 repository from when you check out with http.

 I don't know why Subversion is caring about that. But have you considered 
 using relative URLs for your externals? Usually that's better than using 
 absolute URLs including the protocol.

Did you do a svn switch somewhere in there, and neglect or fail to
switch the contents of the externals in your working copy? And can you
show your svn:externals content?


svn warning when checkout.

2012-06-19 Thread dhanushka ranasinghe
Hi guys ,

i have svn repo that can be checkout from both http and https, but commits
are only allowed via https.  issue is when we checking out svn form http
... i get following waring ...

is there any reason for that

Fetching external item into 'modules/'
svn: warning: '*http*://svn.khc.com/repos/home/tests'
*is not the same repository as*
*'https://svn.khc.com/repos/home'


Thank You
Dhanushka
*


Re: svn warning when checkout.

2012-06-19 Thread Ryan Schmidt

On Jun 20, 2012, at 00:01, dhanushka ranasinghe wrote:

 i have svn repo that can be checkout from both http and https, but commits 
 are only allowed via https.  issue is when we checking out svn form http ... 
 i get following waring ...
 
 is there any reason for that 
 
 Fetching external item into 'modules/'
 svn: warning: 'http://svn.khc.com/repos/home/tests'
 is not the same repository as
 'https://svn.khc.com/repos/home'

It sounds like your externals are using absolute https URLs, and Subversion 
complains that this does not match the URL you checked out the rest of the 
repository from when you check out with http.

I don't know why Subversion is caring about that. But have you considered using 
relative URLs for your externals? Usually that's better than using absolute 
URLs including the protocol.