Updating SqueezePlay ... I don't get it
Posted: Mon Jan 25, 2021 6:22 pm
(aka three dumb questions: WHICH version of WHAT is recommended and how to update?)
Hey all,
I've been running Sqpos 30301 for a couple years, and it just worked, and I've not really thought about updating it (I installed and flashed to memory, and I left it there, great).
1. *should I* be in the habit of updating anything? Does it need updating? apt-get is available, but *should I* use it, or should I not use it?
2. Squeezeplay itself seems a pretty old version - something else I didn't really think about but due to a recent discovery of a bug, I'm now aware that I should think about it... should I try to update it / it is straightforward (even if not obvious to me)? Is it upgradable or just simply built in and I should look for an updated sqpos instead? (See q 3)
3. Should I ignore 30301 and just use the latest_316 (or even latest_54) builds instead?
The bug, btw, is that I observed the clock stops working after approximately 23 days. I'm using the Custom Clock plugin, it's also probably quite old, and seems to rely on the number of jiffies being monotonically increasing (and with a 32-bit signed int, it wraps at 23 days). Maybe that's a coincidence, but for the last few months I've been keeping an eye on it, and right around the 23 day mark, the time on the clock stops updating, I wake up and the time is stuck at like 9pm yesterday. And (other than the uptime command) I can't see a great way to diagnose. I strongly suspect a software error, I don't know if it's in the Custom Clock plugin, or Jive, or Squeezeplay, or something else; hence the three questions above: updating, upgrading, or ditching !
(And if you think I'm going nuts, and I should just report my bug even though I'm running an old plugin on an old Squeezeplay version on an old OS that I have never updated, that's great - let me know where I should report it)
(And related to item 3, if I should approach latest_54 as fully usable other than the ALSA bug, happy to do that; I'm only sticking with 30301 for now to see if I can resolve the above bug. And of course if it's already known and fixed let me know how can I find that - I've tried and found nothing much in Jive bugtraq)
Thanks!
Hey all,
I've been running Sqpos 30301 for a couple years, and it just worked, and I've not really thought about updating it (I installed and flashed to memory, and I left it there, great).
1. *should I* be in the habit of updating anything? Does it need updating? apt-get is available, but *should I* use it, or should I not use it?
2. Squeezeplay itself seems a pretty old version - something else I didn't really think about but due to a recent discovery of a bug, I'm now aware that I should think about it... should I try to update it / it is straightforward (even if not obvious to me)? Is it upgradable or just simply built in and I should look for an updated sqpos instead? (See q 3)
3. Should I ignore 30301 and just use the latest_316 (or even latest_54) builds instead?
The bug, btw, is that I observed the clock stops working after approximately 23 days. I'm using the Custom Clock plugin, it's also probably quite old, and seems to rely on the number of jiffies being monotonically increasing (and with a 32-bit signed int, it wraps at 23 days). Maybe that's a coincidence, but for the last few months I've been keeping an eye on it, and right around the 23 day mark, the time on the clock stops updating, I wake up and the time is stuck at like 9pm yesterday. And (other than the uptime command) I can't see a great way to diagnose. I strongly suspect a software error, I don't know if it's in the Custom Clock plugin, or Jive, or Squeezeplay, or something else; hence the three questions above: updating, upgrading, or ditching !
(And if you think I'm going nuts, and I should just report my bug even though I'm running an old plugin on an old Squeezeplay version on an old OS that I have never updated, that's great - let me know where I should report it)
(And related to item 3, if I should approach latest_54 as fully usable other than the ALSA bug, happy to do that; I'm only sticking with 30301 for now to see if I can resolve the above bug. And of course if it's already known and fixed let me know how can I find that - I've tried and found nothing much in Jive bugtraq)
Thanks!