On Tue, Sep 15, 2015 at 06:57:43PM +, Wolfram, Dirk wrote:
> Hi all,
>
> I'd like to file a bug in Subversion 1.9.1 and 1.9.0, but I'm not sure if
> it's a deliberate behavior.
> The problem was not encountered in Subversion 1.7.6, which we used for a long
> time.
> I didn't find anything co
> -Original Message-
> From: Andreas Mohr [mailto:a...@lisas.de]
> Sent: woensdag 16 september 2015 07:48
> To: Eric Johnson
> Cc: b...@qqmail.nl; users@subversion.apache.org
> Subject: Re: Incomplete SVN dump files
>
> Hi,
>
> On Tue, Sep 15, 2015 at 05:26:38PM -0700, Eric Johnson wro
Brett Randall writes:
> Is it still considered valid to filter the client-capabilities passed
> to start-commit? The topic seemed to start with a conversation about
> separately-reporting client RA/protocol versus client-feature
> capabilities, but this resulted in the aforementioned "censoring"
Hi,
I need migrate a SVN project from the station A to machine B.
Server A
CentOS with SVN Version 1.6.12
Server B
CentOS with SVN Version 1.8.11
The size of my SVN project is around 70GB and has approximately 200,000 review.
On stations A I do :
svnadmin dump /path/to/RepositoryName> /tmp/r
Hi Stefan,
sorry this was an accident.
Of course this mail should go to users@subversion.apache.org as well.
BR,
Dirk
-Ursprüngliche Nachricht-
Von: Stefan Sperling [mailto:s...@elego.de]
Gesendet: Mittwoch, 16. September 2015 13:32
An: Wolfram, Dirk
Betreff: Re: Bug Report: The "svn
On Wed, Sep 16, 2015 at 12:08:33PM +, Wolfram, Dirk wrote:
> > I agree that the use of the svn:keywords "URL" has to effect a file's
> > contents if $URL$ is used and therefore the timestamp has to be changed as
> > well.
> >
> > But even if the $URL$ keyword is not set and the file contents
Hi Bert,
On Wed, Sep 16, 2015 at 2:33 AM, Bert Huijben wrote:
>
>
> > -Original Message-
> > From: Andreas Mohr [mailto:a...@lisas.de]
> > Sent: woensdag 16 september 2015 07:48
> > To: Eric Johnson
> > Cc: b...@qqmail.nl; users@subversion.apache.org
> > Subject: Re: Incomplete SVN dump
On 16.09.2015 14:31, Stefan Sperling wrote:
> On Wed, Sep 16, 2015 at 12:08:33PM +, Wolfram, Dirk wrote:
>>> I agree that the use of the svn:keywords "URL" has to effect a file's
>>> contents if $URL$ is used and therefore the timestamp has to be changed as
>>> well.
>>>
>>> But even if the $
On 16.09.2015 20:03, Eric Johnson wrote:
> Hi Bert,
>
> On Wed, Sep 16, 2015 at 2:33 AM, Bert Huijben wrote:
>
>>
>>> -Original Message-
>>> From: Andreas Mohr [mailto:a...@lisas.de]
>>> Sent: woensdag 16 september 2015 07:48
>>> To: Eric Johnson
>>> Cc: b...@qqmail.nl; users@subversion.a
Hi Brane,
>> On Sep 16, 2015, at 11:28 AM, Branko Čibej wrote:
>>
>> On 16.09.2015 20:03, Eric Johnson wrote:
>> Hi Bert,
>>
On Wed, Sep 16, 2015 at 2:33 AM, Bert Huijben wrote:
>>>
>>>
-Original Message-
From: Andreas Mohr [mailto:a...@lisas.de]
Sent: woensdag 16 sep
On Wed, Sep 16, 2015 at 3:47 PM, Eric Johnson wrote:
Yes, I can do that. Probably going to do that in chunks, otherwise it
> has the same awful performance profile as svnsync over a low latency
> connection.
>
FWIW, svnsync and svnrdump make identical calls over the network so their
performance
On Wed, Sep 16, 2015 at 3:55 PM, Mark Phippard wrote:
> On Wed, Sep 16, 2015 at 3:47 PM, Eric Johnson wrote:
>
> Yes, I can do that. Probably going to do that in chunks, otherwise it
>> has the same awful performance profile as svnsync over a low latency
>> connection.
>>
>
> FWIW, svnsync and s
Eric Johnson wrote on Wed, Sep 16, 2015 at 11:03:08 -0700:
> On Wed, Sep 16, 2015 at 2:33 AM, Bert Huijben wrote:
> > After an error you can't trust that the final portion is ok.
> >
>
> Sure, but why not encode that in the dump itself! The absence of an
> "end-commit" trailer could be a signal t
Eric Johnson wrote on Wed, Sep 16, 2015 at 11:03:08 -0700:
> So if the dump of the last commit is incomplete, I an error code tells me,
> what, exactly? That I need to manually edit the stream that I just dumped
> into a file? That I should discard the whole dump, and start again?
If you run dump
Hi Daniel,
The exact logistics of handling an error are probably pretty
straightforward. The underlying problem is that it is never a good
idea to pipe the output of svnrdump directly into svnadmin load,
because svnadmin cannot handle the failure unless the stream itself
carries more information.
Eric Johnson wrote on Wed, Sep 16, 2015 at 16:11:21 -0700:
> Hi Daniel,
>
> The exact logistics of handling an error are probably pretty
> straightforward. The underlying problem is that it is never a good
> idea to pipe the output of svnrdump directly into svnadmin load,
> because svnadmin cannot
16 matches
Mail list logo