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
No upgrades to elementum and burst after kodi's upgrade to v19 #724
Comments
I don't know about any changes in repositories with Kodi 19.
No, it does not. https://github.com/elgatito/plugin.video.elementum/releases
No, it always download archive will all architectures, there were reasons for that. |
As for the rest, reddit was probably wrong and thank you for the clarification. |
@pitsi side note: instead of checking reddit for new releases you can subscribe for notifications about new releases here in github - see "watch" button in the right top corner of the page (you can choose only releases). |
As for the updates, I use this to get updates via rss in my thunderbird |
So, I have one addon from that other third party repo. It was last updated ~10 days before the release date of v19, but since it is python3 ready, it showed up as installed and it works as it should. On the other hand, I want to poke things a little and see how will kodi react. On a scale from 1 to 10, how much do you think I will f up my installation if I delete ~/.kodi/userdata/Database/Addons33.db and force kodi make it again? |
@pitsi you screenshot shows "Official repositories only". I believe it means Kodi official repo, not addon's. |
Update official add-ons from So this should not be a problem, I think. About deletion - people says it will disable all add-ons but probably not more that that, e.g. https://discourse.osmc.tv/t/need-to-delete-addons27-db-and-all-its-gone-for-ever/75698/5 |
The other option there is "any repositories" and the explanation below says
Notice that thing in bold? I think it only refers to official addons, e.g. youtube, twitch etc and since elementum is not an official one, it does not fall in that category. Brb, I am off to mess things up! Thank you for the clarifications. |
Done! Kodi started with estuary and asked me to enable every single addon on the next launch and it even showed the options for the ones that were not set to defaults (elementum, burst, youtube, twitch etc). I enabled them all and switched the forementioned setting to "any repositories" just in case. And things got back to what I reported when I first opened this issue. On the scale from 1 to 10 above, I think this is a 8.5 :D |
Looks like the the migration from old kodi to new has some issues. |
You do know that they will go nuts when they hear about third party addons, right? |
So, I got an update today, the very first one after deleting addons.db and starting fresh. Sadly, it was for an addon that is in the main kodi repo and I am sure it would be done anyway. Because of that, I am now really intrigued in updating libreelec (the x64 one, not the one on my rpi3b+) to v10 that has kodi 19, although it is still in beta and its devs advise for a fresh install. The amount of addons I have installed there is like 3 times the ones I have on my pc, so it will be a lot of work if something breaks and I have to start fresh. On the other hand, I already know which ones are ready for 19 and which ones are not (and the ones that will never be), so that makes my work a bit easier. I will install the repos first, buy extracting everything in the right folder and then each and every addon from its repo. Tldr of the above. I know that elementum's repo is installed from the elementum itself (as a video plugin). Is there a repository.elementum.zip that will save me some work? |
if i understand correctly: |
As far as I understand, any Kodi19 added new setting to allow auto-updates from all repositories or Kodi repositories only. |
@elgatito @antonsoroko So, right now I am trying something insane! I will remove all my addons from ~/.kodi/addons, except from the repository ones, by deleting their folders from there and the addons.db. I am also keeping their settings intact in ~/.kodi/addons/userdata/addon_data. |
@pitsi I don't understand what you want to achieve with all those actions? |
I want to make a "fresh" install (not actually fresh, but an existing one with all my addons installed fresh) in which every addon is listed as installed and will get updates in the future, because kodi does not mark them as installed. And I almost did it! After that, I batch installed my addons from command line (howto upon request), leaving elementum for the end due to its uniqueness. I downloaded the right zip as usual, installed it via "install from zip", restarted kodi and the notification "Elementum daemon has started" made me happy for like 30 seconds. Elementum is now properly installed and running, as you can see here. Then the prompt to install burst came up, I pressed yes and nothing happend. So I went to settings > addons > install from repository > elementum repository > program addons to install it manually. And this came up, although both elementum and the repo were installed already! Obviously, I will press ok there and it will install as usual, although it will get me back to what I described in the first place. ---edit |
So, I reinstalled elementum one more time (right after burst) yesterday. It downloaded the full package, so I had to delete the uneeded architectures etc, but it works as it should. I haven't made the upgrade to libreelec 10 on my other system yet. I will follow the same insane procedure I did yesterday, but this time I will keep elementum (plugin.video.elementum) and its repo (repository.elementum) and see if the repo and the addon will show up as enabled afterwards. |
Upgrading libreelec to 10 failed miserably and now the system starts with a black screen with a cursor in the middle. ---edit |
So, a friend of mine just reported a similar behavior. I am now certain this is a kodi issue and although I do want them to fix it, I won't report it because of their attitude. If anyone else wants to do it, I can provide any needed support (except full logs). Feel free to close this issue anytime you wish. |
Time to close this, because it is not an issue of elementum but a general behavior of kodi against third party addons. |
Preface. I upgraded to kodi 19 a few weeks ago (right after the day it was released). After the upgrade was completed (the dialogs about updating databases before launch and the mandatory upgrades of all the addons), I checked if every third party addon and repo is still there, and indeed everything was there and the repos seemed to work just fine, e.g. I could see elementum and burst listed under elementum's repo.
Expected Behavior
So, since the repo is still enabled, one would expect the updates to keep coming once they are available.
Current Behavior
However, this does not happen and I assume it's because of some new "policy" about third party repos that the new kodi implements.
Possible Solution
As seen in the screenshots below, reinstalling each addon again upgrades them. I have to wait a few more days to see if they will get autoupgraded
Steps to Reproduce (for bugs)
There is a small description of what I did in the preface. Do not do it unless you really want to go through installing 18.9 fresh, then install elementum on it and finally upgrade to 19, because the procedure is quite tedious.
Context
I saw earlier in reddit that elementum was upgraded to 0.1.73 and burst to 0.63, so I checked where my kodi installations are.
I also have another kodi 18.9 installation that works as it should and it is now on elementum 0.1.72 and burst 0.63.
One more annoying thing after the manual upgrage was that kodi downloaded the zip that containes elementum for all operating systems and architectures. ~140MB as seen below, while I was expecting for something around 15MB
On top of that, ALL the binaries were extracted in ~/.kodi/addons/plugin.video.elementum/resources/bin, raising that folder's size to 350+MB
I will delete the ones that are not linux_x64, but I assumed it would download and install only the one for the os and the architecture it is currently run on.
Your Environment
The text was updated successfully, but these errors were encountered: