rpedde wrote:
If you install the .ipk, it should notice that you don’t have sqlite 3.x and install it automagically.
that’s the theory, anyway. If it fails, I’d like to hear about it. If it does, you can try manually installing the sqlite3 libs (ipkg install sqlite).
The install went OK, once I did a “ipkg update”.
Got yer run-time errors right here:
2006-01-16 21:14:58: Starting rendezvous daemon
2006-01-16 21:14:58: Starting signal handler
2006-01-16 21:14:59: Can't get db version. New database?
2006-01-16 21:14:59: Initializing database
2006-01-16 21:14:59: Full reload...
2006-01-16 21:14:59: Starting mp3 scan of /share/hdd/data/nathan/nathan/music/ogg
2006-01-16 21:14:59: Query: pragma synchronous = off
2006-01-16 21:14:59: Error: file is encrypted or is not a database
2006-01-16 21:14:59: Aborting
2006-01-16 21:14:59: Rendezvous socket closed (daap server crashed?) Aborting.
2006-01-16 21:14:59: Aborting
That’s all that’s in the log file with the default logging level.
My install went like this:
# ipkg install mt-daapd_cvs-20060116-1_armeb.ipk
Upgrading mt-daapd on root from cvs-20051122-1 to cvs-20060116-1...
Installing sqlite (3.2.8-1) to root...
Downloading http://ipkg.nslu2-linux.org/feeds/unslung/cross/sqlite_3.2.8-1_armeb.ipk
Configuration file '/opt/etc/mt-daapd/mt-daapd.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions (if diff is installed)
The default action is to keep your current version.
*** mt-daapd.conf (Y/I/N/O/D) [default=N] ?YAnd then I hand-edited the mt-daapd.conf file to include my changes (new admin pw, log file on, 3600 second refresh).
I’ll dig around more. Happy for hints if you think of them first.