Bugzilla – Bug 8953
Version of Softsqueeze shipped with 7.1 warns to upgrade because it's optimized for 7.0
Last modified: 2009-09-08 09:15:00 UTC
Launching Softsqueeze at work for the first time after upgrading SqueezeCenter to SqueezeCenter Version: 7.1 - 22170 @ Mon Jul 28 13:31:27 PDT 2008 - Debian - EN - utf8, Softsqueeze (version 3.6) issued a message that said it was optimized for version 7.0 but I was running Squeezecenter v 7.1 and so I should upgrade. It had a download button, which took me to a page which told me to go to Sourceforge, which said it had version 3.5, one OLDER than what I already had. So I uninstalled Softsqueeze anyway, then reinstalled it through the appropriate Squeezecenter page. The version installed from Squeezecenter was 3.6, the same I had just removed, and it issued the same warning.
This should probably cover it for the time being. The problem is that the certificate is out of date, so any builds of softsqueeze will end up giving another warning. Given that SS if being deprecated, it probably makes more sense to simply check the box to shut off the warning and move on. =================================================================== --- softsqueeze/src/org/titmuss/softsqueeze/Softsqueeze.java (revision 22267) +++ softsqueeze/src/org/titmuss/softsqueeze/Softsqueeze.java (working copy) @@ -57,7 +57,7 @@ private static final String MIN_SLIMSERVER_VERSION = "6.5"; - private static final String MAX_SLIMSERVER_VERSION = "7.0"; + private static final String MAX_SLIMSERVER_VERSION = "8.0"; private boolean isSlimserverCheck = false;
*** Bug 8968 has been marked as a duplicate of this bug. ***
Richard said maybe he will just take out the check. A replacement for SoftSqueeze is planned.
change 22432 put off the version check, and put in place a more appropriate message for the future. Of course, I'm assuming SS will remain at least as an emulator in svn, if not built into the distro when the replacement comes. change 22437 points the about and homepage to the wiki instead of the outdated sourceforge page.
Richard says he will rebuild new version with KDF code once he returns back home.
I did do a build shortly after the changes above and committed it as version 3.7b1. The only thing that isn't there is the security certificate. I'm also not sure that the applet version works correctly. But, webstart should suffice for all that is required.
change 22727 build with security cert. Mickey, note this has not expired. I seem to remember you were going to get an updated cert?
Matt, Dean says you can get the relevant code signing key for softsqueeze.
Matt: where do we stand on the new key?
Matt is on it.
I really don't see how I can help here... I contacted THAWTE and they told me that the expired certificate cannot be "renewed", but rather a new certificate is generated. In order to do this, they need certain information from our "java server" (something that doesn't totally make sense to me) that I cannot provide them. Richard, you set up the certificate last time ... right? Why not do it again this time? I definitely do not have enough information to request the certificate myself at this point.
Change 22886 should fix this.
Fixed in change 22892...
So is this fix live in 7.2.1 then?
Verified, no more upgrading warning in SoftSqueeze 3.7, 7.2.1 - 23530.
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC