[Johpin]

Installing IPTV Manager for Kodi 20.3 and 20.5 on Raspberry Pi OS Bookworm (64 bits) and Slackware aarch64 gives the following message:
The dependency on pvr.iptsimple version 3.8.8 could not be satisfied.

On an Android 13 device and on an Android 11 TV the addon IPTV Manager pulled in
all necessary depedencies (Kodi 20.5). For Raspberry Pi OS Bookworm (64 bits)
and Slackware aarch64 it seems to be broken.

Could this be repaired, so it is not necessary anymore to compile addons like
inputstream.ffmpegdirect, inputstream.rtmp and pvr.iptvsimple?

[DarrenHill]

Can you not just install them via apt or whatever package manager is appropriate?

[Johpin]

Can you not just install them via apt or whatever package manager is appropriate?

For Raspberry Pi OS Bookworm (64 bits) it will not be straightforward:

sudo apt install kodi-inputstream-ffmpegdirect
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kodi-inputstream-ffmpegdirect : Depends: kodi-api-inputstream (>= 3.2.0)
                                 Depends: kodi-api-inputstream (< 3.3.0)
E: Unable to correct problems, you have held broken packages.

This issue can found in
https://github.com/raspberrypi/bookworm-...issues/144
As I understood it can be solved by APT pinning, but I didn't try.

Slackware does not have a package manager, only Slackbuilds to compile and build packages from source code.
There is no slackbuild for inputstream.ffmpegdirect (with patches).

[DarrenHill]

OK.

Neither of those are actually platform that we directly support, they are community/third party supported (or self-build).
So the updated package would need to be prepared and offered by the package repo provider.

The short answer to your original question would be yes it could probably be done, but not by us as we are not the provider in these cases.