Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Update to upstream version '19.4+dfsg1'
with Debian dir 785df2d7aaebc18d476d910cf727ffaf5fba0d28

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

  * Build native JsonSchemaBuikder and TexturePacker
    before configuring Kodi
  * Disable building TexturePacker statically
  * Add proper build-architecture depends on
    GIF, JPEG, LZO2, PNG

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

As pointed by Johannes Schauer Marin Rodrigues (josch) in this
debian-cross mailing list thread:
https://lists.debian.org/debian-cross/2021/10/msg00036.html


it makes sense to determine which packages provide parts
that need to be linked into the build of Kodi and which packages
are supplementary tools.

For cross-compiling, supplementary / helper tools can be marked
as "arch:native" to avoid execition of code for different
architecture, if they are not already marked as "multi-arch: foreign"
by their maintainers.

This commit marks groovy and libcommons-lang-java as arch:native,
because apt resolver treats them as host-arch during the resolution
of build dependencies and fails to find them because they are arch:all.
Also, default-jre must be native arch to speed building up.

The known-problematic python3-dev dependency is replaced with
libpython3-dev, python3-dev:any per josch's advice.

Modification of pbuilder-satisfydepends-apt to pass debug flags:

  -o Debug::pkgDepCache::Marker=yes \
  -o Debug::pkgDepCache::AutoInstall=yes \
  -o Debug::pkgProblemResolver=yes

revealed that libpython3.9-minimal:host is picked by samba-libs,
which is a dependency of libsmbclient-dev.

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

.. to align with upstream packaging scheme.

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

The user reported the inability install armhf Kodi on arm64
board due to kodi-data:all depending on python3-{pil,pycryptodome}:any

As Helmut Grohne pointed out, the multi-arch dependency resolver
selects only native architecture packages (the one built for
'bare' processor) if arch:all package depends on arch:any packages.

To resolve this issue, the following changes to packaging were made:

  * Python dependencies were moved from kodi-data:all to kodi-bin:any,
    because python code in '/usr/share/kodi/addons' is useless without
    kodi-bin. Also, kodi-data is too big to keep it as arch:any.

  * kodi-eventclients-{dev,kodi-send,ps3,zeroconf}:all become arch:any.
    They install binaries in '/usr/bin'.

  * New packages kodi-eventclients-dev-common:all and
    kodi-eventclients-python:any are added.

  * kodi-eventclients-python needs only python3-bluez, while
    kodi-eventclients-ps3 needs python3-usb and python3-pyudev.

  * '/usr/bin/dh_kodiaddon' moved to kodi-addons-dev:any

  * Dependencies on source/binary versions are revised according to
    https://wiki.debian.org/binNMU



Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

  * Re-order patches in debian/patches/kodi
  * Rebase cdatetime-std-chrono topic patches
  * Rebase libdvdread patches

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

It is used only on Windows and UWP platforms.

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Vasyl Gello authored Oct 24, 2021 and Mattia Rizzolo committed Oct 24, 2021

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Vasyl Gello authored Oct 24, 2021 and Mattia Rizzolo committed Oct 24, 2021

  * Drop patches merged upstream:

    kodi/0006-fix-s390x-build.patch
    kodi/0009-fix-alpha-build.patch
    kodi/0014-Fix-ppc64el-build-kernel-bitness-detection.patch
    kodi/0021-Detect-and-honor-big-endian-arch.patch
    kodi/0022-Add-metainfo.patc

  * Refresh fuzzy patches

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Vasyl Gello authored Oct 24, 2021 and Mattia Rizzolo committed Oct 24, 2021

Update to upstream version '19.3+dfsg1'

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

During reproducibility test on i386 an old bug was spotted.

CMake does detect ARCH as 'x86_64-linux' if the host system
is 'amd64', ignoring the bitness requested by 'dpkg-buildpackage'.

This results in differing file names for libdvdnav if built
with 'KERNEL' variation by 'reprotest'.

Also arrange if-clauses to match buildd architecture list.

As of now, it is not needed to add if-clauses for:

  * 'arm64' - because 'cmake/scripts/ArchSetup.cmake' sets
    a proper architecture from CPU,
  * 'x32' - because there is no varition implemented for
    this architecture upstream

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Thanks to Matthias Klumpp (@ximion):

https://github.com/ximion/appstream-generator/issues/98



Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

  * Drop merged workaround for #989814
  * Add package metainfo (PR#20266)

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>

Update to upstream version '19.2+dfsg1'
with Debian dir c6681df274aaa10dbe86a0c75f3d9de5ccb5f001

Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>