I have what should hopefully a quick and easy question to answer although my explanation probably makes it sound more complicated
I have installed the March update on my RPi 2 and all is good.
Is the version of Kodi that is installed the final v17.1 release as just announced over at the Kodi website?
Checking on my Pi the version of Kodi shows as 17.1-RC2 with a compile date of 17/03/17 which appears to be just before the final 17.1 release was announced. What’s confusing me is that I don’t think an RC2 version was available from Kodi and it went straight from RC1 to Final, so does the RC2 release here include all the fixes and updates that are in the final 17.1 release?
I don’t think it can do based on the fact that some fixes where only merged two days ago but I’m unclear on how the release versions here correlate to the ones on the Kodi site.
Follow up question, if the latest fixes in the final 17.1 release are not included in the March update will they be in the next OSMC update? (Presumably April).
Thanks for your help and support.
I think it is there. Just updated my apt-cache, and I have a pristine
Unpacking vero3-mediacenter-osmc (17.1.0-1) over (17.0.0-15) …
11:30:42.678 T:4110578608 NOTICE: Starting Kodi (17.1). Platform: Linux ARM (Thumb) 32-bit
So, just update from now on, and it should show you the new version.
I updated last night (21 March) and this morning it says:
08:40:26.401 T:4108837808 NOTICE: Starting Kodi (17.1-RC2). Platform: Linux ARM (Thumb) 32-bit
08:40:26.401 T:4108837808 NOTICE: Using Release Kodi x32 build (version for Vero)
08:40:26.401 T:4108837808 NOTICE: Kodi compiled Mar 17 2017 by GCC 4.9.2 for Linux ARM (Thumb) 32-bit version 3.16.39 (200743)
08:40:26.401 T:4108837808 NOTICE: Running on Open Source Media Center 2017.03-1, kernel: Linux ARM 64-bit version 3.14.29-16-osmc
Kodi 17.1-RC2, compiled on 17 March.
So I did a further apt-get this morning and got this:
osmc@osmc:~/.kodi/temp$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.2 MB of archives.
After this operation, 5,120 B disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://apt.osmc.tv/ jessie/main vero3-mediacenter-osmc armhf 17.1.0-1 [41.2 MB]
Fetched 41.2 MB in 6min 2s (114 kB/s)
(Reading database ... 25946 files and directories currently installed.)
Preparing to unpack .../vero3-mediacenter-osmc_17.1.0-1_armhf.deb ...
Unpacking vero3-mediacenter-osmc (17.1.0-1) over (17.0.0-15) ...
Processing triggers for mime-support (3.58) ...
Setting up vero3-mediacenter-osmc (17.1.0-1) ...
Rechecking the kodi log:
11:51:21.575 T:4108227504 NOTICE: Starting Kodi (17.1). Platform: Linux ARM (Thumb) 32-bit
11:51:21.575 T:4108227504 NOTICE: Using Release Kodi x32 build (version for Vero)
11:51:21.575 T:4108227504 NOTICE: Kodi compiled Mar 22 2017 by GCC 4.9.2 for Linux ARM (Thumb) 32-bit version 3.16.39 (200743)
11:51:21.575 T:4108227504 NOTICE: Running on Open Source Media Center 2017.03-1, kernel: Linux ARM 64-bit version 3.14.29-16-osmc
Kodi 17.1, compiled on 22 March! Hehe. You’ve been rumbled, Sam!
That looks promising
Will run another update and check what I get.
Thanks for the replies
The Packages file has a timestamp of 2017-03-22 07:17.
It’s true, Sam doesn’t sleep.
There was an issue with some builds, so I had to rebuild them and stay up and wait for them to complete, test them, then push them to release.
Thanks for the update Sam.
Can you just confirm that this latest build does include all fixes included in the final 17.1 release? Just want to double check as I’ve seen on another thread that version numbers here don’t necessarily correspond with those the release available directly from Kodi.
All fixes are included
Your version should say 17.1, not RC
Yeah - we got that now.
@sam_nazarko Go get some sleep my friend You need it!