Summary: | squeezecenter 7.2.0 compiles fine but does not start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karel De Vriendt <kdvgent> |
Component: | Current packages | Assignee: | Joe Peterson (RETIRED) <lavajoe> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | stuart |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Karel De Vriendt
2008-09-02 04:25:20 UTC
P.S.: I have exactly the same problem with squeezecenter 7.1.0 - leaving no working ebuild availalbe any more. Are you sure your database (mysql) is set up properly? I cannot reproduce this problem. I am copying Stuart to see if it looks familiar to him. I had a working squeezecenter 7.0.1 installation. Using a suggestion from the Squeezebox support forums I deleted my mysql database and recreated one using emerge --config =media-sound/squeezecenter-7.2.0. Things work OK now. Should I "by default" recreate my database after every update (on the squeezebox website, it is said that one must uninstall before installing a new version but doing so of course would not remove the database)? Thanks for your help. Thanks for the report on how you "fixed" it. I am not sure if this should be required in general. Stuart might have a comment on this. You may want to ask this specifically on the forums to see what they say about it (i.e. is it "expected" that the DB needs to be recreated). Even if yes, I suspect it could only apply when upgrading from specific older versions that had a different DB format or something. Marking this as resolved - please reopen if there is still an ebuild-related issue. There shouldn't be a problem in the future. Between the Portage ebuild for SqueezeCenter 7.0.1 and 7.0.2 we moved the location of the SqueezeCenter preferences file. The preference file includes the database connection information which is why your new 7.2.0 installation couldn't connect to the database - it had lost the password used to connect. The easiest end-user fix is to re-do the 'config' step which recreates that preferences file and password, but it also wipes your database in the process. We shouldn't be moving that preferences file in the future so you'll be able to take the latest ebuild without having to reset your database and rescan your collection. Sorry for the inconvenience. I posted a comment about this issue with the announcement for the 7.0.2 version (http://forums.slimdevices.com/showthread.php?t=48131), but if you skipped a few versions you may not have realised that it still applies. |