Just installed the latest OSMC image 24-12 and installed the Beta Build, during installation of Beta Build, I got a sad face, rebooting via terminal > sad face.
I will perform the steps again with a clean SD card just to be sure I didn’t do anything funky.
edit: wrote the image from dec-24st, finished the OSMC wizard on the tv, ran the commands to upgrade to Kodi 17 beta build, sad face after the reboot: http://paste.osmc.io/axomutepoc
So seems we have a couple of issues. There is an extra < in /usr/share/kodi/addons/repository.xbmc.org/addon.xml also the md5 location seems incorrect.
Once past that hurdle the old md5 issue is back. So you need to set hashes to false also to get addons to install
@Sam: How can we rollback to your Beta5-release?
After letting OSMC do its upgrade using ‘MyOSMC’, I’m stuck in a sad-face-loop, removing /.kodi doesn’t help so I figure I need to reinstall the Beta5 again - but how to?
Smthg like ‘sudo apt-get install --reinstall rbp2-mediacenter-osmc-16.9.5-1’ doesn’t work, so I’m stuck at the moment…
It seems that file is causing the boot loop. Also the song info etc doesn’t seem to be appearing when playing a song through my iPhone. Just a heads up. Not sure how that really works so don’t know if a log dump will help. Have attached anyway after fixing the xml file.
Under services all I have is updates. I can’t see btplayer under all either. So it appears not to be installed. Let me know if you want any logs or anything ran. Happy to give you ssh access too if that’s easier
Thanks for reporting the issue with the repository XML file. It looks like I’ve fat-fingered that twice in the past few weeks, but I have now pushed updated builds with a fix, so you can update to restore normal service.
The MD5 location is actually correct, but hashes did need to be disabled. Interestingly, Kodi doesn’t seem to host any MD5 hashes, and unless their mirror system is generating them on the fly, I’m not sure how it’s working at all. The MD5 file we provide does resolve and is up to date, so it should be working. That’s for another day though.
You can’t. The reason we have test builds is so that these things get tested and discovered before we distribute these builds to the masses. If this doesn’t take your fancy (and that’s completely understandable), then you should stay with Kodi Jarvis. @gmc’s builds allow downgrading because we use a very hacky way to create the repository for those builds. But that system isn’t suitable for OSMC proper (where we have a lot of packages and dependencies). Most users also won’t know how to downgrade nor know what to downgrade. But we resolved this issue in less than one hour, which is a pretty quick response time.
Run update again. It’s possible your ISP is running a proxy or caching the repository somewhere. The latest version is 1.0.7:
I’m on a pi3 so armhf. That said though the package doesn’t appear to be in any of my sources. Apt-cache shows 1.0.5 as the only available version and not in a repo.
The repo can’t be cached though as I installed the new beta update. Kodi shows it’s running rc1
I had to rename/delete the ‘Addons26.db’ to make this latest OSMC-Krypton quit the sadface loop, probably because I have installed a repo from the german Kodinerds.net website (legit Amazon Prime and Pro7 (german broadcasters) etc. addons) which after a reboot were immediately marked as incompatible - but: those addons do still work flawlessly runnig today’s official Krypton RC for Windows… and I don’t get why OSMC didn’t start before after renaming /home/osmc/.kodi.
So OSMC on RPi2 works now, I also could install the latest fixed version.
Another thing: I can’t switch to German as the desired language, there are only English and Turkish available. Never had that before…