Posts: 6,339
Joined: Jul 2010
Reputation:
116
artrafael
Team-XBMC Forum Moderator
Posts: 6,339
You didn't say which add-ons, so don't know if you are referring to the default XBMC.org repository or some third-party repository. If it's the XBMC.org repository, you can try doing a "Force refresh" (System/Settings > Add-ons > Get Add-ons > open context menu of selected repository). For a third-party repository, in addition to "Force refresh", see if there's a separate Frodo repository -- if there is, remove the old one and add the new Frodo-compatible one.
Posts: 1
Joined: Jul 2013
Reputation:
0
okay, getting this message on almost every xbmc official repository add-on.
last tried xwmm add on
current xbmc version 13-alpha6
am rather curious as to why default repository items giving such issues
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
bugs in an alpha? the world is coming to an end!
Posts: 3
Joined: Jul 2013
Reputation:
0
2013-10-17, 17:24
(This post was last modified: 2013-10-17, 17:25 by dms6601.)
I'm having the same issue.
My environment is: Openelec r16208 (compiled last night), on RPi, and XBMC version is 13 (alpha 9).
For example I attempt to install from zip, Navi-X and I immediately get that dependencies not met crap.
did: mv Addons??.db to a bak file name
did: restart xbmc.bin
did: reattempt to install addon (Navi-X)
* Also getting a lot of "marked broken" notifications requests, which I'm ignoring for now.
Posts: 17,859
Joined: Jul 2011
Reputation:
371
We provide no help for any piracy addon.
Posts: 3
Joined: Jul 2013
Reputation:
0
Sure, but it's not one particular addons, or one particular "marked broken" notifications requests, it's a bunch of spurious notifications that inhibit installation of a broad range of addons, or repositories.
Is there a code change that addon programmers need to address? I'm just trying to understand the error as there is little in the xbmc.log that is useful.
Posts: 17,859
Joined: Jul 2011
Reputation:
371
2013-10-17, 19:34
(This post was last modified: 2013-10-17, 19:34 by Martijn.)
Yes. I posted the change in our python dev section of the forum. If they don't follow up on that they will end up with broken addons.
We notified them now way before final release.
That's where our responsibility ends.