Is it really necessary to force users to use pippleware's KODI?

Rascas

Did you at least tried with a really clean install, without your old .kodi settings ? And check or post some logs ? I could help you with that, but I am not interested in spending time giving support for an old, unoptimized Kodi version. I am not a RetroPie maintainer, just this Kodi version maintainer.

toto

@Rascas

My Jessie Lite setup is up to date and as you can read above I indeed moved my .kodi dir to a temp dir before trying pipplewares version so it as good as a clean install as you can get. Like I posted above it is pretty much an unaltered Jessie Lite setup.

Rascas

Please post some logs:
/tmp/runcommand.log
/home/pi/.kodi/temp/kodi.log

toto

I'm sorry but I removed all the logs and reinstalled Raspbians KODI after testing. I'm really not to bothered doing that all over again.

I just keep it as it is for now, everything I want is working fine.

BuZz

Doesn't help us though - and bear in mind people may not be "bothered" to help you next time you have a problem either! it goes both ways.

toto

That's fine by me.

toto

For anyone interested, this fixes my initial annoyance.

Create or edit /etc/apt/preferences with the following text:

Package: *
Pin: origin *.bintray.com
Pin-Priority: 1

Now KODI and related packages won't be updated/upgraded to pipplewares version.

That's it from me, you can now delete my account at your convenience.

Thanks!

mediamogul

Wait! you never told us where you hid the money.

toto

I might cover that in my next appearance...

Until then, toto has left the building!

glennlake

@toto If you don't want to help other people on this forum, why did you even start this post??

toto

@glennlake

You might not have noticed but I even posted a simple solution (apt-pinning) to my problem above which also could help others.

BuZz

No actual need to pin it - if you uninstall kodi from retropie-setup (at least on v4.x) it removes the repo and packages - and jessie version can be installed. Or manually uninstall and remove /etc/apt/sources.list.d/pipplware.list

[edit] correction it wont uninstall the repo without a dependencies removal currently.

sudo ./retropie_packages.sh kodi depends remove

toto

Just got home and decided to have another go at this although I'm perfectly happy with apt-pinning myself it might help others.

Tried it with another SD card (Raspiban Jessie Full edition unaltered, up to date only RetroPie installed). The same thing happens when I use pipplewares KODI, it just segment faults. I have saved the log file (only KODIs, started from console).

If people are still interested I could post that log file.

BuZz

Yes please. (via pastebin.com or similar).

toto

@BuZz

Pinning was the best option for me because when you update installed binaries from retropie-setup it installs pipplwares repro again and you can start over again. This way pipplwares repro gets ignored when you upgrade.

BuZz

It shouldn't re-install the Repo so long as Kodi shows as not installed from RetroPie 4.x as it only updates packages that are installed. (It works this out based on folders in /opt/retropie so it will ignore Jessie Kodi)

BuZz

I have updated the Kodi script so removal via RetroPie-Setup will remove pipplware repository.

toto

@BuZz said in Is it really necessary to force users to use pippleware's KODI?:

It shouldn't re-install the Repo so long as Kodi shows as not installed from RetroPie 4.x as it only updates packages that are installed. (It works this out based on folders in /opt/retropie so it will ignore Jessie Kodi)

Actually it does (checked this before upgrading and it clearly said KODI wasn't installed). I've dealt with this several times removed pipplewares repro before updating to make sure. I hope you now understand my initial anoyance.

toto

@BuZz said in Is it really necessary to force users to use pippleware's KODI?:

I have updated the Kodi script so removal via RetroPie-Setup will remove pipplware repository.

Thanks, I will try that later this week, maybe tomorrow.

BuZz

@toto probably because you still had the repository installed. I don't understand your annoyance. We do this for free and have been trying to help. Perhaps you can try and be a little more understanding