Re: cygwin 1.7.15: svn disk I/O error
On 8/7/2012 11:32 AM, David Rothenberger wrote: On 8/6/2012 7:21 PM, Warren Young wrote: Some time after *that*, at a future time entirely up to the Subversion packages' maintainer, David Rothenberger, Subversion will be rebuilt against those new SQLite packages. Is that actually necessary? SVN is dynamically linked to SQLite, so a recompile isn't necessary unless the ABI for SQLite changes, right? I was just recalling your -3 and -4 packages, rebuilt after my last SQLite release, partly to see if rebuilding would fix the svn+sqlite problems. You are right that that might not have done anything, and that consequently a rebuild won't be necessary or helpful now either. -- 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: cygwin 1.7.15: svn disk I/O error
On 8/6/2012 7:21 PM, Warren Young wrote: > Some time after *that*, at a future time entirely up to the Subversion > packages' maintainer, David Rothenberger, Subversion will be rebuilt > against those new SQLite packages. Is that actually necessary? SVN is dynamically linked to SQLite, so a recompile isn't necessary unless the ABI for SQLite changes, right? -- David Rothenberger daver...@acm.org What hath Bob wrought? -- 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: cygwin 1.7.15: svn disk I/O error
Christopher, On Tue, Aug 7, 2012 at 12:07 AM, Christopher Faylor wrote: >>Is the snapshot that cgf is testing going to roll back svn to SQLite >>3.7.3? > > Huh? No. I really have to point out that the Cygwin DLL != SQLite? I'm not familiar with the snapshot process, and I didn't realize from your wording that a snapshot only contained the Cygwin DLL itself: "We're considering rolling a new release which fixes some of the problems which have cropped up here in the last few weeks. So, if you haven't already, we'd appreciate having people try out the latest snapshot at: http://cygwin.com/snapshots/ ." Warren has set me straight. Michael -- 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: cygwin 1.7.15: svn disk I/O error
On Mon, Aug 6, 2012 at 10:21 PM, Warren Young wrote: >>> What reason could there be for a new Cygwin DLL to be accompanied by a >>> new >>> version of SQLite? Their maintainerships are entirely decoupled. >> >> Pardon my ignorance; I'm not familiar with the release process. > > Well, to a first approximation, it's entirely asynchronous. Every package > maintainer releases versions on whatever schedule they wish. There are > probably dozens of active Cygwin package maintainers. Got it; I had somehow gotten the impression that there was one big synchronized release-to-production of the Cygwin binary and all packages. > You have to enter the Cygwin Time Machine to do that: > http://www.fruitbat.org/Cygwin/index.html#cygwincirca Thanks! > Bottom line: it's going to take at least a few days if you want to wait, > maybe a week, maybe more. If you have to have a fix today, use the Time > Machine. Thanks for the insight into the package release process. Given that branch reintegration is so dicey that I've ended up doing while [ 1 ]; do cleanup && revert && reintegrate && break; done , I think I'll use the Time Machine :) Michael -- 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: cygwin 1.7.15: svn disk I/O error
On 8/6/2012 11:06 PM, Achim Gratz wrote: Warren Young writes: I think I've given Achim Gratz enough time to try and fix the bug resulting from his build option changes. I cannot fix something that I can't even reproduce. I gave you some ideas of ways to reproduce it without TortoiseSVN. Did you try those? I didn't hear one way or the other. I can however reproduce the bug that led to and fixed by those changes. Try my .13 release. While updating my source patch so it would apply, I saw that upstream made a change that might have some relevance to your original complaint. There may be others. Anyway, I think the whole "pretend it's Unix" concept hangs up on the fact that SQLite has a *lot* of Windows and Cygwin-aware code in it. It may be that your attempt simply wasn't complete enough, so that you had mostly POSIX code but the occasional Windows- or Cygwin-ism in there fighting against it. I think it would be interesting to do a caveman patch to SQLite, completely ripping out anything Cygwin or Windows related, then see how that does. -- 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: cygwin 1.7.15: svn disk I/O error
Warren Young writes: > I think I've given Achim Gratz enough time to try and fix the bug > resulting from his build option changes. I cannot fix something that I can't even reproduce. I can however reproduce the bug that led to and fixed by those changes. As said before, if someone has an idea how to reproduce I'll look into it again and until then you are free to do whatever you deem reasonable. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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: cygwin 1.7.15: svn disk I/O error
On Mon, Aug 06, 2012 at 08:40:10PM -0400, Michael Gundlach wrote: >Hello, > >On Fri, 15 Jun 2012, Warren Young wrote: >> tl;dr: someone made the problem go away by rolling my recent 3.7.12 release >> back to the prior 3.7.3 version. > >I also have this problem (on a new Win7x64 machine with an SSD) >despite not having TortoiseSVN installed nor having Microsoft Security >Essentials' Real Time scanning turned on. > >I'd be happy to revert SQLite to 3.7.3 and work around the problem. >However, I am unable to revert SQLite from 3.7.12 to 3.7.3, because I >get an svn error after doing that: "SQLite compiled for 3.7.12, but >running with 3.7.3". Cygwin setup offers me subversion 1.7.5-4 and >1.7.5-3, and both result in the same error. > >Is the snapshot that cgf is testing going to roll back svn to SQLite >3.7.3? If not, any pointers on how to handle this myself would be >appreciated. Huh? No. I really have to point out that the Cygwin DLL != SQLite? -- 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: cygwin 1.7.15: svn disk I/O error
On 8/6/2012 7:55 PM, Michael Gundlach wrote: On Mon, Aug 6, 2012 at 9:09 PM, Warren Young wrote: Is the snapshot that cgf is testing going to roll back svn to SQLite 3.7.3? What reason could there be for a new Cygwin DLL to be accompanied by a new version of SQLite? Their maintainerships are entirely decoupled. Pardon my ignorance; I'm not familiar with the release process. Well, to a first approximation, it's entirely asynchronous. Every package maintainer releases versions on whatever schedule they wish. There are probably dozens of active Cygwin package maintainers. Occasionally one package depends on a fix in another, so that the release of one will dictate the release schedule of another, but this is not only rare, the condition generally doesn't persist. fact, I wasn't aware that I could get to subversion -1 or -2 once it was gone from Cygwin Setup. You have to enter the Cygwin Time Machine to do that: http://www.fruitbat.org/Cygwin/index.html#cygwincirca You can start digging somewhere around 1.7.15-1. you'll be shipping an update such that Cygwin Setup will offer a working subversion package out of the box? As soon as I'm done sending this email, I'll send another email (called an RFU) asking one of the Cygwin server admins to copy my new SQLite 3.7.13-1 packages up to the main Cygwin package repository server. About a day after they've done that, those new packages will be on all the mirrors. Some time after *that*, at a future time entirely up to the Subversion packages' maintainer, David Rothenberger, Subversion will be rebuilt against those new SQLite packages. He will do his own RFU, and a day or so later, you'll be able to use setup.exe to upgrade to this new system. Bottom line: it's going to take at least a few days if you want to wait, maybe a week, maybe more. If you have to have a fix today, use the Time Machine. -- 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: cygwin 1.7.15: svn disk I/O error
On Mon, Aug 6, 2012 at 9:09 PM, Warren Young wrote: >> Is the snapshot that cgf is testing going to roll back svn to SQLite >> 3.7.3? > > What reason could there be for a new Cygwin DLL to be accompanied by a new > version of SQLite? Their maintainerships are entirely decoupled. Pardon my ignorance; I'm not familiar with the release process. In fact, I wasn't aware that I could get to subversion -1 or -2 once it was gone from Cygwin Setup. Could you point me to instructions for installing old packages, and I can take it from there? > I've pretty much already given up on this. I thought I would wait for > SQLite 3.7.14, then build it the old way, but I see no signs that will > happen soon. According to the announced intention to release every 2-3 > months, it could happen this week, or it could happen next month. > > I think I've given Achim Gratz enough time to try and fix the bug resulting > from his build option changes. > > I'll start working on a .13 release, built the old way. Sorry again that I'm not familiar with how the project is run -- do you mean that you'll be shipping an update such that Cygwin Setup will offer a working subversion package out of the box? Thanks again! Michael -- 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: cygwin 1.7.15: svn disk I/O error
On 8/6/2012 6:40 PM, Michael Gundlach wrote: I'd be happy to revert SQLite to 3.7.3 and work around the problem. However, I am unable to revert SQLite from 3.7.12 to 3.7.3, because I get an svn error after doing that: "SQLite compiled for 3.7.12, but running with 3.7.3". Cygwin setup offers me subversion 1.7.5-4 and 1.7.5-3, and both result in the same error. Yes, both -3 and -4 were rebuilt against SQLite 3.7.12. You'd have to dig up a copy of -1 or -2 to get back to the 3.7.3 based versions. Is the snapshot that cgf is testing going to roll back svn to SQLite 3.7.3? What reason could there be for a new Cygwin DLL to be accompanied by a new version of SQLite? Their maintainerships are entirely decoupled. I've pretty much already given up on this. I thought I would wait for SQLite 3.7.14, then build it the old way, but I see no signs that will happen soon. According to the announced intention to release every 2-3 months, it could happen this week, or it could happen next month. I think I've given Achim Gratz enough time to try and fix the bug resulting from his build option changes. I'll start working on a .13 release, built the old way. -- 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: cygwin 1.7.15: svn disk I/O error
Hello, On Fri, 15 Jun 2012, Warren Young wrote: > tl;dr: someone made the problem go away by rolling my recent 3.7.12 release > back to the prior 3.7.3 version. I also have this problem (on a new Win7x64 machine with an SSD) despite not having TortoiseSVN installed nor having Microsoft Security Essentials' Real Time scanning turned on. I'd be happy to revert SQLite to 3.7.3 and work around the problem. However, I am unable to revert SQLite from 3.7.12 to 3.7.3, because I get an svn error after doing that: "SQLite compiled for 3.7.12, but running with 3.7.3". Cygwin setup offers me subversion 1.7.5-4 and 1.7.5-3, and both result in the same error. Is the snapshot that cgf is testing going to roll back svn to SQLite 3.7.3? If not, any pointers on how to handle this myself would be appreciated. Thanks in advance, Michael -- 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: cygwin 1.7.15: svn disk I/O error
On 7/11/2012 9:47 AM, Achim Gratz wrote: marco atzeri gmail.com> writes: a solution for testing is to add the new directory as first in the PATH. I think it already tries to do that, I'll have to check more closely if it's missing some directories or if the order is perhaps wrong. It may also be that the Ruby and Perl dynaloaders ignore the PATH settings in certain situations (at least the Perl dynaloader seems to map the library via an absolute path). It will be a while before I get to this, for now I'll just use the workaround of installing the untested libraries onto the build system before testing. Regards, Achim. if it is a perl dll, than he need to install. In windows the current directory is always considered so the perl binary will use the dll in /usr/bin before anything else in the PATH. I have the same issue testing the perl-Graphics-Magick package Regards Marco -- 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: cygwin 1.7.15: svn disk I/O error
marco atzeri gmail.com> writes: > a solution for testing is to add the new directory as first in the PATH. I think it already tries to do that, I'll have to check more closely if it's missing some directories or if the order is perhaps wrong. It may also be that the Ruby and Perl dynaloaders ignore the PATH settings in certain situations (at least the Perl dynaloader seems to map the library via an absolute path). It will be a while before I get to this, for now I'll just use the workaround of installing the untested libraries onto the build system before testing. Regards, Achim. -- 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: cygwin 1.7.15: svn disk I/O error
On 7/11/2012 8:33 AM, Achim Gratz wrote: David Rothenberger acm.org> writes: The tests work for me, but I've never been able to get them to work without first installing the newly built packages. After some more investigations, this is because the dynamic linker seems to use the libraries installed on the system rather than the ones in the build directory at least sometimes during the tests and if they are either not present or from a different version of svn things are falling apart. If I find a way to have it always use the newly built libraries instead (or at least the ones installed in $DESTDIR) I'll send a patch. Regards, Achim. a solution for testing is to add the new directory as first in the PATH. -- 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: cygwin 1.7.15: svn disk I/O error
David Rothenberger acm.org> writes: > The tests work for me, but I've never been able to get them to work > without first installing the newly built packages. After some more investigations, this is because the dynamic linker seems to use the libraries installed on the system rather than the ones in the build directory at least sometimes during the tests and if they are either not present or from a different version of svn things are falling apart. If I find a way to have it always use the newly built libraries instead (or at least the ones installed in $DESTDIR) I'll send a patch. Regards, Achim. -- 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: cygwin 1.7.15: svn disk I/O error
On 6/28/2012 2:35 PM, Achim Gratz wrote: I can't easily test this myself since I don't have TortoiseSVN installed Me, too, but it seems to me that there's a better way to find the problem than trying to replicate the problem reporters' exact environment. That's too complicated. The leading hypothesis explaining the problem is that there's a file locking problem between two programs both trying to access the same set of SQLite DB files. So, write two programs to do exactly that, and see if they will fight over the DB file or not. If they cooperate, as the SQLite FAQ says they should, then we're off in the weeds and someone needs to come up with a better hypothesis. If they fight, you then have two simple programs that, together, demonstrate the problem, which means you're much closer to finding a real fix that makes both sets of users happy. Take advantage of the fact that I'm a disinterested Cygwin package maintainer. You have some time to play with here. -- 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: cygwin 1.7.15: svn disk I/O error
David Rothenberger writes: > I make two packages, one for 5.10 and one for 5.14. There's a separate > patch that's required for 5.14. Did you include it? The source package > for -4 includes it automatically. Yes, I worked from the -4 package on one machine and the -3 package on the other. > There was a problem with the openldap-devel package at one point; it was > missing lots of things. I had to reinstall it to get the libraries. Then it was almost certainly this package, which is properly requested by the .cygport file. > The tests work for me, but I've never been able to get them to work > without first installing the newly built packages. The last time I did > this, I did: > > 1. Do "cygport *.cygport almostall" > 2. Install the packages. > 3. Rebase the dll and so files in */build and */inst > 4. Do "cygport *.cygport check" > > All the tests passed except for a Ruby test (it appeared the output came > in a different order than expected) and a few Perl tests (it couldn't > delete a temporary directory). Ah OK, I tried to do the tests without those packages installed. Thanks. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html -- 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: cygwin 1.7.15: svn disk I/O error
On 6/28/2012 10:37 AM, Rolf Campbell wrote: > On 2012-06-27 14:17, David Rothenberger wrote: >> Anyway, I'll have a new release available shortly built against the >> latest SQLite package, so others that want to use TortoiseSVN can try it. > > I just upgraded to the -5 package, and turned the TSVN icon caching back > on, and it very quickly failed in the same way as the -3 package. I'm sorry this isn't working for you, but as Subversion packager for Cygwin, I'm not planning to spend any time figuring out why. I have had problems with TortoiseSVN's icon cache and Cygwin Subversion for years and just came to the conclusion it had to be turned off. There is a reasonable work-around, tracking this down appears to be a lot of work, and I personally don't care. Sorry if that sounds rude; I just don't have the time, interest, or skills to work on this further. I'll be glad to do anything to help someone else track it down or include a patch to fix it. -- David Rothenberger daver...@acm.org mixed emotions: Watching a bus-load of lawyers plunge off a cliff. With five empty seats. -- 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: cygwin 1.7.15: svn disk I/O error
Warren Young writes: >> Now, if somebody could find out _where_ in SQLite it fails... > > Is it not true that you're the only one in many years of SQLite's > availability in Cygwin who wanted it compiled the way it currently is? Well yes, since one couldn't use temporary databases unless you have administrator rights. There may be a fix of this going through the Win32 interfaces as it were, but if there is, it's not easily spottable. > Since everyone else was apparently happy with it the way it was, and > the new way is causing problems, I'd say it's up to you to find the > fix before I give up and release the next version with the compilation > changes reverted. This is what I expect you to do and hence the frowny — yet another package that I have to locally patch. I can't easily test this myself since I don't have TortoiseSVN installed and as I said there's too many places where the error messages could come from, so I'm still hoping that someone can point to where exactly it's croaking in interaction with TortoiseSVN. > Put another way: I have two parties of users, both of whom claim > SQLite is giving them problems, one a group of size=1, and the other > group somewhat larger. I understand. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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: cygwin 1.7.15: svn disk I/O error
On 6/28/2012 1:11 PM, Achim Gratz wrote: Rolf Campbell writes: On 2012-06-27 14:17, David Rothenberger wrote: Anyway, I'll have a new release available shortly built against the latest SQLite package, so others that want to use TortoiseSVN can try it. I just upgraded to the -5 package, and turned the TSVN icon caching back on, and it very quickly failed in the same way as the -3 package. :-( Now, if somebody could find out _where_ in SQLite it fails... Is it not true that you're the only one in many years of SQLite's availability in Cygwin who wanted it compiled the way it currently is? Since everyone else was apparently happy with it the way it was, and the new way is causing problems, I'd say it's up to you to find the fix before I give up and release the next version with the compilation changes reverted. Put another way: I have two parties of users, both of whom claim SQLite is giving them problems, one a group of size=1, and the other group somewhat larger. -- 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: cygwin 1.7.15: svn disk I/O error
On 6/28/2012 12:04 PM, Achim Gratz wrote: > David Rothenberger writes: >>> I can't seem to get this working. There are a few warnings, but nothing >>> that >>> would explain such a massive fail. Would you mind posting the ldd output >>> for >>> your _Core.dll? >> >> % ldd /usr/lib/perl5/vendor_perl/5.10/i686-cygwin/auto/SVN/_Core/_Core.dll >> ntdll.dll => /c/Windows/SysWOW64/ntdll.dll (0x772f) > [...] >> cygsvn_diff-1-0.dll => /usr/bin/cygsvn_diff-1-0.dll (0x67df) >> ??? => ??? (0x77) > > Hmm. This is an installed version of the same library, not the one from > the build directory That's correct. I've cleaned up my build directory. I did try it from my build directory before, though, and there were no ???. > ... note also that I build for Perl 5.14 in case that > makes a difference. I make two packages, one for 5.10 and one for 5.14. There's a separate patch that's required for 5.14. Did you include it? The source package for -4 includes it automatically. > Any way, I think those "???" are a red herring, I've built on my home > machine and there it works, even though I have those "???" entries as > well (albeit in total much less lines, but this is a Win7/64 machine > vs. Win7/32bit at work and perl 5.10). The perl bindings work for me on Win7/64 using 5.10. I use them every day. >>> I was still missing a -devel package. Once installed, the Apache modules >>> build >>> and, more importantly link. >> >> Which -devel package was missing? cygport should have warned you >> about missing build dependencies. > > I updated some other packages (libserf) as well, so I don't know which > one it was exactly, but I think it might have been openldap-devel. > Interestingly enough it was the linking step that failed, not the > compilation, so the header files must already have been present via some > other package. There was a problem with the openldap-devel package at one point; it was missing lots of things. I had to reinstall it to get the libraries. > Gnome-keyring requires pkg-config during the configure step, not > requested by the cygport file. Thanks, I'll add that to the .cygport file. > Ruby tests are still failing because it looks for the extension > libraries in a different directory than where they really are. The tests work for me, but I've never been able to get them to work without first installing the newly built packages. The last time I did this, I did: 1. Do "cygport *.cygport almostall" 2. Install the packages. 3. Rebase the dll and so files in */build and */inst 4. Do "cygport *.cygport check" All the tests passed except for a Ruby test (it appeared the output came in a different order than expected) and a few Perl tests (it couldn't delete a temporary directory). -- David Rothenberger daver...@acm.org Ambiguity: Telling the truth when you don't mean to. -- 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: cygwin 1.7.15: svn disk I/O error
Rolf Campbell writes: > On 2012-06-27 14:17, David Rothenberger wrote: >> Anyway, I'll have a new release available shortly built against the >> latest SQLite package, so others that want to use TortoiseSVN can try it. > > I just upgraded to the -5 package, and turned the TSVN icon caching > back on, and it very quickly failed in the same way as the -3 package. :-( Now, if somebody could find out _where_ in SQLite it fails... Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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: cygwin 1.7.15: svn disk I/O error
David Rothenberger writes: >> I can't seem to get this working. There are a few warnings, but nothing that >> would explain such a massive fail. Would you mind posting the ldd output for >> your _Core.dll? > > % ldd /usr/lib/perl5/vendor_perl/5.10/i686-cygwin/auto/SVN/_Core/_Core.dll > ntdll.dll => /c/Windows/SysWOW64/ntdll.dll (0x772f) [...] > cygsvn_diff-1-0.dll => /usr/bin/cygsvn_diff-1-0.dll (0x67df) > ??? => ??? (0x77) Hmm. This is an installed version of the same library, not the one from the build directory... note also that I build for Perl 5.14 in case that makes a difference. Looking at the addresses from my library I know where cygwin1.dll is and it is already in a different place. I could look up all the other libraries in the rebase database to find what they are. I have no idea what the unresolved addresses above 0x7000 are and I see you also have one of these, so maybe this is normal. Anyway, I still don't know when and why ldd decides to show you "???" and if that relates to the problem with DynaLoader. Any way, I think those "???" are a red herring, I've built on my home machine and there it works, even though I have those "???" entries as well (albeit in total much less lines, but this is a Win7/64 machine vs. Win7/32bit at work and perl 5.10). >> I was still missing a -devel package. Once installed, the Apache modules >> build >> and, more importantly link. > > Which -devel package was missing? cygport should have warned you > about missing build dependencies. I updated some other packages (libserf) as well, so I don't know which one it was exactly, but I think it might have been openldap-devel. Interestingly enough it was the linking step that failed, not the compilation, so the header files must already have been present via some other package. Gnome-keyring requires pkg-config during the configure step, not requested by the cygport file. Ruby tests are still failing because it looks for the extension libraries in a different directory than where they really are. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: cygwin 1.7.15: svn disk I/O error
On 2012-06-27 14:17, David Rothenberger wrote: Anyway, I'll have a new release available shortly built against the latest SQLite package, so others that want to use TortoiseSVN can try it. I just upgraded to the -5 package, and turned the TSVN icon caching back on, and it very quickly failed in the same way as the -3 package. -- 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: cygwin 1.7.15: svn disk I/O error
On 6/28/2012 4:49 AM, Achim Gratz wrote: > Achim Gratz nexgo.de> writes: >>> Strange. It works for me and the ldd output for _Core.dll is reasonable. > > I can't seem to get this working. There are a few warnings, but nothing that > would explain such a massive fail. Would you mind posting the ldd output for > your _Core.dll? % ldd /usr/lib/perl5/vendor_perl/5.10/i686-cygwin/auto/SVN/_Core/_Core.dll ntdll.dll => /c/Windows/SysWOW64/ntdll.dll (0x772f) kernel32.dll => /c/Windows/syswow64/kernel32.dll (0x74ae) KERNELBASE.dll => /c/Windows/syswow64/KERNELBASE.dll (0x74c8) cygapr-1-0.dll => /usr/bin/cygapr-1-0.dll (0x6e8c) cygwin1.dll => /usr/bin/cygwin1.dll (0x6100) cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x6d6b) cyguuid-1.dll => /usr/bin/cyguuid-1.dll (0x67a4) cygssp-0.dll => /usr/bin/cygssp-0.dll (0x67f4) cygsvn_swig_perl-1-0.dll => /usr/bin/cygsvn_swig_perl-1-0.dll (0x67c4) cygsvn_delta-1-0.dll => /usr/bin/cygsvn_delta-1-0.dll (0x67e1) cygsvn_subr-1-0.dll => /usr/bin/cygsvn_subr-1-0.dll (0x67c5) cygaprutil-1-0.dll => /usr/bin/cygaprutil-1-0.dll (0x6e8a) cygcrypt-0.dll => /usr/bin/cygcrypt-0.dll (0x6e3e) cygexpat-1.dll => /usr/bin/cygexpat-1.dll (0x6da3) cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x69a9) cygintl-8.dll => /usr/bin/cygintl-8.dll (0x699a) cygmagic-1.dll => /usr/bin/cygmagic-1.dll (0x6953) cygz.dll => /usr/bin/cygz.dll (0x6765) cygsqlite3-0.dll => /usr/bin/cygsqlite3-0.dll (0x6803) CRYPT32.DLL => /c/Windows/syswow64/CRYPT32.DLL (0x7674) msvcrt.dll => /c/Windows/syswow64/msvcrt.dll (0x7686) MSASN1.dll => /c/Windows/syswow64/MSASN1.dll (0x74cd) cygperl5_10.dll => /usr/bin/cygperl5_10.dll (0x689f) cygsvn_diff-1-0.dll => /usr/bin/cygsvn_diff-1-0.dll (0x67df) ??? => ??? (0x77) >>> Yaakov's changes worked for me. > > I was still missing a -devel package. Once installed, the Apache modules > build > and, more importantly link. Which -devel package was missing? cygport should have warned you about missing build dependencies. -- David Rothenberger daver...@acm.org If you tell the truth you don't have to remember anything. -- Mark Twain -- 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: cygwin 1.7.15: svn disk I/O error
Achim Gratz nexgo.de> writes: > > Strange. It works for me and the ldd output for _Core.dll is reasonable. I can't seem to get this working. There are a few warnings, but nothing that would explain such a massive fail. Would you mind posting the ldd output for your _Core.dll? > > Yaakov's changes worked for me. I was still missing a -devel package. Once installed, the Apache modules build and, more importantly link. Regards, Achim. -- 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: cygwin 1.7.15: svn disk I/O error
David Rothenberger writes: > Strange. It works for me and the ldd output for _Core.dll is reasonable. What version of autotools, swig etc. are you using? The only swig wrappers that work for me are those for Python. Both Ruby and Perl seem to die on those strangely non-functional DLL the build has produced. Ruby had an additional problem: it was looking for the libraries in a directory .ext, but the build put them into .libs. A symlinked fixed that, but then the DLL could not be loaded anyway... > Yaakov's changes worked for me. Yes, there must be some difference in how the build got configured. Anyway, it seems that your new build will be available much faster than any attempt by me to find and fix those differences. > Anyway, I'll have a new release available shortly built against the > latest SQLite package, so others that want to use TortoiseSVN can try it. Thank you. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: cygwin 1.7.15: svn disk I/O error
On 6/27/2012 7:06 AM, Achim Gratz wrote: > Achim Gratz nexgo.de> writes: >> I'm not near my work machine, so this is from memory... the test suite >> requires perl modules I didn't have installed and fails most perl tests >> without them — not too worried about this, will install those later this >> week. > > The fail is not due to a module missing, but due to the perl dynaloader not > being able to load the DLL produced by the build. The error message is not > helpful as there's no reason given for why it couldn't load the DLL. The file > exists and is readable /executable. However, LDD gives strange output: Strange. It works for me and the ldd output for _Core.dll is reasonable. >> I've had to comment out the Apache module build since the mod_dav.la >> was nowhere to be found and no Cygwin package provides it. > > Even with the changes to the build config by Yaakov trying to build the Apache > module fails for me, now with unresolved symbols of the form "_dav_*". I've > built without mod_dav to work around that. Yaakov's changes worked for me. > Rebasing does help. Failing Perl tests aside (which never start due to the > issue outlined above), all further tests so far are pass. Judging from the > current progress, I'd think tests will run at least for two more hours. Yes, rebasing helped for me, too. The Ruby tests encountered fork failures, but everything else is working. I don't think this proves much, though. The errors I was getting in the past were fork failures and not the SQLite error being reported. Anyway, I'll have a new release available shortly built against the latest SQLite package, so others that want to use TortoiseSVN can try it. -- David Rothenberger daver...@acm.org It has long been an axiom of mine that the little things are infinitely the most important. -- Sir Arthur Conan Doyle, "A Case of Identity" -- 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: cygwin 1.7.15: svn disk I/O error
Achim Gratz nexgo.de> writes: > I'm not near my work machine, so this is from memory... the test suite > requires perl modules I didn't have installed and fails most perl tests > without them — not too worried about this, will install those later this > week. The fail is not due to a module missing, but due to the perl dynaloader not being able to load the DLL produced by the build. The error message is not helpful as there's no reason given for why it couldn't load the DLL. The file exists and is readable /executable. However, LDD gives strange output: # ldd subversion/bindings/swig/perl/native/blib/arch/auto/SVN/_Core/_Core.dll ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x772e) kernel32.dll => /cygdrive/c/Windows/system32/kernel32.dll (0x75c6) KERNELBASE.dll => /cygdrive/c/Windows/system32/KERNELBASE.dll (0x756b) ??? => ??? (0x587f) ??? => ??? (0x6c54) ??? => ??? (0x6100) ??? => ??? (0x6b1a) ??? => ??? (0x615e) ??? => ??? (0x61ad) ??? => ??? (0x617d) ??? => ??? (0x619a) ??? => ??? (0x617e) ??? => ??? (0x6c52) ??? => ??? (0x6be2) ??? => ??? (0x6b6a) ??? => ??? (0x6662) ??? => ??? (0x6503) ??? => ??? (0x64ca) ??? => ??? (0x6056) ??? => ??? (0x61bf) ??? => ??? (0x7559) ??? => ??? (0x771d) ??? => ??? (0x754a) > I've had to comment out the Apache module build since the mod_dav.la > was nowhere to be found and no Cygwin package provides it. Even with the changes to the build config by Yaakov trying to build the Apache module fails for me, now with unresolved symbols of the form "_dav_*". I've built without mod_dav to work around that. > The ephemeral rebase option I posted patches for in cygwin-apps should > help with that. Since I should have the same problem, I'll see that I > can adapt the cygport file to use it. Rebasing does help. Failing Perl tests aside (which never start due to the issue outlined above), all further tests so far are pass. Judging from the current progress, I'd think tests will run at least for two more hours. Regards, Achim. -- 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: cygwin 1.7.15: svn disk I/O error
Achim Gratz wrote: > David Rothenberger writes: > > I'm not sure that me running the test suite will prove much, so I'll > > make the rebuild available as a test release in case someone that was > > experiencing the problem would like to try it out. > > Thanks, that should help as well if the OP could check if it makes any > difference. I'm hitting the same problem (or, at least, my setup is similar to the OP's, and the thing that fixed it for me also fixed it for him), I'm certainly willing to test any new build. Adam
Re: cygwin 1.7.15: svn disk I/O error
David Rothenberger writes: > The cygport file should check for all required build dependencies. If > you find one missing, please let me know. I'm not near my work machine, so this is from memory... the test suite requires perl modules I didn't have installed and fails most perl tests without them — not too worried about this, will install those later this week. Also, the requires check for Berkeley-DB 4.2 and 4.5, but only 4.5 and 4.8 are currently offered by Cygwin. I've had to comment out the Apache module build since the mod_dav.la was nowhere to be found and no Cygwin package provides it. >> David Rothenberger, I'd appreciate if you could try to do another build >> of svn and tell us if there are any test regressions w.r.t to your last >> build. > > The point of the rebuild is to see if building against the latest > sqlite3 package fixes the problem? Either that or maybe whether the testsuite that comes with svn confirms the problem and thus delivers a debuggable testcase. > I can do a rebuild in the next few days. However, I have not been able > to get the test suite to run fully for quite a while due to rebase > problems. The ephemeral rebase option I posted patches for in cygwin-apps should help with that. Since I should have the same problem, I'll see that I can adapt the cygport file to use it. > Many tests use triggers and these often encounter fork > failures. I have never seen a SQLite error message in the test > failures, but I also don't have TortoiseSVN installed. (I removed it > long ago when the icon cache caused me problems.) If you still have a test log it might prove helpful. > I'm not sure that me running the test suite will prove much, so I'll > make the rebuild available as a test release in case someone that was > experiencing the problem would like to try it out. Thanks, that should help as well if the OP could check if it makes any difference. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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: cygwin 1.7.15: svn disk I/O error
On 6/26/2012 9:45 AM, Achim Gratz wrote: > Achim Gratz writes: > I've tried to re-build svn against the new SQLite library, but I'm not > sure if that works correctly on my machine (the tests are still runnning > and I get some test failures already since apparently I'm still missing > some dependencies). However, I don't have TortoiseSVN installed anyway. The cygport file should check for all required build dependencies. If you find one missing, please let me know. > David Rothenberger, I'd appreciate if you could try to do another build > of svn and tell us if there are any test regressions w.r.t to your last > build. The point of the rebuild is to see if building against the latest sqlite3 package fixes the problem? I can do a rebuild in the next few days. However, I have not been able to get the test suite to run fully for quite a while due to rebase problems. Many tests use triggers and these often encounter fork failures. I have never seen a SQLite error message in the test failures, but I also don't have TortoiseSVN installed. (I removed it long ago when the icon cache caused me problems.) I'm not sure that me running the test suite will prove much, so I'll make the rebuild available as a test release in case someone that was experiencing the problem would like to try it out. -- David Rothenberger daver...@acm.org "Daddy, Daddy, make Santa Claus go away!" "I can't, son; he's grown too powerful." "HO HO HO!" -- Duck's Breath Mystery Theatre -- 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: cygwin 1.7.15: svn disk I/O error
Achim Gratz writes: > Cygwin should (and apparently does) abstract away that difference. But > it seems that the locking strategy might be slightly different between > Win32 and POSIX, triggering a foray into that "disk I/O error" branch. > There may still be a bug some place else, i.e. it may get a timeout > rather than a "file locked" state. I'll have a look when I find some > time. I've had a look at the sources and those two error messages are with near certainty generated by SQLite. Unfortunately there are many places where they could be generated, it would certainly help if it could be traced where exactly in SQLite this is happening (must be at least two places, maybe more). I've tried to re-build svn against the new SQLite library, but I'm not sure if that works correctly on my machine (the tests are still runnning and I get some test failures already since apparently I'm still missing some dependencies). However, I don't have TortoiseSVN installed anyway. David Rothenberger, I'd appreciate if you could try to do another build of svn and tell us if there are any test regressions w.r.t to your last build. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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: cygwin 1.7.15: svn disk I/O error
Warren Young writes: >> Note that SQLite isn't really designed for concurrent access >> to the database file from a different process. > > There is a paucity of truth in that statement. So let me re-formulate that sentence: concurrent access ultimately relies on the file locking provided by the OS. The concurrency support in SQLite is simply to not keep state outside a critical section and lock the database file exclusively when entering one. > But, there's only so much SQLite can do to cooperate with the OS's > locking strategy. On POSIX systems where SQLite was born, locking is > mostly advisory and cooperative, whereas Windows gives you mandatory > locks by default in a lot of cases. Mandatory locks allow one process > (e.g. TortoiseSVN) to deny another (e.g. Cygwin svn) the ability to > change a file, indefinitely. Cygwin should (and apparently does) abstract away that difference. But it seems that the locking strategy might be slightly different between Win32 and POSIX, triggering a foray into that "disk I/O error" branch. There may still be a bug some place else, i.e. it may get a timeout rather than a "file locked" state. I'll have a look when I find some time. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: cygwin 1.7.15: svn disk I/O error
On 6/19/2012 3:18 PM, Achim Gratz wrote: I suspect that svn does not deal with the file being locked exclusively (when TortoiseSVN accesses the database) and some call through the windows interface blocked. It's possible svn has a timer on the call that results in a SQL call through SQLite, and when this doesn't return as fast as svn thinks it ought to, it bombs out, complaining that there "must" be a disk I/O problem. What may actually be happening is that Windows' aggressive locking strategy has set up a deadlock between two processes. As for why .3 and .12 behave differently, it's probably because one or more locks that used to be owned by the SQLite DLL that are now owned by the Cygwin DLL. That is, files are being accessed on the DLL's behalf by Cygwin now, rather than directly through the Windows API. Since Cygwin doubtless does file I/O differently than SQLite did, for the same basic reason that any two programmers tend to write code differently, there's a new conflict. If this is the case, the best solution may be for TortoiseSVN to stop grabbing files for long-term exclusive use. It should only be locking the svn DB files as long as is necessary to make some change. Note that SQLite isn't really designed for concurrent access to the database file from a different process. There is a paucity of truth in that statement. See the SQLite FAQ: https://sqlite.org/faq.html#q5 But, there's only so much SQLite can do to cooperate with the OS's locking strategy. On POSIX systems where SQLite was born, locking is mostly advisory and cooperative, whereas Windows gives you mandatory locks by default in a lot of cases. Mandatory locks allow one process (e.g. TortoiseSVN) to deny another (e.g. Cygwin svn) the ability to change a file, indefinitely. -- 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: cygwin 1.7.15: svn disk I/O error
Rolf Campbell writes: > I would hate to add TortoiseSVN to the BLODA. The icon cache _is_ dodgy — at least the one for TortoiseGit, which needs to be restarted regularly. But getting back to SQLite, backing out the changes in the build would get us back a different bug. So it would be very interesting if you could debug where it hits that roadblock in svn. I suspect that svn does not deal with the file being locked exclusively (when TortoiseSVN accesses the database) and some call through the windows interface blocked. Note that SQLite isn't really designed for concurrent access to the database file from a different process. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html -- 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: cygwin 1.7.15: svn disk I/O error
On 2012-06-19 05:29, Adam Dinwoodie wrote: Rolf Campbell wrote: $ svn up Updating '.': svn: E200030: disk I/O error, executing statement 'RELEASE s6' svn: E200030: sqlite: unable to open database file svn: E200030: sqlite: unable to open database file $ svn cleanup svn: E200030: disk I/O error, executing statement 'RELEASE s79' I've had the same problem, and have found a solution: this appears for me to be an interaction with TortoiseSVN, which I have on my machine and which is entirely unaware of Cygwin. Disabling TortoiseSVN's icon cache has completely resolved the issue for me. You can do this by running TortoiseSVN's Settings program, going to "Icon Overlays", and selecting "None" under "Status cache", then hitting Apply. That may explain why Rolf's been hitting this despite apparently having no AV installed. Adam That's a very interesting discovery. I certainly am using TortoiseSVN. There must be some interaction between the most recent version of sqlite and TortoiseSVN's status scanner. I've been playing around with sqlite versions and I've confirmed what others have stated that it's only a problem with v3.7.12.1 and NOT a problem with v3.7.3. I've upgraded back to v3.7.12.1 and disabled TortoiseSVN's icon scanner. It appears to resolve the problem for me as well. I would hate to add TortoiseSVN to the BLODA. -- 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: cygwin 1.7.15: svn disk I/O error
Rolf Campbell wrote: > Recently, I've noticed cygwin svn getting a LOT of errors during > operations. I think this started when upgrading from 1.7.14 to 1.7.15, > but I can't say for sure. The nature of these errors are as follows: > > $ svn up > Updating '.': > svn: E200030: disk I/O error, executing statement 'RELEASE s6' > svn: E200030: sqlite: unable to open database file > svn: E200030: sqlite: unable to open database file > > > $ svn cleanup > svn: E200030: disk I/O error, executing statement 'RELEASE s79' > > > I've had the same problem, and have found a solution: this appears for me to be an interaction with TortoiseSVN, which I have on my machine and which is entirely unaware of Cygwin. Disabling TortoiseSVN's icon cache has completely resolved the issue for me. You can do this by running TortoiseSVN's Settings program, going to "Icon Overlays", and selecting "None" under "Status cache", then hitting Apply. That may explain why Rolf's been hitting this despite apparently having no AV installed. Adam -- 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: cygwin 1.7.15: svn disk I/O error
On 2012-06-15 06:37, Warren Young wrote: It is indeed AV related -- a race between SQLite and AV That's one possibility, but check this out: http://stackoverflow.com/questions/11007024/ tl;dr: someone made the problem go away by rolling my recent 3.7.12 release back to the prior 3.7.3 version. I doubt the problem is in the upstream changes between .3 and .12. I'm more worried about the build option changes. SQLite has a lot of Windows-specific code in it, plus some Cygwin-specific code, too. The build changes override some things to force it to believe it's being built for a more generic POSIX type system. It may be both things: the build option changes that force more I/O calls to go through Cygwin instead of direct to the Win32 API could be tickling BLODA bugs. Yet another possibility is that the build option changes cause a subtle ABI change that will be fixed when SVN is rebuilt against it. I've rolled my machine back to to .3 and I'll see if it fixes my system too. Unfortunately, I'm not able to reproduce the problem *at all* this morning with any version of anything. I guess I'll wait and see for now. -- 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: cygwin 1.7.15: svn disk I/O error
On 2012-06-15 06:37, Warren Young wrote: On 6/14/2012 4:00 PM, Garrison, Jim (ETW) wrote: Why would you think that a disk I/O error was either anti-virus or Cygwin related and not... a disk I/O error? Have you looked in your event logs for errors? It is indeed AV related -- a race between SQLite and AV That's one possibility, but check this out: http://stackoverflow.com/questions/11007024/ tl;dr: someone made the problem go away by rolling my recent 3.7.12 release back to the prior 3.7.3 version. I doubt the problem is in the upstream changes between .3 and .12. I'm more worried about the build option changes. SQLite has a lot of Windows-specific code in it, plus some Cygwin-specific code, too. The build changes override some things to force it to believe it's being built for a more generic POSIX type system. It may be both things: the build option changes that force more I/O calls to go through Cygwin instead of direct to the Win32 API could be tickling BLODA bugs. Yet another possibility is that the build option changes cause a subtle ABI change that will be fixed when SVN is rebuilt against it. Also, I don't think I'm running any A/V software (Windows keeps nagging me that my system is *not* running A/V). I uninstalled it to see if that was the problem before reporting it to this list. Also#2: I'm seeing this problem on a Win7x64 machine, but I also have a WinXPx32 machine which has started exhibiting the same symptoms. That one *is* running Symantec A/V (which I've never had trouble with before). It's a work machine, and I don't have permissions to uninstall A/V, but I'll see if I can convince the IT guy to uninstall it for a while to see if that resolves the problem. -- 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: cygwin 1.7.15: svn disk I/O error
On 6/14/2012 4:00 PM, Garrison, Jim (ETW) wrote: Why would you think that a disk I/O error was either anti-virus or Cygwin related and not... a disk I/O error? Have you looked in your event logs for errors? It is indeed AV related -- a race between SQLite and AV That's one possibility, but check this out: http://stackoverflow.com/questions/11007024/ tl;dr: someone made the problem go away by rolling my recent 3.7.12 release back to the prior 3.7.3 version. I doubt the problem is in the upstream changes between .3 and .12. I'm more worried about the build option changes. SQLite has a lot of Windows-specific code in it, plus some Cygwin-specific code, too. The build changes override some things to force it to believe it's being built for a more generic POSIX type system. It may be both things: the build option changes that force more I/O calls to go through Cygwin instead of direct to the Win32 API could be tickling BLODA bugs. Yet another possibility is that the build option changes cause a subtle ABI change that will be fixed when SVN is rebuilt against it. -- 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: cygwin 1.7.15: svn disk I/O error
> -Original Message- > Subject: RE: cygwin 1.7.15: svn disk I/O error > > > -Original Message- > > Subject: Re: cygwin 1.7.15: svn disk I/O error > > > > On Thu, Jun 14, 2012 at 03:48:05PM -0400, Rolf Campbell wrote: > > >Recently, I've noticed cygwin svn getting a LOT of errors during > > >operations. I think this started when upgrading from 1.7.14 to > > >1.7.15, but I can't say for sure. The nature of these errors are as > follows: > > > > > >$ svn up > > >Updating '.': > > >svn: E200030: disk I/O error, executing statement 'RELEASE s6' > > >svn: E200030: sqlite: unable to open database file > > >svn: E200030: sqlite: unable to open database file > > > > > > > > >$ svn cleanup > > >svn: E200030: disk I/O error, executing statement 'RELEASE s79' > > > > > > > > >Sometimes the errors happen, sometimes not. It seems to be about 50% > > >of the time svn has this type of error now. I've tried running the > > >exact same version of SVN (the command-line version shipped with > > >TourtoiseSVN) on the exact same working copies and I don't have any > > errors. > > > > > >I'm not running any anti-virus (I was, but I uninstalled it a couple > > >of days ago to make sure it wasn't causing this trouble). > > > > Why would you think that a disk I/O error was either anti-virus or > > Cygwin related and not... a disk I/O error? Have you looked in your > > event logs for errors? > > > It is indeed AV related -- a race between SQLite and AV > > http://mail-archives.apache.org/mod_mbox/subversion- > users/201204.mbox/%3CE3F0AE62D06F6C42ACF59588421A2CC50F66713D@DEFTHW99E5 > 4MSX.ww902.siemens.net%3E > > I just ran into this and got around it by temporarily disabling AV See also this thread http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2906294 -- 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: cygwin 1.7.15: svn disk I/O error
> -Original Message- > Subject: Re: cygwin 1.7.15: svn disk I/O error > > On Thu, Jun 14, 2012 at 03:48:05PM -0400, Rolf Campbell wrote: > >Recently, I've noticed cygwin svn getting a LOT of errors during > >operations. I think this started when upgrading from 1.7.14 to 1.7.15, > >but I can't say for sure. The nature of these errors are as follows: > > > >$ svn up > >Updating '.': > >svn: E200030: disk I/O error, executing statement 'RELEASE s6' > >svn: E200030: sqlite: unable to open database file > >svn: E200030: sqlite: unable to open database file > > > > > >$ svn cleanup > >svn: E200030: disk I/O error, executing statement 'RELEASE s79' > > > > > >Sometimes the errors happen, sometimes not. It seems to be about 50% > >of the time svn has this type of error now. I've tried running the > >exact same version of SVN (the command-line version shipped with > >TourtoiseSVN) on the exact same working copies and I don't have any > errors. > > > >I'm not running any anti-virus (I was, but I uninstalled it a couple of > >days ago to make sure it wasn't causing this trouble). > > Why would you think that a disk I/O error was either anti-virus or > Cygwin related and not... a disk I/O error? Have you looked in your > event logs for errors? It is indeed AV related -- a race between SQLite and AV http://mail-archives.apache.org/mod_mbox/subversion-users/201204.mbox/%3ce3f0ae62d06f6c42acf59588421a2cc50f667...@defthw99e54msx.ww902.siemens.net%3E I just ran into this and got around it by temporarily disabling AV -- 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: cygwin 1.7.15: svn disk I/O error
On 2012-06-14 15:55, Christopher Faylor wrote: On Thu, Jun 14, 2012 at 03:48:05PM -0400, Rolf Campbell wrote: $ svn cleanup svn: E200030: disk I/O error, executing statement 'RELEASE s79' Sometimes the errors happen, sometimes not. It seems to be about 50% of the time svn has this type of error now. I've tried running the exact same version of SVN (the command-line version shipped with TourtoiseSVN) on the exact same working copies and I don't have any errors. I'm not running any anti-virus (I was, but I uninstalled it a couple of days ago to make sure it wasn't causing this trouble). Why would you think that a disk I/O error was either anti-virus or Cygwin related and not... a disk I/O error? Have you looked in your event logs for errors? cgf I thought it might be anti-virus related because I read another message about someone having a similar problem and he thought it might be anti-virus related. But now I can't find where I was reading that message anymore. Anyway, another reason is because I only experience this error when I use the cygwin version of SVN. Other versions do not run into any errors when accessing the exact same working copies. I just checked my event logs and I don't see any system errors related to I/O. The only error today is about failing to start the PBADRV service. -- 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: cygwin 1.7.15: svn disk I/O error
On Thu, Jun 14, 2012 at 03:48:05PM -0400, Rolf Campbell wrote: >Recently, I've noticed cygwin svn getting a LOT of errors during >operations. I think this started when upgrading from 1.7.14 to 1.7.15, >but I can't say for sure. The nature of these errors are as follows: > >$ svn up >Updating '.': >svn: E200030: disk I/O error, executing statement 'RELEASE s6' >svn: E200030: sqlite: unable to open database file >svn: E200030: sqlite: unable to open database file > > >$ svn cleanup >svn: E200030: disk I/O error, executing statement 'RELEASE s79' > > >Sometimes the errors happen, sometimes not. It seems to be about 50% of >the time svn has this type of error now. I've tried running the exact >same version of SVN (the command-line version shipped with TourtoiseSVN) >on the exact same working copies and I don't have any errors. > >I'm not running any anti-virus (I was, but I uninstalled it a couple of >days ago to make sure it wasn't causing this trouble). Why would you think that a disk I/O error was either anti-virus or Cygwin related and not... a disk I/O error? Have you looked in your event logs for errors? cgf -- 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
