2018-04-03, 02:02
Can a repo update itself
I mean, can it update its own datadir to "move to a new home", as long as the old home still exists?
My experience says no... but I have no idea why, nor did I google-up any luck. First, me explain the problem, then I'll drop the details...
I have a repo that's been at v1.0.0 for forever. I decided to copy zips to another server, and copy the xml/md5 to a different directory (and in the future I'll eliminate the originals, but for now they all coexist with the same 755 perms). I added an updated v1.0.1 zip for my repo to its datadir, and updated (both) the addons.xml/md5.
If I install v1.0.0 from-zip, and then allow it to update to v1.0.1, the update appears to be successful -- BUT attempting to install any addon does... nothing. It doesn't fail. But it also doesn't work. It just sits there. The log has only one line saying it thinks it's installing an addon. No errors in the log or GUI. I thought maybe quitting and re-opening Kodi might work, but it had no effect.
Now, let's get this clear: the repo is (probably) fine. The zips are (probably) fine.
I (probably) know this because if I remove my v1.0.1 repo, then install v1.0.1 from-zip, it works perfectly fine. Addons install normally.
Whaaaa?
Here's the demonstrative changed properties, in case they matter...
(but I'm pretty sure the fact the datadir moved is the problem bug... err "feature")
original repo version:
updated repo version:
Note url changes
Is this type of self-updating not a thing a repo can do?
I mean, can it update its own datadir to "move to a new home", as long as the old home still exists?
My experience says no... but I have no idea why, nor did I google-up any luck. First, me explain the problem, then I'll drop the details...
I have a repo that's been at v1.0.0 for forever. I decided to copy zips to another server, and copy the xml/md5 to a different directory (and in the future I'll eliminate the originals, but for now they all coexist with the same 755 perms). I added an updated v1.0.1 zip for my repo to its datadir, and updated (both) the addons.xml/md5.
If I install v1.0.0 from-zip, and then allow it to update to v1.0.1, the update appears to be successful -- BUT attempting to install any addon does... nothing. It doesn't fail. But it also doesn't work. It just sits there. The log has only one line saying it thinks it's installing an addon. No errors in the log or GUI. I thought maybe quitting and re-opening Kodi might work, but it had no effect.
Now, let's get this clear: the repo is (probably) fine. The zips are (probably) fine.
I (probably) know this because if I remove my v1.0.1 repo, then install v1.0.1 from-zip, it works perfectly fine. Addons install normally.
Whaaaa?
Here's the demonstrative changed properties, in case they matter...
(but I'm pretty sure the fact the datadir moved is the problem bug... err "feature")
original repo version:
xml:<addon id="repository.myrepo" name="my repo" version="1.0.0" provider-name="me">
<extension point="xbmc.addon.repository" name="my repo">
<dir>
<info compressed="false">http://mysite.org/kodi/addons.xml</info>
<checksum>http://mysite.org/kodi/addons.xml.md5</checksum>
<datadir zip="true">http://mysite.org/kodi/zips/</datadir>
</dir>
</extension>
</addon>
updated repo version:
xml:<addon id="repository.myrepo" name="my repo" version="1.0.1" provider-name="me">
<extension point="xbmc.addon.repository" name="my repo">
<dir>
<info compressed="false">http://mysite.org/kodi2/addons.xml</info>
<checksum>http://mysite.org/kodi2/addons.xml.md5</checksum>
<datadir zip="true">http://othersite.com/kodi/zips/</datadir>
</dir>
</extension>
</addon>
Note url changes
- info
- checksum
- datadir
Is this type of self-updating not a thing a repo can do?