Hi Peter, thanks for checking , is this the same issue that you had with previous version ? caused by ffmpeg ?
Sagi. On Thu, Nov 30, 2017 at 2:25 PM, Peter Snauwaert <peter.snauwa...@gmail.com> wrote: > HI Sagi, > > Just tried and get this: > rpm -Uvh kodi-17.6-151.1.x86_64.rpm > warning: kodi-17.6-151.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key > ID 53ab3a53: NOKEY > error: Failed dependencies: > libva-x11.so.1()(64bit) is needed by kodi-17.6-151.1.x86_64 > libva.so.1()(64bit) is needed by kodi-17.6-151.1.x86_64 > libva.so.1(VA_API_0.33.0)(64bit) is needed by > kodi-17.6-151.1.x86_64 > > Not sure what the problem is since I have > S | Name | Summary > | Type > --+----------------------------------+---------------------- > -------------------------------------+-------- > i | Mesa-libva | Mesa VA-API > implementation | package > i | libva-devel | Development files for the Video > Acceleration API | package > | libva-devel-32bit | Development files for the Video > Acceleration API | package > i | libva-drm2 | DRM backend for the Video > Acceleration API | package > | libva-drm2-32bit | DRM backend for the Video > Acceleration API | package > i | libva-gl-devel | Development files for the Video > Acceleration API | package > | libva-gl-devel-32bit | Development files for the Video > Acceleration API | package > i | libva-glx2 | GLX backend for the Video > Acceleration API | package > | libva-glx2-32bit | GLX backend for the Video > Acceleration API | package > | libva-utils | A collection of utilities and > examples to exercise VA-API | package > | libva-vdpau-driver | HW video decode support for VDPAU > platforms | package > i | libva-wayland2 | Wayland backend for the Video > Acceleration API | package > | libva-wayland2-32bit | Wayland backend for the Video > Acceleration API | package > i | libva-x11-2 | X11 backend for the Video > Acceleration API | package > | libva-x11-2-32bit | X11 backend for the Video > Acceleration API | package > i | libva2 | Video Acceleration > API | package > | libva2-32bit | Video Acceleration > API | package > > > With zypper this is the output. > > zypper install /tmp/kodi-17.6-151.1.x86_64.rpm > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: nothing provides libva-x11.so.1()(64bit) needed by > kodi-17.6-151.1.x86_64 > Solution 1: do not install kodi-17.6-151.1.x86_64 > Solution 2: break kodi-17.6-151.1.x86_64 by ignoring some of its > dependencies > > Kind regards, > peter > > > On Sat, Nov 25, 2017 at 4:18 PM, Sagi Ben-Akiva <sagi...@gmail.com> wrote: > >> Hi, >> >> Regarding libdvdcss, libdvdnav and libdvdread and >> "Added unneeded return to switch statements in libdvdnav-master >> vmget.c to silence rpmlint errors." >> >> I created a pull request in Kodi libdvdnav repo about a year ago but >> they don't want to merge it. >> https://github.com/xbmc/libdvdnav/pull/2 >> >> I also created a pull request in videolan : >> https://code.videolan.org/videolan/libdvdnav/issues/2 >> Can someone help in accepting them ? >> >> I'm currently building Kodi 17.6 in my home repo with the latest fixes >> from Dave (Thanks Dave, highly appreciated) >> https://pmbs.links2linux.de/package/show/home:sagiben/kodi >> >> Can someone with Tumbleweed check my build before I'm creating a pull >> request ? >> >> Thanks, >> Sagi. >> >> On Thu, Nov 23, 2017 at 8:09 PM, Peter Snauwaert < >> peter.snauwa...@gmail.com> wrote: >> >>> Awesome, thanks! >>> >>> On Thu, Nov 23, 2017 at 1:04 PM, Dave Plater <davejpla...@gmail.com> >>> wrote: >>> >>> > Fixed kodi, confirmed by email. Submitted sr#4048 >>> > Dave >>> > >>> > On 11/21/17, Dave Plater <davejpla...@gmail.com> wrote: >>> > > Kodi is made to build with it's internal (from >>> github.com/xbmc/FFmpeg) >>> > > ffmpeg until kodi 1.8x is released which has been rewritten to build >>> > > with ffmpeg 3.4. >>> > > It already builds with "internal" libdvdcss, libdvdnav and >>> libdvdread. >>> > > These have become a problem since the internal ffmpeg build. These >>> > > libs are statically linked. >>> > > See the bug references at the beginning of this thread. >>> > > Dave >>> > > >>> > > On 11/21/17, Olaf Hering <o...@aepfle.de> wrote: >>> > >> On Tue, Nov 21, Dave Plater wrote: >>> > >> >>> > >>> What I don't understand is none of these are related to ffmpeg and >>> why >>> > >>> tis wasn't a problem before. >>> > >> >>> > >> Before we try to force a different libffmpeg into kodi, it must be >>> > >> checked >>> > >> if the other libraries in the kodi process make some use of >>> libffmpeg. >>> > >> If they do, there will be most likely a runtime conflict and kodi >>> must >>> > >> be fixed to work with "any" libffmpeg. >>> > >> >>> > >> In case of no conflict it is likely easier to build a private >>> ffmpeg in >>> > >> %_libdir/ffmpeg3x and build kodi with RPATH pointing to that >>> directory. >>> > >> >>> > >> >>> > >> Olaf >>> > >> >>> > > >>> > >>> _______________________________________________ >>> Packman mailing list >>> Packman@links2linux.de >>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman >>> >> >> > _______________________________________________ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman