[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Problem with Fedora 18

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 21 Feb 2013 10:38:32 +0100

On Wed, Feb 20, 2013 at 08:51:25PM -0500, Gavin Baumanis wrote:
> Have you tried performing a;
> svn cleanup of your local working copy and then the upgrade?

Yes, this is recommended. Try running 'svn cleanup' with a 1.6
client, and then try running 'svn upgrade' with a 1.7 client.

Keep in mind that some corrupt 1.6 working copies cannot be
upgraded. E.g. some are corrupt even if 1.6 doesn't complain during
daily use, because 1.6 doesn't always read all .svn meta data at once.
Upgrading a working copy to 1.7 implies reading all .svn meta data
at once which might uncover lurking problems.

It is regrettable that not every 1.6 working copy can be upgraded
but it is not very easy for us to fix. See here for more information:
http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng

> From: Celso Tadao Suzuki [mailto:celso.suzuki_at_digitro.com.br]
> Sent: Wednesday, 20 February 2013 12:32
> To: dev_at_subversion.apache.org
> Subject: Problem with Fedora 18
>
> Hi,
>
> I was using Fedora 15 an I upgrade my box to Fedora 18.
> The SVN server is 1.6.6 version
> The SVN client is 1.7.8 version
>
> Now, when i try a command like info I got the message :
>
> [celso_at_sfw06 tcf]$ svn info
> svn: E155036: Please see the 'svn upgrade' command
> svn: E155036: Working copy '/home2/celso/SVN/tcf' is too old (format 10,
> created by Subversion 1.6)
>
> Executint the svn upgrade I got the message
>
> [celso_at_sfw06 tcf]$ svn upgrade
> svn: E200033: database is locked, executing statement 'PRAGMA
> synchronous=OFF;PRAGMA recursive_triggers=ON;'
>
> When I try to check out a new project the same message appears:
> [celso@sfw06 SVN]$ svn co http://pst.svn.digitro.com.br/easycall/tcf/trunk
> TcF
> svn: E200033: database is locked, executing statement 'PRAGMA
> synchronous=OFF;PRAGMA recursive_triggers=ON;'

This is strange. Did you try to check out a new working copy on top
of an existing working copy? I don't understand how you could otherwise
get this kind of error.

Please try again after changing the last argument to a directory that
does not yet exist.
 
>
> Obs:
>
> I read the file /var/log/httpd/access_log at the SVN server.
> When I execute the info and the upgrade command, there is no log. Only when
> I ran the check out command there is the following register:

That's expected. 'svn upgrade' is an off-line operation (except when
upgrading working copies created by very old Subversion clients which
did not cache repository ID information).

> 192.168.160.7 - - [20/Feb/2013:11:40:31 -0300] "OPTIONS /easycall/tcf/trunk
> HTTP/1.1" 401 401 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "OPTIONS
> /easycall/tcf/trunk HTTP/1.1" 200 179 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /easycall/tcf/trunk HTTP/1.1" 207 694 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /!svn/vcc/default HTTP/1.1" 207 385 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /!svn/bln/232442 HTTP/1.1" 207 446 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /easycall/tcf/trunk HTTP/1.1" 207 694 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /!svn/vcc/default HTTP/1.1" 207 446 "-" "SVN/1.7.8 neon/0.29.6"
> 192.168.160.7 - celso [20/Feb/2013:11:40:31 -0300] "PROPFIND
> /!svn/bc/232442/easycall/tcf/trunk HTTP/1.1" 207 709 "-" "SVN/1.7.8
> neon/0.29.6"
>
>
> Could you help me, please ?
>
> Thanks in advance
>
> Celso Suzuki
>
Received on 2013-02-21 10:39:20 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.