New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update avahi, nss-mdns and jsoncpp #2138
Conversation
The 0.x.y branch of jsoncpp is feature compatible with the 0.5.0 used from my testing. I looked at updating a pvr addon (pvr.hdhomerun) to use newer updated versions, and the latest 0.10.6 release (dated April 2016) had no regressions. That branch only receives minor backports from master every now and again. This is more just to let you know my experiences. I havent looked at anything LE ships that uses jsoncpp, so obviously it would require some thorough testing. |
@fuzzard many thanks for the info. Unfortunately all of the pvr addons that use What should happen is that the upstream projects switch to using a more modern The PVR addons using
Ping @ksooo - time to update jsoncpp in the remaining addons? Maybe even to 1.x.y if possible? |
Fully understand, just wanted to pass on info i had at hand. I have a working branch of pvr.hdhomerun running on the 1.x.y branch, but the most annoying thing with that is the build on win machines has deprecated warning spam. Even if no deprecated methods are being used or referenced. There was a PR to jsoncpp to minimise the deprecation warnings to only when affected functions were used, but last i checked (couple weeks back) the behaviour hadn't changed. I have a PR at pvr.hdhomerun to pull it up to 0.10.6 with the end goal to take it up to the 1.x.y branch, but maintaner has gone a little awol. I figure if we can get one of the pvr clients up to date as a reference, it might make it easier on the others to change. All this isnt really relevant to LE though. Again, just info at hand that might be useful at a later date. |
added 3 commits to bump to latest versions
|
According to docs and https://github.com/CvH/LibreELEC.tv/blob/76d000231af7df69ce4079992f82c44f38c16898/packages/network/nss-mdns/config/nsswitch.conf only libnss_mdns_minimal is needed. I will also have a look at librespot later tonight. IIRC to runtime test, resolve libreelec.local (or another device on your subnet, eg a routee) in libreelec. |
A brief test on Generic is working OK (absolute basics - booting into Kodi, pinging www.google.co.uk, Samba is working, but no PVR tests) However if @ksooo (or anyone else) has no plans to update I'll include this as-is in test builds as it will help confirm there are no immediate |
I chatted @ksooo on Slack and he has no plans to update Until upstream is updated (and really, all the PVR addons need to be updated to be on the same version otherwise it gets messy), we should drop the |
Ive had a quick glance at those other 5 pvr addons Millhouse (not including pvrhdhomerun). Octonet is the only one that currently compiles against Leia Head. Ill do a PR to octonet for a version bump, would you be able to throw that into test builds to try and get some actual testing done against it? I dont have the backends for any of these pvr addons for testing. The other 4 all use instances of iChannelNumber and strStreamUrl which were removed as part of ksooo's work over the past couple months. As you have already been excluding them in your builds, im not sure whats best to do here. Ill have a look through and see if i can make the necessary changes to compile them in a minimalist fashion. But the maintainers (if there are any) will probably need to look at some of the other changes ksooo has done lately anyway. |
Yes, currently only The upstream PRs are not strictly relevant to LibreELEC as we build with an "external" Hopefully the addons that do compile will merge your PRs in which case we can then align LibreELEC with the commit already in this PR. Many thanks for taking care of this! |
Hi MillHouse, Sorry for bringing this up in this thread, but im not sure whats the best way/place to ask this. Ive done an initial pass on pvr.filmon to bring upto PVR API 5.7.0 as a bit of a test to see what may be required for the others. This includes a bump to jsoncpp 0.10.6 Could you possibly build with this, and request any feedback. If it functions, ill look to pull the rest up to the bare minimum, but i cant test it at all, so its a blind fix. It compiles, and runs in Leia Head, but thats as far as i can get. Ive honestly no idea what the user base is, or even if filmon is used by anyone, so dont know where i can get any feedback. |
Thanks - I'll try building pvr.filmon later this and give you feedback on the PR. |
Another PR this time for pvr.pctv. The only thing ive noticed in regards to jsoncpp (and this is the same for argustv) is they use a deprecated function (getFormatedErrorMessages). The only reason this method has been deprecated is because of the typo in the function name (new method getFormattedErrorMessages). Edited to add pvr.stalker kodi-pvr/pvr.pctv#52 Im wondering if theres any point updating some of these addons, or if we/i should just let them die. Theres lots of non implemented ToDo's running back to the timer changes done for API 2.0.0/1.9.7 At a brief glance, argustv is going to require a bit more in depth knowledge of the code. Ill have a look when i get some more time, but i may have to leave that one for someone else. |
Thanks, I'll include Killing addons is never an easy decision, but if they're not maintained it does become a little easier. |
pvr.pctv and pvr.stalker have both built successfully - thanks! |
@MilhouseVH I guess it works for your builds ? If so I should squash the commits I guess? |
@Rechi has just submitted PRs for the PVR addons that bumps jsoncpp to 1.8.3: kodi-pvr/pvr.argustv#74 I'm not seeing any code changes though - I thought jsoncpp 1.x.y was incompatible with jsoncpp 0.x.y? @fuzzard are the PVR changes sufficinet for jsconcpp 1.8.3? |
your going to see a shit ton of deprecation spam in your builds. The old functions are still in, but are all marked as deprecated. Should work for now, but dont expect good things in the future. i would suggest sticking with the 0.x.y branches at this stage personally |
@fuzzard As upstream has now moved to 1.8.3 I think doing the same is the best option, regardless of the deprecation spam - if we remain on 0.x.y while upstream uses 1.x,y any differences in behaviour that we experience (both good and bad) could be the result of being on the older library. Presumably the deprecation changes are in the pipeline? @CvH could you add another commit that bumps jsconpp to 1.8.3 and I'll try some test builds. |
yeah, feel free to bump if they are going to do that. ive put a comment on the pvr.hdhomerun PR to ask if he is aware of the changes, but if they want to push to it, thats up to them i guess. |
Many thanks, @fuzzard! |
8f01f02
to
9cf6128
Compare
Thanks that builds ok. These are the jsoncpp-related deprecation warnings for all PVR addons: http://sprunge.us/APZD |
I've put up a patch to the pvr.hdhomerun addon to change to the new methods. The spam comes from the windows side of builds. GCC/Clang handles the deprecations differently, with only 1 message per instance, but windows seems to show it regardless with multiple. Seems Rechi is wanting to go ahead with it regardless, and i understand why. Just would have been nice to update the addons to remove the deprecated methods rather than blindly do a version bump, but all good. |
Another off topic, but @MilhouseVH ive just pushed a PR to pvr.argustv kodi-pvr/pvr.argustv#75 |
Will do. I can at least say they all build OK. |
rebased |
changed the url from OE mirros to actually maintained repos