On 10/26/11 15:37, Philip Martin wrote:
Attila Nagyb...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn 1.7.1
Did you upgrade with 1.7.0 or 1.7.1?
I've upgraded the WC with 1.7.0, then switched to 1.7.1, which I'm
currently using.
The upgrade took nearly one
On Wed, Oct 26, 2011 at 10:27:24PM +0200, romaric rillet wrote:
Hi,
I have un file with the filesystem read-only attribut.
I commit this file with svn commit test.cpp -m .
Since version 1.7, the filesystem read-only attribut is removed by the
commit operation.
I would like to keep this
Robert-Jean Denault wrote on Wed, Oct 26, 2011 at 16:27:52 -0400:
Hello Stefan, Konstantin
I solved the problem by running a loop around svn pget, svn pset.
The svn pget returns clean log entries, so extraction the svn:log entries,
and resetting them cleans them up.
#!/bin/ksh
On Wed, Oct 26, 2011 at 10:27:24PM +0200, romaric rillet wrote:
Hi,
I have un file with the filesystem read-only attribut.
I commit this file with svn commit test.cpp -m .
Since version 1.7, the filesystem read-only attribut is
removed by the commit operation.
I would like to
On Thu, Oct 27, 2011 at 10:47:51AM +0200, Attila Nagy wrote:
On 10/26/11 15:37, Philip Martin wrote:
Attila Nagyb...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn 1.7.1
Did you upgrade with 1.7.0 or 1.7.1?
I've upgraded the WC with 1.7.0, then switched to
Hi,
Von: Attila Nagy [mailto:b...@fsn.hu]
BTW, with the current (1.7) WC-implementation, what possible problems do you
see where this would be needed?
Previously with the per-directory .svn directories it was of course much
easier, I could checkout the WC and move the .svn directory to
On Thu, Oct 27, 2011 at 09:53:11AM +, Markus Schaber wrote:
Hi,
Von: Attila Nagy [mailto:b...@fsn.hu]
BTW, with the current (1.7) WC-implementation, what possible problems do
you see where this would be needed?
Previously with the per-directory .svn directories it was of course
From: Philip Martin philip.martin_at_wandisco.com
Date: Tue, 25 Oct 2011 18:00:07 +0100
People are replying to utwente.nl address in your Reply-To header.
Thanks for pointing this out. I don't use this hotmail address a lot and
totally forgot the address in the reply-to (which stopped
On Thu, Oct 27, 2011 at 10:20:36AM +, Wabe W wrote:
From: Philip Martin
Can you reproduce the problem with a local test repository?
I tried to reproduce the problem by making a local test repository.
However, there's no problem anymore. It works perfectly fine.
Are path-based access
Attila Nagy b...@fsn.hu writes:
On 10/26/11 15:37, Philip Martin wrote:
Attila Nagyb...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn 1.7.1
Did you upgrade with 1.7.0 or 1.7.1?
I've upgraded the WC with 1.7.0, then switched to 1.7.1, which I'm
currently
Wabe W wabekoelm...@hotmail.com writes:
I also tried a checkout of a(n existing) repository to a different
location. I get the same error message when I try to update.
This is reproducible? You checkout some revision R1 and update to R2
and see the error?
Can you describe the changes between
On Thu, Oct 27, 2011 at 4:47 AM, Attila Nagy b...@fsn.hu wrote:
On 10/26/11 15:37, Philip Martin wrote:
Attila Nagy b...@fsn.hu b...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn 1.7.1
Did you upgrade with 1.7.0 or 1.7.1?
I've upgraded the WC with
On 10/27/11 13:47, Mark Phippard wrote:
On Thu, Oct 27, 2011 at 4:47 AM, Attila Nagy b...@fsn.hu
mailto:b...@fsn.hu wrote:
On 10/26/11 15:37, Philip Martin wrote:
Attila Nagyb...@fsn.hu mailto:b...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn
On 10/27/11 12:58, Philip Martin wrote:
Attila Nagyb...@fsn.hu writes:
On 10/26/11 15:37, Philip Martin wrote:
Attila Nagyb...@fsn.hu writes:
I'm trying to update a working copy of some tens of GBs with svn 1.7.1
Did you upgrade with 1.7.0 or 1.7.1?
I've upgraded the WC with 1.7.0,
Mark Phippard markp...@gmail.com writes:
I would imagine svn upgrade is almost entirely writes and I recall it does
quite a few transactions. So couldn't the linear slow down just be based on
the growth in the amount of bytes that are written to disk each time?
Yes, number of transactions
On 10/27/11 14:13, Philip Martin wrote:
Mark Phippardmarkp...@gmail.com writes:
I would imagine svn upgrade is almost entirely writes and I recall it does
quite a few transactions. So couldn't the linear slow down just be based on
the growth in the amount of bytes that are written to disk
Hi, Stefan,
Von: Stefan Sperling [mailto:s...@elego.de]
On Thu, Oct 27, 2011 at 09:53:11AM +, Markus Schaber wrote:
If you have uncommitted property modifications, copies or moves in the
working copy, a lossless transition (or repair) of the WC to 1.7 should be
possible in the following
On Thu, Oct 27, 2011 at 8:12 AM, Attila Nagy b...@fsn.hu wrote:
ZFS.
It it worth to make benchmarks with this WC with 1.6 and 1.7? I so, I can
try to find the time for it.
There are some pretty easy to run benchmarks you can run to see if 1.7 is
simply slower in your environment. See:
Hello,
This append when i upgrade working copy after instal of version 1.7
Thanks for your help
Best regards
Marc Salama
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion
Hi,
history :
I haved a FreeBSD server (8.0-STABLE) with subversion-1.6.17_2 port.
Acces to repository is configured thrue apache 2.2 + mod_dav + dav_svn.
Of course, all works fine :)
I've got a new server on FreeBSD 8.2-STABLE with subversion-1.7.1,
apache, mod_dav dav_svn.
All works fine
On Windows 7 Enterprise.
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But
On Thu, Oct 27, 2011 at 06:00:15PM +0400, Andrey Ogorodnik wrote:
Hello ,
WANdisco SVN v1.7.1 server. Updated to 1.7.1 from 1.7.0 because getting the
same problem on 1.7.0. Update did not help to solve an issue.
When using svn cleanup, receiving this assert/crash.
You may be running with a Berkeley DB library different than the one
your binaries were compiled against.
For future reference, don't send only the .log file but also the
transcript of the svnadmin invocation (copy-paste it from your
terminal).
Andrej Kičina wrote on Thu, Oct 27, 2011 at
Hello,
I have two PCs:
- PC1, IP: 192.168.8.16, Windows XP
- PC2, IP: 192.168.8.40, Windows Server 2003
In PC1 I have installed:
- Subversion for Win32, version 1.6.0.
- TortoiseSVN 1.6.16 for Win32
- Folder with scripts to control versions:
D:\Scripts_DB
(This folder contains many sub-folders
I was able to work around this. I tried the upgrade several times and
noticed it was always failing in the same place. I deleted the
subdirectory tree one level above that from my local copy and the
upgrade was successful. The subsequent SVN Update had no problems.
Unfortunately, I couldn't
25 matches
Mail list logo
