Perl mod mismatch in squeezeboxserver-7.5.1-30836 (using OpenSolaris)

[Blue_Atom]

Just a heads up, but when I upgraded from 7.5.0 to 7.5.1 I got an error from the Array.pm module;

Undefined subroutine &Class::XSAccessor::Array::newxs_getter called at /usr/local/squeezeboxserver-7.5.1-30836/CPAN/Class/XSAccessor/Array.pm line 64.


Further investigation suggested that the Array.pm was version 1.05 but the binary version under CPAN/arch/... was 1.04. As the version on http://svn.slimdevices.com/repos/slim/7.5/trunk/vendor/CPAN/ is 1.04 I used the Array.pm from http://svn.slimdevices.com/repos/slim/7.5/trunk/vendor/CPAN/Class-XSAccessor-Array-1.04.tar.gz to replace /usr/local/squeezeboxserver-7.5.1-30836/CPAN/Class/XSAccessor/Array.pm .

This worked and now I have a successfully upgraded slimserver instance running on my server.

[crabe]

Rather than plugging in the old 1.04 Array.pm you might also upgrade to Class-XSAccessor-1.05 which contains the fitting Array.pm version - worked for me :-)

[crabe]

Class-XSAccessor-1.05.tar.gz can be downloaded at http://search.cpan.org/~smueller/Class-XSAccessor-1.05/ or from the 7.6 tree at http://svn.slimdevices.com/slim/7.6/trunk/vendor

[Blue_Atom]

Nice idea - I think I got a bit hung up on the 1.04 thing but am now running 1.05.
Interesting thing is I started seeing these messages when I started the service with 1.05 (which I never had before);
[ Jun 21 18:56:36 Executing start method ("/usr/local/slimserver/slimserver.pl --perfmon --cliaddr=192.168.0.1 --playeraddr=192.168.0.1 --daemon --logdir=/usr/local/slimserver/Logs --pr--prefsdir=/usr/local/slimserver/prefs"). ]
[10-06-21 18:56:37.9844] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 06:59:24 MDT 2010) perl 5.008008
[ Jun 21 18:56:38 Method "start" exited with status 0. ]
/usr/local/bin/mysql_config[79]: sed: not found [No such file or directory]
/usr/local/bin/mysql_config[87]: sed: not found [No such file or directory]
/usr/local/bin/mysql_config[139]: sed: not found [No such file or directory]
..
..

Rather bizarre.
I manually added a line to source /etc/profile in the mysql_config script and the messages went away.