[Bug 30] Tracker : Sponsorship Request
https://bugzilla.rpmfusion.org/show_bug.cgi?id=30 Sérgio Basto changed: What|Removed |Added Depends on|6387| Referenced Bugs: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6387 [Bug 6387] Review request: kodi-inputstream-ffmpegdirect - inputstream.ffmpegdirect for Kodi -- You are receiving this mail because: You are the assignee for the bug.___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
[Bug 6387] Review request: kodi-inputstream-ffmpegdirect - inputstream.ffmpegdirect for Kodi
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6387 Sérgio Basto changed: What|Removed |Added CC||ser...@serjux.com Blocks|30 | --- Comment #1 from Sérgio Basto --- you are already in packager group Referenced Bugs: https://bugzilla.rpmfusion.org/show_bug.cgi?id=30 [Bug 30] Tracker : Sponsorship Request -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [intel-media-driver] Update to 22.5.4
Hi, On Mon, Oct 24, 2022 at 2:48 PM Dominik 'Rathann' Mierzejewski < domi...@greysector.net> wrote: > Intel's releases for oneVPL-intel-gpu list the corresponding component > versions: > https://github.com/oneapi-src/oneVPL-intel-gpu/releases > > oneVPL GPU Runtime: > https://github.com/oneapi-src/oneVPL-intel-gpu/releases/tag/intel-onevpl-22.5.4 > oneVPL Dispatcher and Samples: > https://github.com/oneapi-src/oneVPL/releases/tag/v2022.2.2 > Driver: > https://github.com/intel/media-driver/releases/tag/intel-media-22.5.4 > Gmmlib: > https://github.com/intel/gmmlib/releases/tag/intel-gmmlib-22.2.0 > libva: https://github.com/intel/libva/releases/tag/2.16.0 > libva-utils: https://github.com/intel/libva-utils/releases/tag/2.16.0 > > So, by "in sync" I mean keep the oneVPL and oneVPL-intel-gpu packages at > the version corresponding to other components released at the same time > per Fedora branch. I'm fine with this, but I think the "releases" you see should be considered the minimum recommended versions that should go together, not as a hard list.. The repositories listed here for RHEL/Ubuntu actually mix and match stuff compared to the "release" bundles: https://dgpu-docs.intel.com/installation-guides/index.html Besides this, I'm fine with keeping stuff in sync, no issue from my side. Thanks, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.org/ ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [intel-media-driver] Update to 22.5.4
Le lun. 24 oct. 2022 à 14:48, Dominik 'Rathann' Mierzejewski a écrit : > > On Sunday, 23 October 2022 at 10:42, Simone Caronni wrote: > > Hi Dominik, > > > > sorry I was on holiday. > > > > On Mon, Oct 17, 2022 at 2:13 PM Dominik 'Rathann' Mierzejewski < > > domi...@greysector.net> wrote: > > > > > Simone, would it make sense keep the oneVPL-intel-gpu package in > > > sync with intel-media-driver (RPM Fusion), intel-mediasdk and > > > intel-gmmlib (Fedora) in all branches? > > > > Yes we can, I've given you admin access to both oneVPL and > > oneVPL-intel-gpu, even though I don't understand what you mean by "in > > sync". The versioning is all different among the various components > > both in terms of format and significance and in most cases there is > > really no dependency between them. > > Intel's releases for oneVPL-intel-gpu list the corresponding component > versions: > https://github.com/oneapi-src/oneVPL-intel-gpu/releases > > oneVPL GPU Runtime: > https://github.com/oneapi-src/oneVPL-intel-gpu/releases/tag/intel-onevpl-22.5.4 > oneVPL Dispatcher and Samples: > https://github.com/oneapi-src/oneVPL/releases/tag/v2022.2.2 > Driver: > https://github.com/intel/media-driver/releases/tag/intel-media-22.5.4 > Gmmlib: https://github.com/intel/gmmlib/releases/tag/intel-gmmlib-22.2.0 > libva: https://github.com/intel/libva/releases/tag/2.16.0 > libva-utils: https://github.com/intel/libva-utils/releases/tag/2.16.0 > > So, by "in sync" I mean keep the oneVPL and oneVPL-intel-gpu packages at > the version corresponding to other components released at the same time > per Fedora branch. > > > Currently, intel-media-driver and intel-mediasdk versions are the > > > following: > > > intel-mediasdk intel-media-driver intel-gmmlib > > > F38: 22.5.4 22.5.4 22.2.1 > > > F37: 22.4.4 22.4.4 22.1.7 > > > F36: 22.3.0 22.3.1 22.1.7 > > > F35: 21.4.3 21.4.3 21.3.5 > > > > > > As you can see, we're only updating to the official releases: > > > https://github.com/Intel-Media-SDK/MediaSDK/releases > > > https://github.com/intel/media-driver/releases > > > not to each tagged version. > > > > Any reason for this? Intel updates to the tagged releases as well when > > possible in their repository. They usually contain bugfixes. > > What do you mean by "their repository"? > > Updating only to official releases was Nicholas' idea. Perhaps he can > elaborate here. My take is that the official releases of the components > are tested by Intel together as a set, so deviating from these versions > brings us into untested territory, which we'd rather avoid. Well, the intel versioning related to the multimedia stack is weird for the least, I've tried to ask for clarification (I cannot find out the ticket from any on the related intel github projects). But the main idea is that anything not in tagged with "released" or in the same branch, is pre-release beta/alpha/wip software (whatever you call it). For example intel-media-driver 22.6.0 is pre-release and might rely on matching pre-release software as of libva-2.17git, gmmlib-22.3 (which broke ABI compared with 22.2) and all (including indirect dependencies to the opencl stack). Of course, like any software, you can build many combinations and assume things works, but then you will lack many of the advertised feature and bring bugs across fedora releases. As a side note, I plan to update to libva-2.16 and all in f37+ only as 0day updates... (with the libva ABI bug fixed as I hope). This will be coordinated with the intel-opencl stack maintainer Thanks for rising the issue. ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [intel-media-driver] Update to 22.5.4
On Sunday, 23 October 2022 at 10:42, Simone Caronni wrote: > Hi Dominik, > > sorry I was on holiday. > > On Mon, Oct 17, 2022 at 2:13 PM Dominik 'Rathann' Mierzejewski < > domi...@greysector.net> wrote: > > > Simone, would it make sense keep the oneVPL-intel-gpu package in > > sync with intel-media-driver (RPM Fusion), intel-mediasdk and > > intel-gmmlib (Fedora) in all branches? > > Yes we can, I've given you admin access to both oneVPL and > oneVPL-intel-gpu, even though I don't understand what you mean by "in > sync". The versioning is all different among the various components > both in terms of format and significance and in most cases there is > really no dependency between them. Intel's releases for oneVPL-intel-gpu list the corresponding component versions: https://github.com/oneapi-src/oneVPL-intel-gpu/releases oneVPL GPU Runtime: https://github.com/oneapi-src/oneVPL-intel-gpu/releases/tag/intel-onevpl-22.5.4 oneVPL Dispatcher and Samples: https://github.com/oneapi-src/oneVPL/releases/tag/v2022.2.2 Driver: https://github.com/intel/media-driver/releases/tag/intel-media-22.5.4 Gmmlib: https://github.com/intel/gmmlib/releases/tag/intel-gmmlib-22.2.0 libva: https://github.com/intel/libva/releases/tag/2.16.0 libva-utils: https://github.com/intel/libva-utils/releases/tag/2.16.0 So, by "in sync" I mean keep the oneVPL and oneVPL-intel-gpu packages at the version corresponding to other components released at the same time per Fedora branch. > Currently, intel-media-driver and intel-mediasdk versions are the > > following: > > intel-mediasdk intel-media-driver intel-gmmlib > > F38: 22.5.4 22.5.4 22.2.1 > > F37: 22.4.4 22.4.4 22.1.7 > > F36: 22.3.0 22.3.1 22.1.7 > > F35: 21.4.3 21.4.3 21.3.5 > > > > As you can see, we're only updating to the official releases: > > https://github.com/Intel-Media-SDK/MediaSDK/releases > > https://github.com/intel/media-driver/releases > > not to each tagged version. > > Any reason for this? Intel updates to the tagged releases as well when > possible in their repository. They usually contain bugfixes. What do you mean by "their repository"? Updating only to official releases was Nicholas' idea. Perhaps he can elaborate here. My take is that the official releases of the components are tested by Intel together as a set, so deviating from these versions brings us into untested territory, which we'd rather avoid. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
RPM Fusion update report 2022-10-24
RPM Fusion update report Section free: - Fedora 35 - Pushed to testing: faad2-2.10.1-1.fc35 zoneminder-1.36.30-2.fc35 Pushed to stable: mpd-0.23.10-1.fc35 ndiswrapper-kmod-1.63-7.fc35 vlc-3.0.18-1.fc35 Fedora 36 - Pushed to testing: faad2-2.10.1-1.fc36 xpra-codecs-freeworld-4.4-1.fc36 zoneminder-1.36.30-2.fc36 Pushed to stable: ffmpeg-5.0.1-8.fc36 libde265-1.0.9-1.fc36 mpd-0.23.10-1.fc36 ndiswrapper-kmod-1.63-7.fc36 vlc-3.0.18-1.fc36 Fedora 37 - Pushed to testing: faad2-2.10.1-1.fc37 xpra-codecs-freeworld-4.4-1.fc37 zoneminder-1.36.30-2.fc37 Pushed to stable: ffmpeg-5.1.2-3.fc37 libde265-1.0.9-1.fc37 mpd-0.23.10-1.fc37 ndiswrapper-kmod-1.63-7.fc37 vlc-3.0.18-1.fc37 EL 7 - Pushed to testing: zoneminder-1.36.30-2.el7 Pushed to stable: vlc-3.0.18-1.el7 EL 8 - Pushed to testing: zoneminder-1.36.30-2.el8 Pushed to stable: ffmpeg-4.2.8-1.el8 mpd-0.23.10-1.el8 vlc-3.0.18-1.el8 EL 9 - Pushed to testing: faad2-2.10.1-1.el9 zoneminder-1.36.30-2.el9 Pushed to stable: ffmpeg-5.1.2-3.el9 libde265-1.0.9-1.el9 vlc-3.0.18-1.el9 Section nonfree: - Fedora 35 - Pushed to testing: discord-0.0.21-1.fc35 Pushed to stable: broadcom-wl-6.30.223.271-21.fc35 wl-kmod-6.30.223.271-45.fc35 Fedora 36 - Pushed to testing: discord-0.0.21-1.fc36 Pushed to stable: broadcom-wl-6.30.223.271-21.fc36 wl-kmod-6.30.223.271-45.fc36 Fedora 37 - Pushed to testing: discord-0.0.21-1.fc37 Pushed to stable: broadcom-wl-6.30.223.271-21.fc37 fdk-aac-2.0.2-5.fc37 wl-kmod-6.30.223.271-45.fc37 EL 7 - Pushed to testing: Pushed to stable: broadcom-wl-6.30.223.271-21.el7 wl-kmod-6.30.223.271-45.el7 EL 8 - Pushed to testing: Pushed to stable: broadcom-wl-6.30.223.271-21.el8 wl-kmod-6.30.223.271-45.el8 EL 9 - Pushed to testing: Pushed to stable: broadcom-wl-6.30.223.271-21.el9 wl-kmod-6.30.223.271-45.el9 Theses packages will be available in main mirror in a few hours. Wait for local mirrors to sync Please report any issue to https://bugzilla.rpmfusion.org ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
