Package Base Details: kodi-devel

Git Clone URL: (read-only)
Keywords: kodi kodi-devel
Submitter: alucryd
Maintainer: MarcinWieczorek (graysky)
Last Packager: graysky
Votes: 32
Popularity: 0.161333
First Submitted: 2014-08-11 23:33
Last Updated: 2019-06-20 19:53

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

butler360 commented on 2019-01-08 23:42

I did check the timestamp and it corresponded to when I installed kodi-devel-eventclients.

graysky commented on 2019-01-07 12:30

DTS = date time stamp (ie did you have a version that overwrote this package's copy on the file system). If not, I do not understand how your build from this PKGBUILD would have the incorrect shebang.

butler360 commented on 2019-01-07 05:47

It does belong to this package:

> $ pacman -Qo /usr/bin/kodi-send
/usr/bin/kodi-send is owned by kodi-devel-eventclients 18.0rc4-1

What does DTS refer to?

> $ pacman -Qi kodi-send
error: package 'kodi-send' was not found

graysky commented on 2019-01-06 13:40

@butler360 - All the addons including kodi-send should have their respective shebang statements adjusted, see:

So the question is why is your build not doing that... does /usr/bin/kodi-send on your filesystem actually belong to this package? What is the DTS on it? What is the output of pacman -Qi kodi-send?

butler360 commented on 2019-01-06 08:17

OK actually it works if I manually edit the shebang for kodi-send to use python3 instead of 2.

butler360 commented on 2019-01-06 08:07

When I try to run kodi-send I get an import error for xbmcclient.

> $ kodi-send --action="Up"
Traceback (most recent call last):
  File "/usr/bin/kodi-send", line 30, in <module>
    from xbmcclient import *
ImportError: No module named xbmcclient

Seems it got installed into the packages dir for python3 rather than 2:

> $ locate xbmcclient

Is this a problem with the PKGBUILD or might I have done something wrong?

graysky commented on 2018-12-20 18:38

You can try building with makepkg but best practice is to use a chroot which is dead simple. I stand by my statement about AUR helpers btw.

tadly commented on 2018-12-20 13:51

Sorry but I wholeheartedly disagree.
As I've already mentioned I've never had to do a clean chroot build up until this point and I've been using arch for 4-5 years now relaying on a lot of AUR packages.
So saying that "AUR helpers rarely help" is just not right.
But I don't want to start a discussion in the comments of an AUR package so I'll leave it at that. :)

graysky commented on 2018-12-18 16:38

AUR helpers rarely help. If you read through the AUR comments, you'll find lots of different examples of build failures because of AUR helpers.

tadly commented on 2018-12-18 15:16

@graysky Yeah, sorry for that.
No, I was using an aur helper.
Never had to do a clean chroot build with any package ever so I kinda forgot this is a thing.
Build seems to be getting further this time around.