How to pass a message file in UTF8 encoding to svn commit?

2015-08-27 Thread Hunger Tobias
Hello SVN users list!

I have a file in UTF8 encoding, containing a couple of non-ASCII characters 
(Cyrillic mostly, some äüß and such). I know that file to be in UTF8 encoding.

Then I am trying to run:
svn commit --encoding utf8 --file mymsg.txt somefile.cpp

and I get the following error:
svn: E22: Commit failed (details follow):
svn: E22: Error normalizing log message to internal format
svn: E22: Non-ASCII character (code 195) detected, and unable to convert 
to/from UTF-8

Did I set something wrong in --encoding? Or does that not effect --file? How 
can I force SVN to treat the file contents as UTF8?

Best Regards and thanks in advance for your help,
Tobias

Tobias Hunger, Senior Software Engineer | The Qt Company

The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der 
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B


Re: How to pass a message file in UTF8 encoding to svn commit?

2015-08-27 Thread Hunger Tobias
Hi Bert,

thank you for your prompt reply! I'll give that a try and see whether that 
works for everybody. utf8 does work fine for me, but people on windows claim 
it breaks for them.

Best Regards,
Tobias

Tobias Hunger, Senior Software Engineer | The Qt Company

The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der 
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B


From: Bert Huijben b...@qqmail.nl
Sent: Thursday, August 27, 2015 15:53
To: Hunger Tobias; users@subversion.apache.org
Subject: RE: How to pass a message file in UTF8 encoding to svn commit?

 -Original Message-
 From: Hunger Tobias [mailto:tobias.hun...@theqtcompany.com]
 Sent: donderdag 27 augustus 2015 15:45
 To: users@subversion.apache.org
 Subject: How to pass a message file in UTF8 encoding to svn commit?

 Hello SVN users list!

 I have a file in UTF8 encoding, containing a couple of non-ASCII
characters
 (Cyrillic mostly, some äüß and such). I know that file to be in UTF8
encoding.

 Then I am trying to run:
 svn commit --encoding utf8 --file mymsg.txt somefile.cpp

 and I get the following error:
 svn: E22: Commit failed (details follow):
 svn: E22: Error normalizing log message to internal format
 svn: E22: Non-ASCII character (code 195) detected, and unable to
convert
 to/from UTF-8

 Did I set something wrong in --encoding? Or does that not effect --file?
How
 can I force SVN to treat the file contents as UTF8?

I think at least UTF-8 as passed value should work.
That encoding name is hardcoded to avoid the entire conversion.

The other values might depend on what iconv settings are used by your
specific client.

Bert



RE: How to pass a message file in UTF8 encoding to svn commit?

2015-08-27 Thread Bert Huijben


 -Original Message-
 From: Hunger Tobias [mailto:tobias.hun...@theqtcompany.com]
 Sent: donderdag 27 augustus 2015 15:45
 To: users@subversion.apache.org
 Subject: How to pass a message file in UTF8 encoding to svn commit?
 
 Hello SVN users list!
 
 I have a file in UTF8 encoding, containing a couple of non-ASCII
characters
 (Cyrillic mostly, some äüß and such). I know that file to be in UTF8
encoding.
 
 Then I am trying to run:
 svn commit --encoding utf8 --file mymsg.txt somefile.cpp
 
 and I get the following error:
 svn: E22: Commit failed (details follow):
 svn: E22: Error normalizing log message to internal format
 svn: E22: Non-ASCII character (code 195) detected, and unable to
convert
 to/from UTF-8
 
 Did I set something wrong in --encoding? Or does that not effect --file?
How
 can I force SVN to treat the file contents as UTF8?

I think at least UTF-8 as passed value should work.
That encoding name is hardcoded to avoid the entire conversion.

The other values might depend on what iconv settings are used by your
specific client.

Bert



Re: assertion failed (svn_dirent_is_absolute(local_abspath)) TortoiseSVN-1.8.8

2015-08-27 Thread Andreas Stieger
Hello,

On 02/07/15 11:34, Valeriy Goncharov wrote:
 Subversion Exception!
 In file
 'D:\Development\SVN\Releases\TortoiseSVN-1.8.8\ext\subversion\subversion\libsvn_wc\wc_db.c'
 line 8731: assertion failed (svn_dirent_is_absolute(local_abspath))

Please update to the latest compatible TortoiseSVN 1.8.12 (linking
against svn 1.8.14) and try again:
http://sourceforge.net/projects/tortoisesvn/files/1.8.12/Application/

Andreas


update -r PREV causes tree conflict if a folder to be removed contains ignored sub-folder

2015-08-27 Thread Gert Kello
Hi.

I have a case where updating to older version causes tree conflict, if
update (to older revision) removes some folder and that folder has some
global-ignores ignored sub-folder. I'm not sure if that's a bug but it is
inconvenient for me...

The (windows cmd) script to create situation is attached. Basically,
1. The update removes folder
2. There's a unversioned subfolder in working copy
3. The subfolder is ignored via config file global-ignores

svn version 1.9.0 (r1692801), windows

If the unversioned folder is ignored via svn:ignore property then update
does not trigger tree conflict (but sequence 'svn up -R PREV  svn up'
still does...)

Am I doing something wrong with global-ignores?

Gert
@echo off
SET testdir=test
set URL=file:///%CD%/test/repos
set URL=%URL:C:\=\%
set URL=%URL:\=/%
echo Base url for repo: %URL%

RMDIR /Q /S %testdir%
mkdir %testdir% || goto error
svnadmin create %testdir%\repos || goto error
svn mkdir %URL%/trunk -m  || goto error
svn co %URL%/trunk %testdir%\trunk || goto error
mkdir %testdir%\trunk\test || goto error
echo Test1  %testdir%\trunk\test\a.txt || goto error
svn add --parents %testdir%\trunk\test\a.txt || goto error
svn ps svn:ignore bin %testdir%\trunk\test || goto error
svn commit %testdir%\trunk -m  || goto error

ECHO svn:ignore is Ok to be in removed dir
svn co %URL%/trunk %testdir%\wc1 || goto error
mkdir  %testdir%\wc1\test\bin || goto error
REM check that working copy status is clean
svn status %testdir%\wc1 || goto error
svn up %testdir%\wc1 -r PREV || goto error
ECHO 'svn up %testdir%\wc1' would cause tree conflict now
ECHO 'svn up %testdir%\wc1 --force' would work
ECHO.

ECHO global-ignores is not Ok to be in removed dir
svn co %URL%/trunk %testdir%\wc2 || goto error
mkdir  %testdir%\wc2\test\obj || goto error
REM check that working copy status is clean
svn status %testdir%\wc2 --config-option config:miscellany:global-ignores=obj 
|| goto error
svn up %testdir%\wc2 -r PREV --force --config-option 
config:miscellany:global-ignores=obj
goto end

:error 
echo The script did not work Ok.

:end