Re: What is wrong with SVN?
David Stacey wrote: I think what you're seeing here is what we term a BLODA - some non-Cygwin application interfering with a Cygwin application. In your case, if you're not running a native Windows svn client then anti-virus is top of the suspect list. I know you claim that you have used MSE for years, but anti-virus tools update very frequently, and their behaviour can (and does) change. See the following link, under "File access problems": http://cygwin.com/faq/faq.html#faq.using.bloda Your best bet is to either disable or tune the anti-virus tool so that it doesn't scan the '.svn' directory inside your working copy. If you do this, does the check out complete successfully? If you are not able to try this, can you get svn to recover? Try these two commands in succession: $ svn cleanup $ svn update Does the check out complete (or at least get a little further)? I've taken a look at the cygcheck output that you attached and it seems to be OK. So unless anyone else on this list can provide further insight, it really looks as if a third party (probably your anti-virus) is locking the 'wc.db' file whilst svn is trying to update it - and there's not much we can do about that. As suggested here, http://gcc.gnu.org/ml/fortran/2013-09/msg00067.html there is a git mirror which allows to download the fortran-dev branch.. Thanks, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: What is wrong with SVN?
On 30/09/2013 13:08, Angelo Graziosi wrote: David Stacey wrote: Here are some ideas: Firstly, check to see which versions of subversion, sqlite3 and cygwin you're using. Check the output of the following command, and if you're using older packages then try updating: $ cygcheck -c cygwin sqlite3 subversion Cygwin Package Information Package VersionStatus cygwin 1.7.25-1 OK sqlite3 3.7.17-3 OK subversion 1.8.3-1OK Same here (on XP 32)... I have checked out the repo a second time, using the Cygwin packages listed above on Windows XP SP3. The operation completed successfully, checking out revision 203048. The operation took around 45 minutes. Thirdly, if the database file is locked then that could point to an old version of sqlite3 (namely 3.7.12.1) clashing with another subversion client (e.g. TortoiseSVN), or some anti-virus software locking a file in the '.svn' directory (e.g. 'wc.db'). See if you can check out into an area of the drive that isn't being virus scanned. For years I have the same AV (MSE) and I have used SVN without problems... I think what you're seeing here is what we term a BLODA - some non-Cygwin application interfering with a Cygwin application. In your case, if you're not running a native Windows svn client then anti-virus is top of the suspect list. I know you claim that you have used MSE for years, but anti-virus tools update very frequently, and their behaviour can (and does) change. See the following link, under "File access problems": http://cygwin.com/faq/faq.html#faq.using.bloda Your best bet is to either disable or tune the anti-virus tool so that it doesn't scan the '.svn' directory inside your working copy. If you do this, does the check out complete successfully? If you are not able to try this, can you get svn to recover? Try these two commands in succession: $ svn cleanup $ svn update Does the check out complete (or at least get a little further)? I've taken a look at the cygcheck output that you attached and it seems to be OK. So unless anyone else on this list can provide further insight, it really looks as if a third party (probably your anti-virus) is locking the 'wc.db' file whilst svn is trying to update it - and there's not much we can do about that. Cheers, Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: What is wrong with SVN?
Warren Young wrote: What happens if you modify it a bit: $ CYGWIN_SQLITE_LOCKING=posix svn co svn://... It works for almost an hour (I started to think it was a good fix for me...) but then it stopped in the same way... :-( [...] Afortran-dev/gcc/testsuite/gcc.c-torture/execute/pr42006.c Afortran-dev/gcc/testsuite/gcc.c-torture/execute/pr20466-1.c Afortran-dev/gcc/testsuite/gcc.c-torture/execute/980929-1.c svn: E200030: sqlite[S14]: unable to open database file svn: E200030: Additional errors: svn: E200030: sqlite[S14]: unable to open database file Ciao, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: What is wrong with SVN?
On 9/29/2013 13:39, Angelo Graziosi wrote: What is wrong with this command: $ svn co svn://gcc.gnu.org/svn/gcc/branches/fortran-dev fortran-dev What happens if you modify it a bit: $ CYGWIN_SQLITE_LOCKING=posix svn co svn://... That forces the SQLite library that Cygwin's svn is linked to to use POSIX compatible locking, instead of the Windows compatible locking it uses by default. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: What is wrong with SVN?
David Stacey wrote: Here are some ideas: Firstly, check to see which versions of subversion, sqlite3 and cygwin you're using. Check the output of the following command, and if you're using older packages then try updating: $ cygcheck -c cygwin sqlite3 subversion Cygwin Package Information Package VersionStatus cygwin 1.7.25-1 OK sqlite3 3.7.17-3 OK subversion 1.8.3-1OK Same here (on XP 32)... Secondly, make sure you're using the cygwin version of 'svn' (i.e. check that some other subversion client isn't in your path): $ which svn /usr/bin/svn I use only Cygwin... Thirdly, if the database file is locked then that could point to an old version of sqlite3 (namely 3.7.12.1) clashing with another subversion client (e.g. TortoiseSVN), or some anti-virus software locking a file in the '.svn' directory (e.g. 'wc.db'). See if you can check out into an area of the drive that isn't being virus scanned. For years I have the same AV (MSE) and I have used SVN without problems... Fourth, the branch you're trying to check out is quite large. Are you running out of drive space? No, I have about 30 GB free.. Attached the cygcheck... Ciao, Angelo. cygcheck_-svr.out.bz2 Description: Binary data -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: What is wrong with SVN?
On 29/09/2013 20:39, Angelo Graziosi wrote: What is wrong with this command: $ svn co svn://gcc.gnu.org/svn/gcc/branches/fortran-dev fortran-dev On GNU/Linux (kubuntu 12.04 64 bit) it is completed successfully but on Cygwin (32 bit) it fails after a while in this way: [...] A fortran-dev/gcc/testsuite/gnat.dg/abstract_with_anonymous_result.adb Afortran-dev/gcc/testsuite/gnat.dg/renaming4.ads Afortran-dev/gcc/testsuite/gnat.dg/loop_optimization14.ads svn: E200030: sqlite[S14]: unable to open database file svn: E200030: Additional errors: svn: E200030: sqlite[S14]: unable to open database file Works for me. Using your command (above), I checked out revision 203020 successfully in 32-bit Cygwin running under Windows 7 Ultimate. Here are some ideas: Firstly, check to see which versions of subversion, sqlite3 and cygwin you're using. Check the output of the following command, and if you're using older packages then try updating: $ cygcheck -c cygwin sqlite3 subversion Cygwin Package Information Package VersionStatus cygwin 1.7.25-1 OK sqlite3 3.7.17-3 OK subversion 1.8.3-1OK Secondly, make sure you're using the cygwin version of 'svn' (i.e. check that some other subversion client isn't in your path): $ which svn /usr/bin/svn Thirdly, if the database file is locked then that could point to an old version of sqlite3 (namely 3.7.12.1) clashing with another subversion client (e.g. TortoiseSVN), or some anti-virus software locking a file in the '.svn' directory (e.g. 'wc.db'). See if you can check out into an area of the drive that isn't being virus scanned. Fourth, the branch you're trying to check out is quite large. Are you running out of drive space? Finally, if all of the above fail, follow the problem reporting guidelines carefully: http://cygwin.com/problems.html Cheers, Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
What is wrong with SVN?
What is wrong with this command: $ svn co svn://gcc.gnu.org/svn/gcc/branches/fortran-dev fortran-dev On GNU/Linux (kubuntu 12.04 64 bit) it is completed successfully but on Cygwin (32 bit) it fails after a while in this way: [...] Afortran-dev/gcc/testsuite/gnat.dg/abstract_with_anonymous_result.adb Afortran-dev/gcc/testsuite/gnat.dg/renaming4.ads Afortran-dev/gcc/testsuite/gnat.dg/loop_optimization14.ads svn: E200030: sqlite[S14]: unable to open database file svn: E200030: Additional errors: svn: E200030: sqlite[S14]: unable to open database file Previous I have used many times SVN on Cygwin successfully.. Ciao, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
