You are here: Home » Reply

Reply To: Nightly build for NSLU2

#3919

UncleOp22
Participant

So I did “ipkg remove” for both mt-daapd and sqlite and sqlite3. Then I reinstalled, based on the nightly ipkg:

# ipkg install mt-daapd_cvs-20060116-1_armeb.ipk
Installing mt-daapd (cvs-20060116-1) to root...
Installing sqlite2 (2.8.16-1) to root...
Downloading http://ipkg.nslu2-linux.org/feeds/unslung/cross/sqlite2_2.8.16-1_armeb.ipk
Configuring mt-daapd



To complete this installation, make any necessary changes
to the config file in /opt/etc/mt-daapd/mt-daapd.conf, and
start the daemon by running /opt/etc/init.d/S60mt-daapd

Configuring sqlite2

# sqlite -version
2.8.16

I then goofed and forgot to enable the logfile before starting, but the slug is definitely busy. So it looks like for slugs the nightlies prefer sqlite 2, but I saw fer shur that my prior attempt put up version 3.2.8-1. I’m a little confused, but things seem to be up for now.

So, are there any pitfalls I should be aware of based on the sql version differences? (Or should I just go read the diffs in CVS?)

Oh, and joy! It seems that my old smart playlists, from before the “ipkg remove” steps above, are still there, so I guess my old DB didn’t get completely nuked. Another intentional artifact?