Re: Feature Request: svn upgrade [--check][--check-current]

Marc Pawlowsky wrote on Fri, Dec 02, 2016 at 20:48:16 -0500: > However I believe a supported, documented, and forward compatible way is > preferable; given the volume of questions that come up when googling it > seems to be a popular item. > I don't recall it ever being asked before on this lis

Re: Feature Request: svn upgrade [--check][--check-current]

hether it gives > error E155036 or not? > > % ./tools/dev/which-error.py E155036 > 00155036 SVN_ERR_WC_UPGRADE_REQUIRED > > Going through your scenarios: > > > svn upgrade --check-current . > > CURRENT: yes > > UPGRADABLE: yes > > VERSION: 20 >

Re: Feature Request: svn upgrade [--check][--check-current]

be able to detect early on in a build process if > the wrong version of SVN was used. > Couldn't you run, say, 'svn info >/dev/null' and see whether it gives error E155036 or not? % ./tools/dev/which-error.py E155036 00155036 SVN_ERR_WC_UPGRADE_REQUIRED Goin

Feature Request: svn upgrade [--check][--check-current]

level as the svn version being used, and if not if it is upgradable. The use case is to be able to detect early on in a build process if the wrong version of SVN was used. Examples: svn upgrade --check . CURRENT: yes UPGRADABLE: yes VERSION: 20 exit code 0 to indicate upgradable, which should be a

Re: SVN upgrade

On Jun 16, 2016, at 6:05 AM, Somashekarappa, Anup (CWM-NR) wrote: > Is the pkgconfig related to apr or apr-util or it is independent of it? > > [USER@server subversion-1.9.4]$ make install > /usr/bin/install -c -d /usr/local/lib /usr/local/share/pkgconfig > /usr/bin/install: cannot change permi

Re: SVN upgrade

