Re: Clarification on hot-backup.py usage

[David Chapman]

(please don't top-post; it makes the thread hard to follow)


On 6 October 2017 at 16:08, William Muriithi  wrote:

Hello,

I am looking at using the script below for backup purpose and a bit at
a loss at how the script verify the backup.

For context, I am referring to the script below and the flag below.

http://svn.apache.org/repos/asf/subversion/trunk/tools/backup/hot-backup.py.in

  --verify   Verify the backup

My question is, what should be the verify directory?  Is it the source
directory on which the SVN server use for writing or is it the backup
directory? I am suspecting its the source as the backup directory is
already compressed.  Would this be correct?

Regards,
William

On 10/6/2017 1:16 PM, William Muriithi wrote:



Hello,

Just realized my problem.  One don't need to specify a directory for
verification. Would still be happy if someone can confirm if
verification is done on the source repo or  on the resulting hot
backup

Thanks in advance.

Regards,
William


It verifies the hot backup directory.

--
David Chapman  dcchap...@acm.org
Chapman Consulting -- San Jose, CA
Software Development Done Right.
www.chapman-consulting-sj.com

Re: Clarification on hot-backup.py usage

[William Muriithi]

Hello,

Just realized my problem.  One don't need to specify a directory for
verification. Would still be happy if someone can confirm if
verification is done on the source repo or  on the resulting hot
backup

Thanks in advance.

Regards,
William

On 6 October 2017 at 16:08, William Muriithi  wrote:
> Hello,
>
> I am looking at using the script below for backup purpose and a bit at
> a loss at how the script verify the backup.
>
> For context, I am referring to the script below and the flag below.
>
> http://svn.apache.org/repos/asf/subversion/trunk/tools/backup/hot-backup.py.in
>
>  --verify   Verify the backup
>
> My question is, what should be the verify directory?  Is it the source
> directory on which the SVN server use for writing or is it the backup
> directory? I am suspecting its the source as the backup directory is
> already compressed.  Would this be correct?
>
> Regards,
> William

Clarification on hot-backup.py usage

[William Muriithi]

Hello,

I am looking at using the script below for backup purpose and a bit at
a loss at how the script verify the backup.

For context, I am referring to the script below and the flag below.

http://svn.apache.org/repos/asf/subversion/trunk/tools/backup/hot-backup.py.in

 --verify   Verify the backup

My question is, what should be the verify directory?  Is it the source
directory on which the SVN server use for writing or is it the backup
directory? I am suspecting its the source as the backup directory is
already compressed.  Would this be correct?

Regards,
William

Re: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

[Daniel Shahaf]

I can't reproduce your problem using a trunk client and httpd-2.4.25 on Linux.

Is there any http proxy or reverse proxy in your setup?

RE: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

[Bartosz Pierzchlewicz]

Dear Johan,
at my first e-mail I wrote EXACTLY what to do to reproduce error.
In my opinion this is low chance to blame client library.
We tried two different compilation of 'pure svn' on Windows, and as third: 
TortoiseSVN client.
Moreover we also tried to reproduce this on Linux machine.

I suppose that this may be connected with http transport, or apache/WebDAV or 
svn server, because when I create repo on locally and use file:/// transport, 
then everything is ok.

Bartosz


-Original Message-
From: Johan Corveleyn [mailto:jcor...@gmail.com] 
Sent: Friday, October 6, 2017 1:30 PM
To: Bartosz Pierzchlewicz
Cc: users@subversion.apache.org
Subject: Re: Problem with file name encoding during merge - URL Encoding 
(Percent Encoding)

On Fri, Oct 6, 2017 at 8:45 AM, Bartosz Pierzchlewicz 
 wrote:
> Hi Daniel,
> After merge to trunk, file on disk has proper name: "file With Space.txt".
> Moreover after commit, file on my disk still has proper name, but when 
> I Checkout to other directory it will have name 'file%20With%20Space.txt'.
>
> Log after second commit says exactly what was happened:
>
> A /trunk/file%20With%20Space.txt (from /branches/1.0/file With 
> Space.txt:3)
>
> File in trunk was created from file in branch, but the filename was changed.
> This is unwanted behavior.

Yes, this seems unwanted. But where did it go wrong? At this point it's unclear 
whether this is a user error, or some tool / UI on top of SVN that did 
something wrong, or SVN itself.

Can you check with the person who performed that commit, to see exactly what he 
did? What svn operation? With what tool (and which version of the tool)?

--
Johan

Re: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

[Johan Corveleyn]

On Fri, Oct 6, 2017 at 8:45 AM, Bartosz Pierzchlewicz
 wrote:
> Hi Daniel,
> After merge to trunk, file on disk has proper name: "file With Space.txt".
> Moreover after commit, file on my disk still has proper name,
> but when I Checkout to other directory it will have name 
> 'file%20With%20Space.txt'.
>
> Log after second commit says exactly what was happened:
>
> A /trunk/file%20With%20Space.txt (from /branches/1.0/file With Space.txt:3)
>
> File in trunk was created from file in branch, but the filename was changed.
> This is unwanted behavior.

Yes, this seems unwanted. But where did it go wrong? At this point
it's unclear whether this is a user error, or some tool / UI on top of
SVN that did something wrong, or SVN itself.

Can you check with the person who performed that commit, to see
exactly what he did? What svn operation? With what tool (and which
version of the tool)?

-- 
Johan

RE: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

[Bartosz Pierzchlewicz]

Hi Daniel,
After merge to trunk, file on disk has proper name: "file With Space.txt".
Moreover after commit, file on my disk still has proper name,
but when I Checkout to other directory it will have name 
'file%20With%20Space.txt'.

Log after second commit says exactly what was happened:

A /trunk/file%20With%20Space.txt (from /branches/1.0/file With Space.txt:3)

File in trunk was created from file in branch, but the filename was changed.
This is unwanted behavior.

Bartosz