Srdan Dukic wrote on Tue, Oct 11, 2011 at 10:15:53 +1300:
> I'm not going to open a bug, I just wanted to search to see whether there
> were any existing issues and this is what I found:
>
> I went to the Subversion bug tracker and searched for the phrase
> "svn_utf__is_valid" which turned up thre
I'm not going to open a bug, I just wanted to search to see whether there
were any existing issues and this is what I found:
I went to the Subversion bug tracker and searched for the phrase
"svn_utf__is_valid" which turned up three results, none of which seem to be
related:
http://subversion.tigri
I had no intention of filing a bug until I had done as much debugging as
possible, not being a developer myself. Thank you for your advice about
where to look for the error in the source code. I can see that the error is
thrown in the 'svn_repos_validate_prop' function in the file you mentioned.
Sp
Don't and don't.
If you want to see what values cross the network, go to the validation
function in libsvn_repos/fs-wrap.c that generates the error message you
get.
And I _am_ a developer, and I already asked you not to file a bug.
Please don't until you have identified a problem we don't already
Thank you for your help. I'll try and turn on debugging on the dav_svn
module to see what actual values are being passed across the network and if
that doesn't turn up anything, I guess I'll just ask on the dev mailing list
or open a bug.
Thanks again
--
Srdan Dukic
On 11 October 2011 08:40, Dan
Your revprops values are all ASCII and LF linefeeds, so r6107 should
get committed to the mirror without issue. The --source-prop-encoding
is new in 1.7.
So, yes, if you're still seeing the error *while syncing r6107* (i.e.,
mirror HEAD is r6106), I'm not really sure what's going on.
Srdan Dukic
> Odd. Perhaps some other revision property of that revision contains
> non-UTF-8?
>
The other revision properties are:
# svn proplist --revprop -r 6107 http://subversion/project/Flow
Unversioned properties on revision 6107:
svn:log
svn:author
svn:date
> > > The actual value of the svn:l
Srdan Dukic wrote on Mon, Oct 10, 2011 at 11:11:08 +1300:
> So, has no one seen this problem before? I guess I'll have to open a bug
> report.
>
No. Rejecting non-utf-8 properties is a common problem. Please don't
open a bug report for it.
(more below)
> --
> Srdan Dukic
>
> On 5 October 20
So, has no one seen this problem before? I guess I'll have to open a bug
report.
--
Srdan Dukic
On 5 October 2011 11:38, Srdan Dukic wrote:
> Hi,
>
> I'm using svnsync to mirror a repository and am doing the initial
> synchronization, when I get the following error:
>
> Transmitting file data
Hi,
I'm using svnsync to mirror a repository and am doing the initial
synchronization, when I get the following error:
Transmitting file data .svnsync: At least one property change failed;
repository is unchanged
svnsync: Error setting property 'log':
Could not execute PROPPATCH.Error setting pro
10 matches
Mail list logo