/pkgconfig /usr/bin/install: cannot change permissions of `/usr/local/share/pkgconfig': No such file or directory make: *** [install-fsmod-lib] Error 1 *From:*Stefan Hett [mailto:ste...@egosoft.com] *Sent:* 2016, June, 15 8:32 AM *To:* users@subversion.apache.org *Subject:* Re: SVN upgrade

RE: SVN upgrade

ctory make: *** [install-fsmod-lib] Error 1 From: Stefan Hett [mailto:ste...@egosoft.com] Sent: 2016, June, 15 8:32 AM To: users@subversion.apache.org Subject: Re: SVN upgrade Hi, Hello, Thank you for your quick response. I am able to proceed further but stuck at [USER@server subversion-1.9.4]$

Re: SVN upgrade

error message, right? If so, knowing your linux distribution would be useful. *From:*Stefan Hett [mailto:ste...@egosoft.com] *Sent:* 2016, June, 15 8:04 AM *To:* users@subversion.apache.org *Subject:* Re: SVN upgrade On 6/15/2016 1:50 PM, Somashekarappa, Anup (CWM-NR) wrote: Hi, I am try

RE: SVN upgrade

le or directory make: *** [install-fsmod-lib] Error 1 From: Stefan Hett [mailto:ste...@egosoft.com] Sent: 2016, June, 15 8:04 AM To: users@subversion.apache.org Subject: Re: SVN upgrade On 6/15/2016 1:50 PM, Somashekarappa, Anup (CWM-NR) wrote: Hi, I am trying t compile the source code to upgrade fro

Re: SVN upgrade

On 6/15/2016 1:50 PM, Somashekarappa, Anup (CWM-NR) wrote: Hi, I am trying t compile the source code to upgrade from SVN 1.7 to 1.9.4 but I am getting the below error. Could you please send the steps for upgrading since I couldn’t find any good document in web ? I am trying to follow the steps

SVN upgrade

Hi, I am trying t compile the source code to upgrade from SVN 1.7 to 1.9.4 but I am getting the below error. Could you please send the steps for upgrading since I couldn't find any good document in web ? I am trying to follow the steps mentioned in http://svn.apache.org/repos/asf/subversion

Re: Getting Subversion Exception while SVN Upgrade working copy

On 2015-03-26 6:08, Stefan Hett wrote: Hi, maybe better to start this of on the TortoiseSVN mailing list (since that's the client you seem to be using). TortoiseSVN uses the Subversion library, which is where the exception is coming from. Also, the message explicitly says to report it on the

Re: Getting Subversion Exception while SVN Upgrade working copy

Hi, maybe better to start this of on the TortoiseSVN mailing list (since that's the client you seem to be using). Regards, Stefan --- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on

Getting Subversion Exception while SVN Upgrade working copy

--- 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 please first search the mailing list

Re: "svn upgrade" does nothing

rectory structure because the root (of the local repo) was already in the > latest version[1]. Does upgrade try to go recursively into all directories, > checking for ".svn" and updating if necessary? Every 'svn' operation scans upwards to find the working copy root. So

Re: "svn upgrade" does nothing

I had pretty much the idea that "svn upgrade" and "svn upgrade ." were the same, I was just trying to scratch both options out of the list. Upgrading the directory itself fixed the problem. This makes me think (I'm saying this just seeing the behaviour, I have no ide

Re: "svn upgrade" does nothing

On Tue, Oct 21, 2014 at 04:42:14PM -0200, Julio Andre Biason wrote: > I run "svn upgrade" in two different forms: > > 1. First, a simple "svn upgrade". No output at all. "svn update" after that > fails: > > Updating '.': > svn: E155

Re: "svn upgrade" does nothing

I run "svn upgrade" in two different forms: 1. First, a simple "svn upgrade". No output at all. "svn update" after that fails: Updating '.': svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/home/jabiason

Re: "svn upgrade" does nothing

On Tue, Oct 21, 2014 at 02:10:39PM -0200, Julio Andre Biason wrote: > Hello, > > I'm having a weird issue with subversion: Every command is interrupt with > this: > > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy a

RE: "svn upgrade" does nothing

I suggest you do a new, clean checkout. You can just copy the dirty files into the new working copy. From: Julio Andre Biason [mailto:jabia...@ucs.br] Sent: Tuesday, October 21, 2014 12:11 PM To: users@subversion.apache.org Subject: "svn upgrade" does nothing Hello, I'm havin

"svn upgrade" does nothing

Hello, I'm having a weird issue with subversion: Every command is interrupt with this: svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/home/jabiason/{work}' is too old (format 10) to work with client version '1.8.10 (r1615264)&

Re: Node '....' has unexpectedly changed kind, after svn upgrade

On 16.09.2014 13:21, hankin wrote: > The status was ~ > > Something was definitely broken. > > When I remove the file and run "svn update", it is a normal file but > with only one line. But the file has many lines and is a normal file. > The status is still ~ after removing and updating. > > But i

Re: Node '....' has unexpectedly changed kind, after svn upgrade

tatus is M Anyways, I changed it to a link, removed the file, copied back the data, and added it again. It's ok now. Thanks. On 16 September 2014 20:37, Philip Martin wrote: > hankin writes: > > > It asked me to run "svn upgrade" so I did. > > > &g

Re: Node '....' has unexpectedly changed kind, after svn upgrade

hankin writes: > It asked me to run "svn upgrade" so I did. > > But now when I try to commit a folder, it says... > Node '' has unexpectedly changed kind > > I haven't changed this file for many months. > > When I run "svn info ..

Node '....' has unexpectedly changed kind, after svn upgrade

Hello, I just upgraded to svn 1.8.8 It asked me to run "svn upgrade" so I did. But now when I try to commit a folder, it says... Node '' has unexpectedly changed kind I haven't changed this file for many months. When I run "svn info ...", it says it&#x

RE: svn upgrade fails with failed assertion

> I'm trying to upgrade a very old svn repo but the command is failing. > > % svn upgrade . > svn: /build/buildd/subversion- > 1.7.5/subversion/libsvn_subr/dirent_uri.c:1518: uri_skip_ancestor: Assertion > `svn_uri_is_canonical(parent_uri, ((void *)0))' failed.

Re: svn upgrade fails with failed assertion

dclist writes: > I'm trying to upgrade a very old svn repo but the command is failing. "working copy" rather than "repo". > > % svn upgrade . > svn: > /build/buildd/subversion-1.7.5/subversion/libsvn_subr/dirent_uri.c:1518: > uri_skip_ancestor:

svn upgrade fails with failed assertion

I'm trying to upgrade a very old svn repo but the command is failing. % svn upgrade . svn: /build/buildd/subversion-1.7.5/subversion/libsvn_subr/dirent_uri.c:1518: uri_skip_ancestor: Assertion `svn_uri_is_canonical(parent_uri, ((void *)0))' failed. [1]3298 abort svn upgra

Re: Planning a SVN upgrade

On Thu, Sep 5, 2013 at 10:46 AM, Maureen Barger wrote: > That is a great idea, Giulio. How do you then make the mirrored repo > writable? > > You don't make mirrors writable. You can make them read-only, and do pass-through for write operations to the main repository for low grade failover behavi

