where have jive update messages gone

[Millwood]

I have lurked on gmane.music.equipment.slimdevices.jive.scm watching jive updates. It appears they stopped appearing on 4/4. Is there another place to watch now?

[gharris999]

http://forums.slimdevices.com/showth...version-to-git

[bluegaspode]

http://forums.slimdevices.com/showth...version-to-git

But shouldn't the code be pushed to github so that one could continue to follow?

[edit] ah - here: https://github.com/logitech

[Millwood]

Sorry to be dense.

The svn changes were posted to the gmain newsgroup, making it easy to monitor activity.

Does github have a similar way to monitor change activity?

Also - what triggered this was noticing a version number change (rather dramatic) in my controller software which did not correspond to an svn update nor to anything I see in github.

So a further question is how the controller and the squeezeos versions will correspond to something I can find in github.

[gharris999]

The svn changes were posted to the gmain newsgroup, making it easy to monitor activity.

Does github have a similar way to monitor change activity?

You could always periodically check these links:

https://github.com/Logitech/squeezeplay/commits/7.8/
https://github.com/Logitech/squeezeos/commits/7.8/

[Millwood]

You could always periodically check these links:

https://github.com/Logitech/squeezeplay/commits/7.8/
https://github.com/Logitech/squeezeos/commits/7.8/

How can a correlate those entries to version numbers of builds?

[awy]

How can a correlate those entries to version numbers of builds?

I'm afraid that you cannot. After installing a build you can look in /etc/squeezeos.vesion and the last line, "Base build revision:", gives the git revision identifier for squeezeos. But nothing tells you the revision of squeezeplay.

[Millwood]

I'm afraid that you cannot. After installing a build you can look in /etc/squeezeos.vesion and the last line, "Base build revision:", gives the git revision identifier for squeezeos. But nothing tells you the revision of squeezeplay.

1. No such file in my debian install. And you say no such file for squeezeplay (jive).

2. The idea was to be able to decide if installing a new beta was worth it based on what was fixed. And to help verify if a fix was a fix.

This all seems a sorry state of affairs if you are correct.

[erland]

1. No such file in my debian install. And you say no such file for squeezeplay (jive).

2. The idea was to be able to decide if installing a new beta was worth it based on what was fixed. And to help verify if a fix was a fix.

This all seems a sorry state of affairs if you are correct.

I guess you can always look at the build date, if the build date is more recent than the date for a specific change in the github commit history that change is likely included in the build. Of course, you can't be completely sure if they have the same date, but then just wait for the next build which have a newer date before beta testing it. In the cases where Logitech feels it's urgent to get feedback on a bug report, I'm sure they will inform us about which build we should use.

I can agree that the new solution might have disadvantages compared to the old subversion system in this regard, but if it makes the work within Logitech easier it should be worth it.

[awy]

1. No such file in my debian install. And you say no such file for squeezeplay (jive)..

Debian install of what? I thought we were talking about player firmware (Radio or Touch).

I guess you mean either LMS or desktop Squeezeplay.

For Squeezeplay the git revision is in the package filename: squeezeplay_7.8.0~22901ff_all.deb.

For LMS the revision used, in both the filename and as reported via the WebUI, etc., is the Unix timestamp of the revision: logitechmediaserver_7.8.0~133664662_all.deb. It is not trivial to correlate this with the git revision-id but it should also not be that difficult.