Hi,
I'm a happy Tracks user on Linux and as I like to live on the edge, I
run the "trunk" version so I get to test the new functionnalities :)
It happens that, as Tracks is now based on Ruby on Rails 1.2.x, it hits
a serious bug if it used on conjunction with some old version of
sqlite3-ruby. To be more precise:
* If you're running a version of Sqlite3 greater than or equal to
3.3.8, then you must *not* use sqlite3-ruby version 1.1.0.
* The solution is to use sqlite3-ruby version *1.2.x *(1.2.1 today).
It is a blocking bug as it may corrupt an existing database if it is
opened with an old sqlite3-ruby library, and it totally prevents the
creation of a fresh database. and of course it prevent the use of any
RoR/sqlite3 application as well.
I have opened a bug report for Debian,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418416, and it has been
solved in the unstable version of Debian only. Unfortunately, the
following stable distributions still provied the old *1.1.0*
sqlite3-ruby library, and therefore cannot run Tracks devel at all:
* Debian Etch (4.0)
* Ubuntu Feisty Fawn (7.04)
In the meantime, until theses 2 distribution upgrade their library,
suppressing the official Debian/Ubuntu libsqlite3-ruby and
libsqlite3-ruby1.8 packages and replacing them with the Gem provided
version solves this problem cleanly.
Could you please add some information in the Readme/Installation files
so as to inform users/tests of this serious potential problem and
include my recommendations?
Regards,
--
Farzad FARID / Architecte Open Source - Associé
Pragmatic Source / http://www.pragmatic-source.com
Tel : +33 9 53 19 21 90 / Mob : +33 6 03 70 65 46
Rejoignez mon réseau de contacts :
http://www.viadeo.com/invitationpersonnelle/002ic6twokcvmi
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
