svn: E000022: Safe data '[...]/m' was followed by non-ASCII byte 195: unable to convert to/from UTF-8

2022-02-18 Thread Thorsten Schöning
Hi everyone,

I'm trying to checkout some SVN working copy on a Synology DSM 6.2.3,
where the SVN client was installed using the (deprecated) package
manager Entware-NG. Some of the directories to checkout contain German
umlauts like "ö", though having those in Windows and some other Ubuntu
18.04 works without any problems. In the first case I'm using TSVN,
while with UB am using the shell client provided by the OS.

The file name triggering the error message is "mööp.txt" and I
verified that it's storeed properly as UTF-8 in the repo:

> mööp.txt
> 6D C3 B6 C3 B6 70 2E 74 78 74

I'm somehwat sure that creating "mööp.txt" on the shell without SVN
works, because the locale uses UTF-8, my PuTTY-session uses UTF-8 and
the file name looks good on the shell in PuTTY. The following is the
locale:

> bash-4.3# locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=en_US.UTF-8

Any idea where this problem might come from?

I can't find any obvious client side setting and the locale doesn't
look that wrong to me. So I guess it might be some incompatibility in
used liby by SVN somewhere, especially as Entware-NG is deprecated.

Thanks!

Mit freundlichen Grüßen

Thorsten Schöning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: thorsten.schoen...@am-soft.de
Web:http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Fax:   05151-  9468-88
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska


Für Rückfragen stehe ich Ihnen jederzeit zur Verfügung. 

Mit freundlichen Grüßen, 

Thorsten Schöning


Telefon: +49 (0)515 94 68 - 0
Fax: 
E-Mail: tschoen...@am-soft.de

AM-Soft IT-Service - Bitstore Hameln GmbH
Brandenburger Straße 7c
31789 Hameln

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen 
und ist ausschliesslich für den Adressaten bestimmt. Jeglicher Zugriff auf 
diese E-Mail durch andere Personen als den Adressaten ist untersagt. Wenn Sie 
nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. 
Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, ist Ihnen jede 
Veröffentlichung, Vervielfältigung oder Weitergabe wie auch das Ergreifen oder 
Unterlassen von Massnahmen im Vertrauen auf erlangte Information untersagt. 

This e-mail may contain confidential and/or privileged information and is 
intended solely for the addressee. Access to this email by anyone else is 
unauthorized. If you are not the intended recipient (or have received this 
e-mail in error) please notify the sender immediately and destroy this e-mail. 
If you are not the intended recipient, any disclosure, copying, distribution or 
any action taken or omitted to be taken in reliance on it, is prohibited and 
may be unlawful. 

Hinweise zum Datenschutz: bitstore.group/datenschutz





svn file rename fails, but recreating a new file and copying the previous contents works

2022-02-18 Thread William Muriithi
Hello,

I have this setup:
- httpd-2.4.37-43
- subversion-1.14.1-1
- mod_dav_svn-1.14.1-1
- openssl-1.1.1k-5

The svn on Rocky Linux that is accessible only over https (Apache) and
everything works fine with exemption of "svn mv" command.  Below is a
series of commands on how to trigger the error.

svn mv xyz.txt  abc.txt
svn ci -m 'Renaming a dummy file for changes"
Adding abc.txt
svn: E175002: Commit failed (details follow):
svn: E175002: Unexpected HTTP status 502 'Bad Gateway' on
'/svn/pro/!svn/rvr/4748/abc.txt'

However, a new file abc.txt will get committed without any problem.

The problem seems to match a problem reported here.
https://community.opalstack.com/d/608-svn-unexpected-http-status-502-bad-gateway/3

This is dated and I am not sure it's still valid.  Has anyone seen
this problem on a fairly recent svn server?  Is there any way of
resolving it if its still a problem with current svn?

Regards,
William


Re: svn file rename fails, but recreating a new file and copying the previous contents works

2022-02-18 Thread Mark Phippard
On Fri, Feb 18, 2022 at 5:52 PM William Muriithi
 wrote:
>
> Hello,
>
> I have this setup:
> - httpd-2.4.37-43
> - subversion-1.14.1-1
> - mod_dav_svn-1.14.1-1
> - openssl-1.1.1k-5
>
> The svn on Rocky Linux that is accessible only over https (Apache) and
> everything works fine with exemption of "svn mv" command.  Below is a
> series of commands on how to trigger the error.
>
> svn mv xyz.txt  abc.txt
> svn ci -m 'Renaming a dummy file for changes"
> Adding abc.txt
> svn: E175002: Commit failed (details follow):
> svn: E175002: Unexpected HTTP status 502 'Bad Gateway' on
> '/svn/pro/!svn/rvr/4748/abc.txt'
>
> However, a new file abc.txt will get committed without any problem.
>
> The problem seems to match a problem reported here.
> https://community.opalstack.com/d/608-svn-unexpected-http-status-502-bad-gateway/3

That is a very common problem. It happens when the server is sitting
behind some kind of load balancer or proxy that is terminating the SSL
connection. The issue is that the svn copy and move commands use
WebDAV HTTP methods. These include the HTTP "Destination" header and
it needs to be rewritten by the proxy to change the https to http.

Here is one example:
https://stackoverflow.com/questions/2479346/502-bad-gateway-with-nginx-apache-subversion-ssl-svn-copy

The answer will depend on the Proxy being used.

Mark