Re: Planning a SVN upgrade

On 05/09/13 15:46, Maureen Barger wrote: That is a great idea, Giulio. How do you then make the mirrored repo writable? On Mon, Sep 2, 2013 at 4:47 AM, Giulio Troccoli wrote: On 23/08/13 21:09, Maureen Barger wrote: Hi - I am currently planning an upgrade from SVN 1.5 (using svnserve and ssh

Re: Planning a SVN upgrade

That is a great idea, Giulio. How do you then make the mirrored repo writable? On Mon, Sep 2, 2013 at 4:47 AM, Giulio Troccoli wrote: > > On 23/08/13 21:09, Maureen Barger wrote: >> >> Hi - >> I am currently planning an upgrade from SVN 1.5 (using svnserve and >> ssh tunnel) to SVN 1.8.1 fronted

Re: Planning a SVN upgrade

On 23/08/13 21:09, Maureen Barger wrote: Hi - I am currently planning an upgrade from SVN 1.5 (using svnserve and ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for authNz. We have about 50 repos. I'll be moving from an older Ubuntu 8 install to Centos 6 x64. My thought was I

Re: Planning a SVN upgrade

On 8/23/2013 4:09 PM, Maureen Barger wrote: Has anyone made a jump this large before? Any comments about my upgrade plan? We jumped from 1.5 to 1.8 on our server-side repositories. Our clients were using a mix of 1.6 and 1.7 (most of the "important to us" improvements in SVN 1.6 and 1.7 were

RE: Planning a SVN upgrade

From: Mark Phippard Sent: Saturday, 24 August 2013 6:35 AM On Fri, Aug 23, 2013 at 4:09 PM, Maureen Barger wrote: I am currently planning an upgrade from SVN 1.5 (using svnserve and ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for authNz. We ha

Re: Planning a SVN upgrade

On Fri, Aug 23, 2013 at 4:09 PM, Maureen Barger wrote: > I am currently planning an upgrade from SVN 1.5 (using svnserve and > ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for > authNz. > We have about 50 repos. I'll be moving from an older Ubuntu 8 install > to Centos 6 x64.

Planning a SVN upgrade

Hi - I am currently planning an upgrade from SVN 1.5 (using svnserve and ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for authNz. We have about 50 repos. I'll be moving from an older Ubuntu 8 install to Centos 6 x64. My thought was I could upgrade the SVN installation in place,

Re: Problem, svn upgrade & externals & svn status (1.6 --> 1.7)

On Wed, Jun 19, 2013 at 1:51 PM, Bert Huijben wrote: > Subversion 1.7.7 and later automatically upgrade all working copies > referenced from svn:externals properties too. > > ** ** > > For older clients can use ‘svn upgrade’ on the externals itself. > >

RE: Problem, svn upgrade & externals & svn status (1.6 --> 1.7)

Subversion 1.7.7 and later automatically upgrade all working copies referenced from svn:externals properties too. For older clients can use 'svn upgrade' on the externals itself. Bert From: Johan Holmberg [mailto:johan...@gmail.com] Sent: woensdag 19 juni 201

Problem, svn upgrade & externals & svn status (1.6 --> 1.7)

"proj1" is the old working copy with "svn upgrade" applied. "proj1-new" is a fresh checkout of the project with the new client version. I have looked around in the ".svn" directory of the projects and found a difference that perhaps explains

RE: error on SVN upgrade working copy when repository has been relocated

> -Original Message- > From: Johannes Lengler [mailto:johannes.leng...@googlemail.com] > Sent: vrijdag 27 juli 2012 10:52 > To: users@subversion.apache.org > Subject: error on SVN upgrade working copy when repository has been > relocated > > The error m

error on SVN upgrade working copy when repository has been relocated

p; SVN_IS_VALID_REVNUM(peg_rev)) ---- What I was doing: I did "SVN upgrade working copy" from version 1.6 to 1.7. Since my last update the svn repository has been relocated to a new url. (I haven't used the rep on this computer for quite some time.) Could that be t

Re: 'svn upgrade' fails with "svn: E155016: Insufficient NODES rows"

On Tue, Apr 17, 2012 at 3:15 PM, Philip Martin wrote: > Johan Corveleyn writes: > >> Do you think it would be useful / feasible to let the 1.7-upgrade code >> cope with this specific corruption, and just silently fix it? > > If somebody can be bothered to write the code I suppose it should be > p

Re: 'svn upgrade' fails with "svn: E155016: Insufficient NODES rows"

Johan Corveleyn writes: > Do you think it would be useful / feasible to let the 1.7-upgrade code > cope with this specific corruption, and just silently fix it? If somebody can be bothered to write the code I suppose it should be possible to ignore .svn-revert files for nodes that are not 'R'.

Re: 'svn upgrade' fails with "svn: E155016: Insufficient NODES rows"

On Tue, Apr 17, 2012 at 2:04 PM, Philip Martin wrote: > Johan Corveleyn writes: > >> When 'svn upgrade'-ing a 1.6 working copy with 1.7.4 (SlikSVN), I get >> the following error: >> >> [[[ >> C:\Temp\sourcesTest>svn upgrade >> Upgraded &#

Re: 'svn upgrade' fails with "svn: E155016: Insufficient NODES rows"

Johan Corveleyn writes: > When 'svn upgrade'-ing a 1.6 working copy with 1.7.4 (SlikSVN), I get > the following error: > > [[[ > C:\Temp\sourcesTest>svn upgrade > Upgraded '.' > Upgraded 'uz' > ... > svn: E155016: Insufficient

'svn upgrade' fails with "svn: E155016: Insufficient NODES rows"

When 'svn upgrade'-ing a 1.6 working copy with 1.7.4 (SlikSVN), I get the following error: [[[ C:\Temp\sourcesTest>svn upgrade Upgraded '.' Upgraded 'uz' ... svn: E155016: Insufficient NODES rows for 'C:\Temp\sourcesTest\.svn\tmp\wcng\uz\mock\TraceEleme

Re: svn upgrade bug with quotes in filename

Guten Tag Dave Rodgman, am Montag, 26. März 2012 um 17:48 schrieben Sie: > I notice that svn upgrade does not like paths with single quotes in the > filename (in this case a directory named "PCB's"). I was only able to > complete the upgrade by deleting the directory. You

svn upgrade bug with quotes in filename

Hi, I notice that svn upgrade does not like paths with single quotes in the filename (in this case a directory named "PCB's"). I was only able to complete the upgrade by deleting the directory. cheers Dave

Re: why does svn upgrade contact the server?

Am 15.12.2011 15:26, schrieb Jojakim: As I explained in my initial post, we have many individual projects. They are usually not touched - sometimes for years - once they are installed and tested (industrial automation area). When we need to do major changes, yes, we import them in a new repo. But

Re: why does svn upgrade contact the server?

On 15.12.2011 13:25:58, Stefan Sperling wrote: > I would recommend to use a 1.6 client instead of trying to upgrade the WC. > And above all import the data into a new repository so it can be versioned > properly again. Having a working copy as the only copy of the data was > bound to cause a dead-e

Re: why does svn upgrade contact the server?

On 15.12.2011 13:04:30, Philip Martin wrote: > The most likely thing to be missing is the root URL. That was it. After fixing entries it worked. Thank you! Jojakim

Re: why does svn upgrade contact the server?

I'd think the right thing to do here would be to import your pristine directory under .svn as the start of a new repository, check it out and copy over changes from the visible part of the working copy, commit that, then work as normal. Anyone have a better idea or hints on how to avoid unwanted m

Re: why does svn upgrade contact the server?

Stefan Sperling wrote on Thu, Dec 15, 2011 at 12:37:00 +0100: > 'svn upgrade' contacts the server when upgrading very old working > copies which didn't store the repository root and UUID. For the record, how old is "old" here? 1.5? 1.0?

Re: why does svn upgrade contact the server?

On Thu, Dec 15, 2011 at 12:04:31PM +, Philip Martin wrote: > Stefan Sperling writes: > > > You will likely be better > > of with a new checkout, given that such old working copies often exhibit > > problems during or after an upgrade to the 1.7.x format anyway. > > That's not possible as the

Re: why does svn upgrade contact the server?

Stefan Sperling writes: > You will likely be better > of with a new checkout, given that such old working copies often exhibit > problems during or after an upgrade to the 1.7.x format anyway. That's not possible as the repository effectively no longer exists. However it is possible to manually

Re: why does svn upgrade contact the server?

Guten Tag Jojakim Stahl, am Donnerstag, 15. Dezember 2011 um 11:54 schrieben Sie: > Till svn 1.6 > we could use svn diff to see changes that we implemented after the initial > crash. Does this mean you worked on the working copy and just never committed? You could have created a new repository wi

Re: why does svn upgrade contact the server?

ct the old server. > > > I found that here http://blogs.collab.net/subversion/ (section "Subversion > 1.7 Q & A, part 1") is stated regarding svn upgrade: "This is a local > metadata storage change only, though. 'svn upgrade' does not contact the > serv

why does svn upgrade contact the server?

1.7 Q & A, part 1") is stated regarding svn upgrade: "This is a local metadata storage change only, though. 'svn upgrade' does not contact the server and does not modify the content of the users' working files." So why my svn tries to contact the server at all? Thanks Jojakim

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

On Mon, Dec 5, 2011 at 5:51 PM, Philip Martin wrote: > "Cooke, Mark" writes: > >> My reading of the OP was that someone had probably seleected a >> sub-folder for conversion and that may well have succeeded.  Seeing as >> you can take a 1.6 sub-folder and effectively make it a top-level >> folder

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

Maybe this can happen in this specific situation if somebody uses "map network path" to a drive letter on windows. If the real root of the WC is \\someserver\\some\path\to\wc\root I can probably still map a drive letter (ie V: to \\someserver\some\path\to\wc\root\sub\folder\for\my\project If I th

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

"Cooke, Mark" writes: > My reading of the OP was that someone had probably seleected a > sub-folder for conversion and that may well have succeeded. Seeing as > you can take a 1.6 sub-folder and effectively make it a top-level > folder, this makes sense to me? Or does the upgrade code crawl > u

RE: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

> -Original Message- > From: Philip Martin [mailto:philip.mar...@wandisco.com] > Sent: 05 December 2011 16:25 > To: Keith Williams > Cc: users@subversion.apache.org > Subject: Re: Attmpting to Update Working Directory for a > Project from V1.6.17 to V1.7.1 using SVN

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

Keith Williams writes: > In examining the Working Copy more closely, the Folder Structure is > partially in 1.6 format and partially is 1.7 format. I am making this > assumption by the presence of the .svn folder in some top level > folders but not in others. A couple of files were deleted at the

RE: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

: Philip Martin [mailto:philip.mar...@wandisco.com] Sent: Monday, December 05, 2011 4:58 AM To: Keith Williams Cc: users@subversion.apache.org Subject: Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy Keith Williams writes: > Subvers

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

Keith Williams writes: > Subversion reported the following > (you can copy the content of this dialog > to the clipboard using Ctrl-C): > > In file > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\entries.c' > line 1654: assertion failed (parent_node || entry->

Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\entries.c' line 1654: assertion failed (parent_node || entry->schedule == svn_wc_schedule_normal)

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

On Mon, Oct 17, 2011 at 11:53:02AM +0200, Andreas Krey wrote: > On Mon, 17 Oct 2011 11:42:13 +, Christophe Franco wrote: > | You had a broken working copy that can't be upgraded. > | http://svn.haxx.se/tsvnusers/archive-2011-10/0086.shtml > > ...practically meaning that the WC 1.6->1.7 convers

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

On Mon, Oct 17, 2011 at 11:42:13AM +0200, Christophe Franco wrote: > Hello > > I have upgraded my TortoiseSVN to 1.7.0 version, and when trying to > upgrade one of my local working copies, here is the error message > that it displays : Known problem. Your 1.6 working copy was corrupted and cannot

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Am 17.10.2011 11:42, schrieb Christophe Franco: Please take the time to report this [...] with as much information as possible about what you were trying to do. This part is important. But please first search the mailing list archives for the error message to avoid reporting the same proble

Re: 1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

On Mon, 17 Oct 2011 11:42:13 +, Christophe Franco wrote: > Hello ... > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\entries.c' > line 1935: assertion failed (svn_checksum_match(entry_md5_checksum, > found_md5_checksum)) To quote Andy Levy from about ye

1.6 to 1.7 migration : Subversion Exception when doing "SVN Upgrade Working Copy"

Hello I have upgraded my TortoiseSVN to 1.7.0 version, and when trying to upgrade one of my local working copies, here is the error message that it displays : --- Subversion Exception! --- Subversion encountered a serious problem. Please take th

Re: svn upgrade with dump/load

On Wed, Sep 28, 2011 at 9:38 AM, Daniel Shahaf wrote: > Nico Kadel-Garcia wrote on Wed, Sep 28, 2011 at 09:15:13 -0400: >> On Tue, Sep 27, 2011 at 3:06 AM, Stümpfig, Thomas >> wrote: >> > Hi all, >> > >> > I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from >> > other threads

Re: svn upgrade with dump/load

On 28.09.2011 07:18, Daniel Shahaf wrote: Wouldn't it also be useful to pass --deltas to 'svnadmin dump'? Of course, you are absolutely right! -- Stefan^2. I should note the advice below only applies to FSFS-backed repositories. Stefan Fuhrmann wrote on Tue, Sep 27, 2011 at 11:11:45 +0200: S

Re: svn upgrade with dump/load

Nico Kadel-Garcia wrote on Wed, Sep 28, 2011 at 09:15:13 -0400: > On Tue, Sep 27, 2011 at 3:06 AM, Stümpfig, Thomas > wrote: > > Hi all, > > > > I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from > > other threads in this list, it is wise to dump and load the repository in > >

Re: svn upgrade with dump/load

On Tue, Sep 27, 2011 at 3:06 AM, Stümpfig, Thomas wrote: > Hi all, > > I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from > other threads in this list, it is wise to dump and load the repository in > order to bring everything to the latest features. Much, much faster and safe

Re: svn upgrade with dump/load

Wouldn't it also be useful to pass --deltas to 'svnadmin dump'? I should note the advice below only applies to FSFS-backed repositories. Stefan Fuhrmann wrote on Tue, Sep 27, 2011 at 11:11:45 +0200: > >Stümpfig, Thomas >

re: svn upgrade with dump/load

Stümpfig, Thomas > wrote: I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from other threads in this list, it is wise to dump and load the repository in order to bring everything to the la

Re: svn upgrade with dump/load

Am 27.09.2011 09:06, schrieb Stümpfig, Thomas: I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from other threads in this list, it is wise to dump and load the repository in order to bring everything to the latest features. I have to keep the revision numbers and transaction da

svn upgrade with dump/load

Hi all, I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned from other threads in this list, it is wise to dump and load the repository in order to bring everything to the latest features. I have to keep the revision numbers and transaction dates. Now svn dump and load offer some

svn upgrade: database table is locked

Hi, Which circumstances can cause "svn upgrade" in SVN 1.7 to fail with the following message: svn: E200030: database table is locked: NODES Thanks, Best regards Markus Schaber ___ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber |

Re: 1.7 'svn upgrade' issue on windows vista

On 09.08.2011 08:54, Ulrich Eckhardt wrote: > I don't think the folder containing the root of a WC should have to > have the exact same name as the folder in the repository it > corresponds to. As this is a feature to me, I hope that 1.7 isn't > going to break this. It is a bug, and it has been fi

Re: 1.7 'svn upgrade' issue on windows vista

On Friday 05 August 2011, Ryan Schmidt wrote: > On Aug 4, 2011, at 18:04, Stephen Meechan wrote: > > The problem was that the svn upgrade command is case sensitive on the WC > > folder name and failed if the name doesn't match exactly. Windows itself > > is case insensi

Re: 1.7 'svn upgrade' issue on windows vista

day, 5 August, 2011 12:32:41 GMT +00:00 GMT Britain, Ireland, Portugal Subject: RE: 1.7 'svn upgrade' issue on windows vista > -Original Message- > From: Stephen Meechan [mailto:s...@smeechan.co.uk] > Sent: vrijdag 5 augustus 2011 1:04 > To: users@subversion.apache.or

RE: 1.7 'svn upgrade' issue on windows vista

> -Original Message- > From: Stephen Meechan [mailto:s...@smeechan.co.uk] > Sent: vrijdag 5 augustus 2011 1:04 > To: users@subversion.apache.org > Subject: 1.7 'svn upgrade' issue on windows vista > > While testing out the svn upgrade feature in 1.7 beta

Re: 1.7 'svn upgrade' issue on windows vista

>> The problem was that the svn upgrade command is case sensitive on the WC >> folder name and failed if the >> name doesn't match exactly. Windows itself is case insensitive and none of >> the other svn commands are >> case sensitive to the WC folder name.

Re: 1.7 'svn upgrade' issue on windows vista

On Aug 4, 2011, at 18:04, Stephen Meechan wrote: > While testing out the svn upgrade feature in 1.7 beta 2, on some working > copies the upgrade failed with an error E155036. > > The problem was that the svn upgrade command is case sensitive on the WC > folder name and fai

1.7 'svn upgrade' issue on windows vista

While testing out the svn upgrade feature in 1.7 beta 2, on some working copies the upgrade failed with an error E155036. The problem was that the svn upgrade command is case sensitive on the WC folder name and failed if the name doesn't match exactly. Windows itself is case insensitiv