> Looking closer at kodi it turns out it has a -l /--lircdev CLI option.
> problem solved. This also means that thomas can walk-around the problem
> by configuring kodi instead of using the symlink.
Yes and that is the way I do it right now. This is for me the save way
to solve future changes.
Package: kodi
Version: 2:17.0~beta6+dfsg1-1
Severity: normal
Dear Maintainer,
kodi is hard coded to the wrong "device" path to lirc.
The binary tries /dev/lircd but the "device" (which is a socket!)
can be found at /var/run/lirc/lircd.
- write ~/.kodi/userdata/Lircmap.xml according to working i
Package: kodi-pvr-vdr-vnsi
Version: 2.6.7-1
Severity: normal
Dear Maintainer,
activating the vnsi add on fails with unstable kodi:
ERROR: PVR - Add-on 'VDR VNSI Client' is using an incompatible API
version. XBMC minimum API version = '5.2.1', add-on API version '5.2.0'
-- System Information:
De
Package: kodi-pvr-vdr-vnsi
Version: 1.11.15-1
Severity: normal
Dear Maintainer,
with upgrade to 17.0~beta5 this addon does not work anymore. Log output:
ERROR: PVR - Add-on 'VDR VNSI Client' is using an incompatible API
version. XBMC minimum API version = '5.2.0', add-on API version '4.1.0'
At
