Hi Justus!
I have incorporated the changes recommended by Helmut to 20.x alpha build.
I installed kodi:i386 in amd64 container to verify installation completes:
echo "deb [trusted=yes] file:///external-repo ./" >
/etc/apt/sources.list.d/local-repo.list
dpkg --add-architecture i386
apt-get
Hi Helmut!
>Why would you want to do that? stable releases do have bugs and unless
>they're severe, we don't usually fix them.
I want to keep 19.x updates consistent with upstream because all 19.x point
releases
are bugfixes and only bugfixes. Plus, as a member of Team Kodi, it is my duty to
On Sat, Oct 16, 2021 at 04:58:34PM +, Vasyl Gello wrote:
> >If you don't like removing
> >Multi-Arch: foreign from kodi-data, there is another way out: Move the
> >python modules to a new kodi-python-addons package. Move the relevant
> >python dependencies to this package. Make it
On Sat, 2021-10-16 at 17:29 +, Vasyl Gello wrote:
> Hi Adam!
>
> CC'ing you because I would like to understand if removing "m-a:
> foreign" from kodi-data might affect dependency resokution on stable.
>
I'm not really sure what you're asking here. The effect on dependency
resolution on a
Hi Adam!
CC'ing you because I would like to understand if removing "m-a: foreign" from
kodi-data might affect dependency resokution on stable.
I really hope it will not put a roadblock to future Kodi 19.x updates in stable
:)
--
Vasyl Gello
==
Hi Helmut!
>I vaguely guess that we're in case b) here.
You are absolutely correct! Kodi data package hosts code which is executed by
Kodi binary and
it depends on python3:any.
>If you don't like removing
>Multi-Arch: foreign from kodi-data, there is another way out: Move the
>python modules
Hi,
I think this bug has been diverted to being able to use widevinecdm.
While that turns the original request a little academic, there still is
a bug there.
On Sat, Oct 16, 2021 at 02:07:19PM +0200, Justus Winter wrote:
> 13:37 but, kodi-data (which is ma: foreign) depends on
>
Vasyl Gello writes:
> What's better about solution to widevinecdm is that it'll solve eternal pain
> of CoreELEC and LibreELEC requiring them to stick with armv7l userspace and
> Kodi only to get Widevine support.
>
> However I have an idea to test. Are you able to test builds?
Yes.
Hi Justus!
What's better about solution to widevinecdm is that it'll solve eternal pain of
CoreELEC and LibreELEC requiring them to stick with armv7l userspace and Kodi
only to get Widevine support.
However I have an idea to test. Are you able to test builds?
--
Vasyl Gello
Vasyl Gello writes:
> Well, as far as I have researched, there might be even the possibility
> to co-install two different Kodi sets for different architectures, but
> that will require fixing the whole Python packaging down to
> python3.x-minimal.
>
> So what did you, do specifically? Did you
Hi Justus!
Well, as far as I have researched, there might be even the possibility to
co-install two different Kodi sets for different architectures, but that will
require fixing the whole Python packaging down to python3.x-minimal.
So what did you, do specifically? Did you rebuild Kodi with
Package: kodi-data
Version: 2:19.1+dfsg2-2
Severity: normal
Dear Maintainer,
Kodi cannot be installed on a foreign architecture. I asked in
#multiarch for help, and this was our discussion:
13:36 I'm trying to install kodi:armhf on arm64
13:37 but, kodi-data (which is ma: foreign) depends on
12 matches
Mail list logo
