Hi:
I can’t get typo gem installation success.
In a debian, I have installed:
ruby1.8
ruby1.8-dev
rdoc1.8.2-1
gems 0.9.2
When running ‘typo install some_dir’ it don’t pass the tests:
copying rails 1.1.6 to /home/lumen/tmp/some_dir/vendor/rails/railties
copying activesupport 1.3.1 to
/home/lumen/tmp/some_dir/vendor/rails/activesupport
copying activerecord 1.14.4 to
/home/lumen/tmp/some_dir/vendor/rails/activerecord
copying actionpack 1.12.5 to
/home/lumen/tmp/some_dir/vendor/rails/actionpack
copying actionmailer 1.2.5 to
/home/lumen/tmp/some_dir/vendor/rails/actionmailer
copying actionwebservice 1.1.6 to
/home/lumen/tmp/some_dir/vendor/rails/actionwebservice
Making scripts executable
Checking database
Creating initial database
expanding apache20.conf.example template
expanding lighttpd.conf.example template
expanding apache13.conf.example template
Migrating Typo’s database to newest release
Cleaning out Typo’s cache
Running tests. This may take a minute or two
***** Tests failed *****
** Please run ‘rake test’ by hand in your install directory.
** Report problems to the Typo mailing list.
***** Tests failed *****
Starting Typo on port 4740
Typo is now running on http://suyilinux:4740
Use ‘typo start /home/lumen/tmp/some_dir’ to restart after boot.
Look in installer/*.conf.example to see how to integrate with your web
server.
When running ‘rake test:units’ I get a lot of errors of type:
test_sha1(UserTest):
SQLite3::SQLException: SQL logic error or missing database
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/errors.rb:94:in
check' /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/resultset.rb:76:in check’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/resultset.rb:68:in
commence' /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/resultset.rb:61:in initialize’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/statement.rb:163:in
new' /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/statement.rb:163:in execute’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/database.rb:212:in
execute' /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/database.rb:187:in prepare’
/usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/database.rb:211:in
execute' /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/database.rb:621:in rollback’
/home/lumen/tmp/some_dir/config/…/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:183:in
rollback_db_transaction' /home/lumen/tmp/some_dir/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:329:in catch_schema_changes’
/home/lumen/tmp/some_dir/config/…/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:183:in
rollback_db_transaction' /home/lumen/tmp/some_dir/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:533:in teardown’
This typo of errors only dissapear if I switch off the “in memory
database” feature, and create the corresponding database (and
database.yml).
Tested in two different machines.
Any help?