For the mt-daap issues all these seems to be related to the following criteria:
* The update was run "by hand" and the new mt-daapd config file was not installed. Since the ownership of the database was changed running the service as mt-daap does not work.
The fix to this is to change the "runas" parameter to say "www-data" instead of "mt-daap".
* In the process of testing, removing the database will cause it to be rebuilt by the user running the mt-daapd service. So if the database was removed and the service started again as "mt-daap" it will be recreated by that user with permissions for that user. In this case when changing the "runas" parameter, the database file needs to be removed again, since it was now created by "mt-daap".
I hope that this makes some sence for you....
/PA
