Bugzilla – Bug 6634
outdated version of Template::Toolkit required
Last modified: 2009-07-31 10:16:12 UTC
starting server manually... [08-01-17 09:56:05.3677] Slim::bootstrap::tryModuleLoad (266) Warning: Module [Template::Stash::XS] failed to load: Couldn't load Template::Stash::XS 2.15: ok... sudo cpan Template::Stash 5 minutes later [08-01-17 10:10:22.1163] Slim::bootstrap::tryModuleLoad (266) Warning: Module [Template::Stash::XS] failed to load: Couldn't load Template::Stash::XS 2.15: Template::Stash::XS object version 2.19 does not match bootstrap parameter 2.15 at /usr/local/lib/perl5/5.8.8/darwin-2level/DynaLoader.pm line 253. What gives? (btw, I ended up with sudo cpan install A/AB/ABW/Template-Toolkit-2.15.tar.gz
How are you running SC? How did you install? You shouldn't need to install any additional perl packages, they are installed with SC if required. Did you download and run the *noCPAN.tgz file?
installed from dmg, clicked 'start server' in control panel; the button goes inactive for a few seconds, then resets to 'start server' title again (so server fails to start). So cd /Library/PreferencePanes/SqueezeCenter/Contents/server ./slimserver.pl and then I see the above errors. This was on a G5 mac tower with OS X 10.4.11 installed.
Just to be sure: did you have any other version installed before? Could you try re-downloading the latest release? You definitely should _not_ need to install any additional modules when installing from the .dmg file. QA - can you reproduce this?
I had 6.5.4 installed before. Still, my main question wasn't "why do I have to manually install a module" (though that's a good question too), but rather "Why are you using Template::Stash::XS 2.15 when 2.19 is available, and shouldn't that be changed?"
A bug tracker is not to ask why we do something a certain way, but to report bugs. Please open a thread in the forums for discussions. Thanks. As for your question: SC is a complex application. Updating always carry the risk of introducing new issues. If a version is running flawlessly and more recent versions only fix minor bugs unimportant to an application, there's no need taking the risk. If it ain't broke, don't fix it.
Well, shouldn't installing a new version install any new required modules? Someone should try upgrading and see if they get the same issue. One would expect software to just work when installing it or upgrading it, right?
In your previous post you said: > my main question wasn't "why do I have to manually install a module" Thus I assumed you didn't need to. But the issue of having to load stuff manually is covered in bug 6633 anyway. Please continue over there. Thanks.
Reduce number of active targets for SC