Created attachment 2707 [details]
screencap

version field is blank as well.  might not be much point having that line if there is no version applicable.

This is settings -> music source -> squeezenetwork

That screen does not exist in the latest code, problem fixed! :)

oh, er, then I guess I need to look for a different problem.  That was r1575 which I built last night.

factory reset and r1593.  I'm still seeing it.  Which latest code was that?

The screen now shows r1577 for the squeezenetwork version, but the wrapping for the first line is still a mess.

ok, i'm confused. i really did take that screen out, and i don't see it in any builds here.

jive.bin is one I built here, but it's from the trunk of jive.  I haven't seen any downloaded bin since 1520.
I am however, still seeing it even in a software build on osx, fresh checkout from trunk two days ago. Just checked out r1605, rbuilt the soft client and it's still there.

On Music Sources, I see SqueezeNetwork, <local serer>, Other Server, and Auto Discovery.

I'm also seeing errors making note that jive has no UUID, both for the soft client and the hardware.

interestingly, windows build at 1607 just lists music sources, no longer showing the option to drill down. In this case, I had deleted the output/build folder.

I guess I need to wipe out the home svn copies, wipe out the build folders and start again.

Maybe it might be a safe plan to add an 'rm -r lua' on the build dir to get rid of previously copied applet files. I'll rename this on the assumption that this will prove to the the same problem at home.

Ah, that makes sense. I foolishly renamed the applet, and actually got the name wrong anyways.

So, is there anything to do here?  Can we close this?

well, we are exposed to this kind of problem if we do change lua modules later on.  It makes sense to have a function to clean them, but certainly post 7.0 as the software client isn't the main target right now.

However, if you and Richard are ok with the risk, it can be closed.

Let's address the specific issue when it happens in the future.

I would also like to note if this does happen in the future, a 'make clean && make' will resolve this. This will only be an issue for people doing there own builds, as the nightly build machine always makes from clean.