Jon Lambert
- Login: Tyche
- Registered on: 2009-11-19
- Last connection: 2011-05-02
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 4 | 4 |
Activity
2011-04-28
-
05:49 Redmine Defect #8182: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- There is no superuser on Cygwin.
2011-04-27
-
02:31 Redmine Defect #8182: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- ...
2011-04-20
-
03:39 Redmine Defect #8182: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- ...
2011-04-19
-
22:34 Redmine Defect #8182: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- There is no running server yet.
I have full access access.
I'm running the "RAILS_ENV=production rake db:migrate ... -
02:28 Redmine Defect #8182 (Closed): SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- Checked out current head......
-
01:34 Redmine Defect #8178: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- Interesting post above. Do you have problems with bots using redmine? ;-)
Anyway I've hopefully verified that the...
2011-04-18
-
23:10 Redmine Defect #8178: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- I'm following the new installation instructions, not trying to update.
Before I issue the command...
RAILS_ENV=... -
23:06 Redmine Defect #8178: SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- I'm following the new installation instructions, not trying to update.
Before I issue the command...... -
19:23 Redmine Defect #8178 (Closed): SQLite3::CantOpenException: unable to open database file: DROP TABLE "issue_histories"
- Failure in DB migration during installation
About your application's environment
Ruby version 1.8.7 ... -
19:29 Redmine Defect #6164: email not working
- > Did you manage to resolve your problem ?
No.
> BTW, email.yaml should be named email.yml, isn't it ?
It is...
Also available in: Atom