Hey there !
I just wanted to mention that in my case CoreElec would not auto-update to 9.0.1 (from 9.0.0).
Mini M8S II 2/16 with CoreElec on SD card.
I had the “auto” set ON.
In tried rebooting (twice) and wait for some time.
I went and switched auto to manual and then again to auto.
I also checked the update channel and the available version when I had it on “manual” but nothing was “available”.
One thing I did not do was to reboot after the 3rd step.
Are there any other steps I should have taken for the auto update to work ?
So this time, I resorted to manual update by placing the update 9.0.1 file into the updates folder and I rebooted. All seems fine now, the update was done. It just seemed strange to me that the auto update was not working. I will test it again with the next version (9.0.2) whenever that comes out and report.
I think the .0.1 autoupdate is offered with some delay.
Just got 9.0.0 on a fresh testbox, so thats the one that is offfered now. I can see how delaying the very latest would help in solving some unforseen stuff before mass release
After updating, the Zattoo PVR Client no longer worked.
I have:
deleted /storage/.kodi/addons/repository.coreelec
cleared the packages folder from all previous versions
then updated Coreelec once more
Error message upon attempting to install the Zattoo PVR Client is: the dependency on kodi.binary instance pvr version 5.1
Could you check addons>my addons>pvr clients>yourpvrclient.
If you go to update here where you can select s version, is there a newer version presented?
@netbuild you may have to force a manual update of the addon
These issues should only happen if you still have a repository package that you have not deleted, we have tried to make it so old versions of CoreELEC can install the addons that shipped at the time of release, so each release of CoreELEC has its own addons folder on the server now, that is why it is imperative that you check that you do not have one installed as it will force your installation to use 9.0.0 addons which are now incompatible and that is why you will see that message.
Real fix is rm -Rf /storage/.kodi/addons/repository.*; everything works/updates again now. I had a couple other retail repos listed (kodinerds and similar) and I guess they were stale as well.
Is it safe to add this to autostart.sh ? Any idea what the implications are?
The problem with what you have just done is that you have now just deleted all of your repositories, so any 3rd party addons that you have installed will no longer update.