From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: sqlite defect
Date: Fri, 12 Jul 2013 20:09:00 -0000 [thread overview]
Message-ID: <51E0571D.1060003@acm.org> (raw)
In-Reply-To: <trinity-fdc5a0b5-6dcf-4fc0-9370-dd32a75fe928-1373654994500@3capp-gmx-bs47>
These kinds of questions belong on the main mailing list. Responding
there.
fger555@gmx.de wrote:
> I never had problems with sqlite before.
>
> But since 3.7.17-3 I cannot read my databases any more
> "unable to open datase file". I remember there was a discussion
> on the cygwin general mailing list about this problem
> (backslashes in path?).
Please provide more specifics about the error and how to cause it. I
use SVN on a daily basis in both 32-bit and 64-bit Cygwin and have
no troubles whatsoever.
You should also read and follow the instructions here:
http://cygwin.com/problems.html.
> Is there a solution for this bug.
> Or could you switch back to the working version again,
> with all the dependencies, as a workaround?
I will not be re-rolling SVN against a prior SQLite release. We'll
have to figure out what's causing the problem in your environment.
--
David Rothenberger ---- daveroth@acm.org
English literature's performing flea.
-- Sean O'Casey on P. G. Wodehouse
--
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
next parent reply other threads:[~2013-07-12 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-fdc5a0b5-6dcf-4fc0-9370-dd32a75fe928-1373654994500@3capp-gmx-bs47>
2013-07-12 20:09 ` David Rothenberger [this message]
[not found] ` <51E703FB.1010300@etr-usa.com>
[not found] ` <trinity-1068d666-3dec-43c9-8453-39c7cae3a94c-1374102947415@3capp-gmx-bs33>
2013-07-18 3:27 ` Warren Young
2013-07-18 9:39 ` jojelino
2013-07-18 10:43 ` Corinna Vinschen
2013-07-19 7:55 ` jojelino
2013-07-19 10:08 ` Corinna Vinschen
2013-07-19 11:30 ` Corinna Vinschen
2013-07-19 11:41 ` jojelino
2013-07-19 11:53 ` Corinna Vinschen
2013-07-19 12:02 ` jojelino
2013-07-19 12:36 ` Corinna Vinschen
2013-07-19 12:57 ` jojelino
2013-07-19 12:58 ` jojelino
2013-07-19 14:26 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51E0571D.1060003@acm.org \
--to=daveroth@acm.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).