Kodi Community Forum

Full Version: getting my repo working
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
This isn't really a skin related question I guess, but I didn't really know where else to put this.

I'm trying to get my repository add-on working and frankly, it's driving me crazy.

I can get the repository installed, and it does give a listing of the available add-ons. However, when I try to update or install them, the download starts and stops right away.

I'm probably doing something wrong but I can't figure it out. Is it because the md5 is missing? How do I get one to be generated anyway?

This is the repo add-on: http://www.mediafire.com/?h16paoeyiq3wnaa

If anyone would be willing to check what I'm doing wrong, that would be great.
Beware of the fact that you'll need to bump up the repo version with each change. Otherwise XBMC will use old cached version even when you are installing it via install from zip.

Where's the repo hosted? I had no luck with Git. It might be easier to use ZIPs with SVN.
Haven't checked your repo, will do just now. You need to have the md5 hash. a free utility for windows is HERE

My hash of addons.xml goes into addons.xml.md5 like this

Code:
F2A0D6C0798D10504BCB7959BA82F4CC  addons.xml


This is pointed to by addon.xml here is mine.

Code:
<addon id="repo.mudisle" name="Mudisle Repo" version="1.0.0" provider-name="Mudislander">
    <extension point="xbmc.addon.repository" name="Mudisle Repo">
        <info>http://xbmc-skin-convergence.googlecode.com/svn/branches/repo/addons.xml</info>
        <checksum>http://xbmc-skin-convergence.googlecode.com/svn/branches/repo/addons.xml.md5</checksum>
        <datadir zip="true">http://xbmc-skin-convergence.googlecode.com/svn/branches/repo</datadir>
    </extension>
    <extension point="xbmc.addon.metadata">
        <summary>Convergence Repo Installer</summary>
        <description>Mudisle Repo is the home for the skin Convergence a vertical menu system for XBMC</description>
        <disclaimer>You break it - You get to keep the pieces</disclaimer>
        <license>GPL</license>
        <platform>all</platform>
        <noicon>true</noicon>
        <nofanart>true</nofanart>
    </extension>
</addon>
Try cleaning up

http://xbmc-focus.googlecode.com/svn/tru.../addon.xml

Safari says it's not valid. I would get rid of

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

and extra spaces.
pecinko Wrote:Safari says it's not valid. I would get rid of

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

If Safari says that the posted line is not valid, then Safari is bugged. This is a valid header-line which should be in any XML document. But obviously you have to make sure that the encoding of the whole XML file really is UTF-8. You can drop the standalone because it is not required but it is valid.
Thanks guys, I've cleaned up the xml's and compared every with how other repo's are structured but it still won't work.
Now when I make a zip it tells me the add-on doesn't have the correct structure...it's an xml with a png... what else do I need to take into account structure wise :?
Do you maybe use OS X to compress the .zip file?
Montellese Wrote:If Safari says that the posted line is not valid, then Safari is bugged. This is a valid header-line which should be in any XML document. But obviously you have to make sure that the encoding of the whole XML file really is UTF-8. You can drop the standalone because it is not required but it is valid.

:-)

Safari says that the document is invalid and probably because of tabs/extraspaces/formating.

However, since it's not required by XBMC I was suggesting dropping the first line. So I have put everything on one pile and compressed sentence afterwards. I guess that makes me bugged :-)
Try renaming skin.refocus.zip to skin.refocus-0.9.3.zip

BTW you have regenerated MD5 after xml changes, cleaned your's repo addon from cache and reinstalled it?
One difference between your repo that I downloaded & mine is
Quote:<extension point="xbmc.repo.jeroen"
and
Quote:<extension point="xbmc.addon.repository"
I do remember that I also battled until I used another person's and changed the paths & names.
Edit Removed link as no longer needed
pecinko Wrote:Try renaming skin.refocus.zip to skin.refocus-0.9.3.zip

BTW you have regenerated MD5 after xml changes, cleaned your's repo addon from cache and reinstalled it?
Yup I regenerate the md5 every time and clear the cache

Mudislander Wrote:One difference between your repo that I downloaded & mine is
Yeah caught that one earlier too, it's corrected now.

`Black Wrote:Do you maybe use OS X to compress the .zip file?
No, I'm on Windows 7. I took your repo addon btw, only changed the names, didn't even change the url's just to see if it would install and even then xbmc says the structure is wrong Huh Also tried to use 7zip instead of Windows's zip tool.
Installed your repo (my version) which points to an update of your repo v2.0.0, which will not install & also points to your skin, also will not download.

At a guess I'd say it's looking for the zip file with the version number as mentioned by pecinko

Edit Here is my data directory for you to look at http://xbmc-skin-convergence.googlecode....nvergence/

BTW Is this a sneaky way for everybody to download your repo Wink
It's been a while since I did XML but back when that was my thing, there were a couple of really common text editors that insisted putting BOM's (http://www.opentag.com/xfaq_enc.htm#enc_bom) at the top of their files. Unfortunately, some XML parsers have trouble with the BOMs and will complain, even though the files are well formed. In my specific case, it was a good daylong mystery trying figure out why Xalan and Xerces were barfing on certain developer's code. It eventually turned out that the developer in question was using Eclipse and it was adding a BOMs to every XML file he touched.
Open the addons.xml with Microsoft Visual or some other ide that can recognize xml structures. Then you will see the problem and you can correct it.
It's indeed like oo_void said a BOM on top of the file. if you put the cursor in front
Code:
<?xml version="1.0" encoding="UTF-8"?>
and hit backspace the xml turns valid (even though seemingly nothing else changes)
Pages: 1 2