ion/trunk/subversion/svnsync/sync.c
Is it the section that's commented as "Normalize svn:* properties as
necessary." that the error's being thrown?
--
Srdan Dukic
On 30 October 2012 17:21, Daniel Shahaf wrote:
> IIRC svnsync would only complain about revisions add or modify
tarts complaining about UTF-8 again and won't
load the version.
--
Srdan Dukic
On 30 October 2012 17:04, Daniel Shahaf wrote:
> Srdan Dukic wrote on Tue, Oct 30, 2012 at 16:58:01 +1300:
> > Checked it by examining the contents of the dump file (cat [dumpfile]).
> >
y errors
complaining about the encoding of the properties.
--
Srdan Dukic
On 30 October 2012 16:51, Daniel Shahaf wrote:
> Srdan Dukic wrote on Tue, Oct 30, 2012 at 16:45:36 +1300:
> > Thanks for that. Using svnadmin "dump" and then "load" worked.
> >
> > I d
Thanks for that. Using svnadmin "dump" and then "load" worked.
I didn't even have to pass the "--bypass-prop-validation" option to the
load command, as it seems the non-UTF8 symbols were converted to a "?" by
the dump command.
--
Srdan Dukic
O
or editing versioned property 'svn:log'
But still no luck. Can anyone tell me how to modify the "svn:log" property
on the file itself, as opposed to the revision property? Has anyone seen
this issue before?
Thank you
--
Srdan Dukic
eone who's working on
the Subversion code looking at the problem.
Thank you
--
Srdan Dukic
On 11 October 2011 09:38, Srdan Dukic wrote:
> 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 ab
ot;svn_utf_is_valid" function is the one that is
rejecting this value. Would you happen to know where this function is
defined?
Thank you
--
Srdan Dukic
On 11 October 2011 09:08, Daniel Shahaf wrote:
> Don't and don't.
>
> If you want to see what values cross the network, g
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 Oct
nc --source-prop-encoding
>
>
Is this a valid option to pass to svnsync? When I attempt to run svnsync
with this option, I get the following error:
svnsync: invalid option: --source-prop-encoding
The only other thing I can think of is that the original commit may have
been done on a windows mach
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:
>
anyone else had this problem? If so, how did you solve it?
The version of both of the subversion source and mirror are 1.6.11 and the
command line tools are also this version.
Thank you
--
Srdan Dukic
On 21 September 2011 08:53, Stephen Butler wrote:
>
>
> No, you can delete (on the command line) directly in the repository
> by escaping each " " in the URL with "\ " or "%20".
>
>
This is what I've tried:
svn rm http://subversion/src/Repo/Grad Training
svn rm "http://subversion/src/Repo/Grad T
On 20 September 2011 17:48, Lorenz wrote:
> Srdan Dukic wrote:
>
> I don't think you have a problem with spaces here.
>
>
So, just to confirm, ignoring the permissions issues, the only way to delete
a directory with a space in it in Subversion 1.6 is to check out the paren
Hi,
I've got a directory in subversion with a space in the name which I'd like
to delete. This is what I've tried:
svn rm http://subversion/src/Repo/Grad Training
svn rm "http://subversion/src/Repo/Grad Training"
svn rm "http://subversion/src/Repo/Grad%20Training";
svn rm http://subversion/src/Re
14 matches
Mail list logo