Re: [PATCH] allow svnsync to translate non-UTF-8 log messages to UTF-8

2010-09-13 Thread Daniel Shahaf
Daniel Trebbien wrote on Sun, Sep 12, 2010 at 16:21:03 -0700: > On Sun, Sep 12, 2010 at 1:49 PM, Daniel Shahaf > wrote: > > Unrelatedly, you mentioned that in the repository you work on there are > > soem properties in latin1 and some in utf8.  So one will need (until > > they fix the properties

Re: [PATCH] Test case for issue #3471: svn up touches file w/ lock & svn:keywords property

2010-09-13 Thread Senthil Kumaran S
Philip Martin wrote: + mu_ts_after_update = os.path.getmtime(mu_path) + if (mu_ts_before_update != mu_ts_after_update): +print("The timestamp of 'mu' before and after update does not match.") +raise svntest.Failure Why is this an failure? In the previous versions of subversion ie.,

Re: [PATCH] Test case for issue #3471: svn up touches file w/ lock & svn:keywords property

2010-09-13 Thread Philip Martin
Senthil Kumaran S writes: > In the previous versions of subversion ie., 1.5.x or 1.4.x the keyword > will not expand, but this is not the case with 1.6.x in which it gets > expanded for the first update. This is what the issue #3471 is about > and the committed patch tests that. I'm still confus

Re: Bindings for svn_auth_get_platform_specific_client_providers missing

2010-09-13 Thread Matthijs Kooijman
Hi folks, > I believe the swig perl tests (invoked by running 'make > check-swig-pl') are in subversion/bindings/swig/perl/native/t/ Ah, I'd looked over that very small directory name, I guess :-) I've attached an updated patch with a test case. The testcase is a bity ugly, since it tests each el

Re: [PATCH] allow svnsync to translate non-UTF-8 log messages to UTF-8

2010-09-13 Thread Stefan Sperling
On Sun, Sep 12, 2010 at 04:21:03PM -0700, Daniel Trebbien wrote: > I removed the normalization counting code without much thought in my > hastened efforts to produce a version of `svnsync` that I could use to > mirror the GNU Nano repository. Currently, I am thinking that Stefan > Sperling's idea o

Re: [PATCH] Test case for issue #3471: svn up touches file w/ lock & svn:keywords property

2010-09-13 Thread vijayaguru
On Mon, 2010-09-13 at 10:53 +0100, Philip Martin wrote: > Senthil Kumaran S writes: > > > In the previous versions of subversion ie., 1.5.x or 1.4.x the keyword > > will not expand, but this is not the case with 1.6.x in which it gets > > expanded for the first update. This is what the issue #347

Re: [PATCH] allow svnsync to translate non-UTF-8 log messages to UTF-8

2010-09-13 Thread Daniel Shahaf
Stefan Sperling wrote on Mon, Sep 13, 2010 at 12:16:44 +0200: > Having a similar reporting feature in "svnadmin verify", and ways to > fix these problems with "svndumpfilter" or maybe even "svnadmin recover" > wouldn't hurt either. The verify functionality is part of the FS layer; but the FS layer

Re: [PATCH] Test case for issue #3471: svn up touches file w/ lock & svn:keywords property

2010-09-13 Thread Philip Martin
vijayaguru writes: > In 1.5.x & 1.6.x, the keyword is expanded for the first update and > timestamp is changed for further updates. Here We are just locking the > file with keywords property set and we are not committing the file.Then > running "svn update" should expand the keyword & change the

When should working value of svn:keywords apply?

2010-09-13 Thread Philip Martin
Philip Martin writes: > vijayaguru writes: > >> In 1.5.x & 1.6.x, the keyword is expanded for the first update and >> timestamp is changed for further updates. Here We are just locking the >> file with keywords property set and we are not committing the file.Then >> running "svn update" should e

Re: svn commit: r996581 - in /subversion/trunk/subversion: libsvn_diff/parse-diff.c tests/cmdline/patch_tests.py

2010-09-13 Thread Julian Foad
On Mon, 2010-09-13, s...@apache.org wrote: > * subversion/libsvn_diff/parse-diff.c > (svn_diff_parse_next_patch): When generating a reverse diff, do not swap >the old and new filenames of the patch. The old filename in a unidiff >is often useless (e.g. it contains a ".orig" extension), bu

Re: svn commit: r996581 - in /subversion/trunk/subversion: libsvn_diff/parse-diff.c tests/cmdline/patch_tests.py

2010-09-13 Thread Stefan Sperling
On Mon, Sep 13, 2010 at 05:50:05PM +0100, Julian Foad wrote: > On Mon, 2010-09-13, s...@apache.org wrote: > > * subversion/libsvn_diff/parse-diff.c > > (svn_diff_parse_next_patch): When generating a reverse diff, do not swap > >the old and new filenames of the patch. The old filename in a uni

Fwd: svn commit: r996661 - /subversion/trunk/subversion/tests/libsvn_wc/entries-compat.c

2010-09-13 Thread Erik Huelsmann
Julian, This commit should remove the test failures you were experiencing on trunk with SVN_WC__NODES. At least that should give you confidence that if you see failures, you probably introduced them with local changes :-) Bye, Erik. -- Forwarded message -- From: Date: Mon, Se

In svn_subst_translate_string(), shouldn't REPAIR in the call to svn_subst_translate_cstring2() be TRUE?

2010-09-13 Thread Daniel Trebbien
Looking through the source code for `svn_subst_translate_string` in `subversion/libsvn_subr/subst.c`, it seems odd to me that the `repair` parameter to the call to `svn_subst_translate_cstring2` (for translating the line endings) is `FALSE`. `FALSE` means that if the line endings are inconsistent,

Re: [Issue 3474] making a new subdir, moving files into it and then renaming the subdir, breaks history of the moved files

2010-09-13 Thread Daniel Shahaf
Johan Corveleyn wrote on Sat, Sep 11, 2010 at 00:02:16 +0200: > On Fri, Sep 10, 2010 at 11:45 PM, wrote: > > http://subversion.tigris.org/issues/show_bug.cgi?id=3474 > > > > --- Additional comments from joha...@tigris.org Fri Sep 10 14:45:17 > > -0700 2010 --- > > This issue seems to be