This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Promote sqlite 3.7.13-1 from test status?
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Mon, 11 Feb 2013 22:49:17 +0000
- Subject: Re: Promote sqlite 3.7.13-1 from test status?
- References: <announce.5029275C.4040009@etr-usa.com> <502C0B7D.10909@etr-usa.com> <loom.20120816T092134-266@post.gmane.org> <20120816085016.GB5536@calimero.vinschen.de> <502CCBB1.2070600@etr-usa.com> <20120816105507.GD17546@calimero.vinschen.de> <502CE120.4050900@etr-usa.com> <20120816122654.GG17546@calimero.vinschen.de> <502D1967.7090705@etr-usa.com> <20120816160656.M21257@ds.net> <502D3A5C.7010500@etr-usa.com> <00ad01cd7bf6$7cc68a50$76539ef0$@motionview3d.com> <1345169297.10004.10.camel@YAAKOV04> <87k3qmedzh.fsf@Rainer.invalid> <51194F7F.8050403@etr-usa.com> <87halio886.fsf@Rainer.invalid> <511967DD.8030600@etr-usa.com>
On 11/02/13 21:51, Warren Young wrote:
As I saw it, I released some test builds, they caused a new problem,
I'm not sure you introduced a new problem - Subversion's 'bdb' tests
were locking up on both the .13 and .15 builds. Achim thought that this
might be to do with the version of BerkeleyDB being used:
http://cygwin.com/ml/cygwin/2013-01/msg00285.html
Doing a quick Google, other people have questioned the suitability of
Berkeley as a svn back-end:
http://stackoverflow.com/questions/601348/berkeleydb-vs-tokyo-cabinet/601365#601365
So it's entirely possible that this problem is nothing to do with SQLite.
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