September 2024 - rpmfusion-developers

by Gary Buhrmaster

What is the current thinking on a schedule for RPMFusion to create the initial infrastructure for the EL 10 distribution? Fedora has opened EPEL10 koji targets, and there has been some activity getting packages built in EPEL10. From my observation here are still a lot of packages that need to be built for EPEL10 to make it a viable base for some packages in RPMFusion (I have opened Bugzillas for some packages I will be needing) but it might be nice for the RPMFusion packagers to be able to test, request additional EPEL10 branches and builds, and build their RPMFusion packages before C10S is expected to be available (2024Q4?). Thanks for any insight you can offer. Gary

1 week, 2 days

2
2
0 / 0

Mass rebuild results for F41

by Sérgio Basto

2 weeks, 3 days

4
5
0 / 0

Mass rebuild results for F41

by Sérgio Basto

1 month

3
4
0 / 0

[Bug 6835] New: Sponsorship request for wiki: miika

by RPM Fusion Bugzilla

https://bugzilla.rpmfusion.org/show_bug.cgi?id=6835 Bug ID: 6835 Summary: Sponsorship request for wiki: miika Product: Package Reviews Version: Current Hardware: x86_64 OS: GNU/Linux Status: NEW Severity: enhancement Priority: P1 Component: Review Request Assignee: rpmfusion-package-review(a)rpmfusion.org Reporter: miika.km.tuominen(a)gmail.com CC: rpmfusion-package-review(a)rpmfusion.org namespace: free Hello. I'm interested in contributing to the wiki, and it seems I need to get a sponsor to be able to do that. I did not find any instructions on getting a sponsorship in order to edit the wiki (without submitting a package to be reviewed), but I figured creating a ticket here was the most rational way. I was interested in improving specifically the "Howto/Optimus/NVIDIA PrimaryGPU Support" section, since currently it has instructions for setting Nvidia as the primary GPU only on X11, but not wayland (which is the only supported display server anyway). The reason I consider this important information is because on laptops, you need to have Nvidia as the primary driver in order to use a second monitor. In the spirit of leaving the campground cleaner than I found it, I would also like to add instructions to the contributing page on how to edit the wiki, as it took a while for me to find out what I have to do. And I'm still not sure, since the wiki login claims I don't have correct credentials - maybe it will work when I join the "wikiedit" group. Feel free to ask any questions. Miika -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 month, 1 week

1
4
0 / 0

About unmaintained package libva-intel-driver

by Nicolas Chauvet

Hi there, For the reminder libva-intel-driver VAAPI backend for old Intel hardware is unmaintained upstream but some fixes exist for working with Current Fedora. (1). As no maintainer step in in the ticket, I'm going to retire the package in f41+ Please take the package in our pkgdb https://admin.rpmfusion.org/pkgdb/package/free/libva-intel-driver/ If none step-in by the f41 GA, you will have to do the full review process to restore it. Thanks (1) https://github.com/rpmfusion/libva-intel-driver/pull/3 -- - Nicolas (kwizart)

1 month, 2 weeks

2
2
0 / 0

RPM Fusion update report 2024-09-28

by noreply＠rpmfusion.org

RPM Fusion update report ------------------------ Section free: ------------- Fedora 39 ------------- Pushed to testing: VirtualBox-7.1.2-1.fc39 VirtualBox-kmod-7.1.2-1.fc39 v4l2loopback-0.13.2-1.fc39 v4l2loopback-kmod-0.13.2-1.fc39 Pushed to stable: VirtualBox-7.1.0-2.fc39 VirtualBox-kmod-7.1.0-1.fc39 Fedora 40 ------------- Pushed to testing: VirtualBox-7.1.2-1.fc40 VirtualBox-kmod-7.1.2-1.fc40 cairo-dock-freeworld-3.5.1-1.fc40 jellyfin-10.9.11-1.fc40 v4l2loopback-0.13.2-1.fc40 v4l2loopback-kmod-0.13.2-1.fc40 Pushed to stable: VirtualBox-7.1.0-2.fc40 VirtualBox-kmod-7.1.0-1.fc40 audacity-freeworld-3.6.3-1.fc40 motion-4.7.0-1.fc40 python-ffmpeg-progress-yield-0.9.1-1.fc40 xroar-1.6.3-1.fc40 Fedora 41 ------------- Pushed to testing: VirtualBox-7.1.2-1.fc41 VirtualBox-kmod-7.1.2-1.fc41 cairo-dock-freeworld-3.5.99^20240926git7b3ac7f-1.fc41 jellyfin-10.9.11-1.fc41 mesa-freeworld-24.2.3-3.fc41 qt5-qtwebengine-freeworld-5.15.17-4.fc41 v4l2loopback-0.13.2-1.fc41 v4l2loopback-kmod-0.13.2-1.fc41 Pushed to stable: audacity-freeworld-3.6.3-1.fc41 cairo-dock-freeworld-3.5.99^20240915git1458bc8-1.fc41 mesa-freeworld-24.2.3-2.fc41 motion-4.7.0-1.fc41 pipewire-codec-aptx-1.2.4-1.fc41 python-ffmpeg-progress-yield-0.9.1-1.fc41 rpmfusion-free-release-41-0.2 xroar-1.6.3-1.fc41 EL 8 ------------- Pushed to testing: Pushed to stable: EL 9 ------------- Pushed to testing: Pushed to stable: VirtualBox-7.1.0-2.el9 VirtualBox-kmod-7.1.0-1.el9 Section nonfree: ------------- Fedora 39 ------------- Pushed to testing: discord-0.0.69-1.fc39 Pushed to stable: lpf-spotify-client-1.2.45.454-1.fc39 Fedora 40 ------------- Pushed to testing: discord-0.0.69-1.fc40 Pushed to stable: lpf-spotify-client-1.2.45.454-1.fc40 zerotier-one-1.14.1-1.fc40 Fedora 41 ------------- Pushed to testing: discord-0.0.69-1.fc41 Pushed to stable: lpf-spotify-client-1.2.45.454-1.fc41 rpmfusion-nonfree-release-41-0.2 zerotier-one-1.14.1-1.fc41 EL 8 ------------- Pushed to testing: Pushed to stable: EL 9 ------------- Pushed to testing: discord-0.0.69-1.el9 Pushed to stable: lpf-spotify-client-1.2.45.454-1.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

1 month, 2 weeks

1
0
0 / 0

Re: RPMFusion for EL 10 schedule?

by Gary Buhrmaster

On Fri, Sep 20, 2024 at 3:19 PM Gary Buhrmaster <gary.buhrmaster(a)gmail.com> wrote: > > On Wed, Sep 18, 2024 at 6:34 AM Nicolas Chauvet <kwizart(a)gmail.com> wrote: > > > Also I don't get why epel went with el10.0 dist. There will be > > strictly no matching with the RHEL package set. CentOS Stream has its > > own pace to update packages. So to me it's a wrong assumption that any > > epel tag for centos 10 stream would induce any compatibility with > > related RHEL versions. At least there is only currently one epel10 > > branch there. > > I *think* this is the thinking of dealing with the > legacy of "epel-next" (which was, shall we say, > somewhat problematic), which, while most times, > one does not need/want to upgrade a package > (as EL itself is *mostly" stable), there are times > when you want/need to deal with upgrading an > epel package if/only-if the base EL is updated > (from 10.0 to 10.1, for example), so there may > (eventually) be different minor dist targets in > various build instances and repos (epel10_1, > epel10_2, etc. as additional repos). I do not > recall that this has been fully fleshed out, or > if so, I do not recall it having been fully shared > (either of which may simply mean I am not > paying attention in the right places). A bit more information on some of the thinking about the epel10.0 dist. Comments involving 3rd party repository implications may be useful to the participants there.

1 month, 3 weeks

1
1
0 / 0

ffms2 moving to Fedora

by Dominik 'Rathann' Mierzejewski

Hi! It looks like ffms2 can be moved to Fedora now. I opened a review ticket with the 5.0-RC3 build. Cc'ing Igor, the original maintainer, though I suspect he might be too busy to keep maintaining it. Bugzilla ticket for reference: https://bugzilla.redhat.com/show_bug.cgi?id=2274319 I'll post again when it's ready to be retired. Regards, Dominik -- Fedora https://fedoraproject.org Deep in the human unconscious is a pervasive need for a logical universe that makes sense. But the real universe is always one step beyond logic. -- from "The Sayings of Muad'Dib" by the Princess Irulan

1 month, 3 weeks

1
1
0 / 0

RPM Fusion update report 2024-09-21

by noreply＠rpmfusion.org

RPM Fusion update report ------------------------ Section free: ------------- Fedora 39 ------------- Pushed to testing: VirtualBox-7.1.0-2.fc39 VirtualBox-kmod-7.1.0-1.fc39 Pushed to stable: mythtv-34.0-4.28.20240704gitc63d023aa8.fc39 Fedora 40 ------------- Pushed to testing: VirtualBox-7.1.0-2.fc40 VirtualBox-kmod-7.1.0-1.fc40 audacity-freeworld-3.6.3-1.fc40 motion-4.7.0-1.fc40 python-ffmpeg-progress-yield-0.9.1-1.fc40 xroar-1.6.3-1.fc40 Pushed to stable: audacity-freeworld-3.6.2-1.fc40 mythtv-34.0-4.28.20240704gitc63d023aa8.fc40 vdr-markad-4.1.6-1.fc40 Fedora 41 ------------- Pushed to testing: audacity-freeworld-3.6.3-1.fc41 cairo-dock-freeworld-3.5.99^20240915git1458bc8-1.fc41 mesa-freeworld-24.2.3-2.fc41 motion-4.7.0-1.fc41 pipewire-codec-aptx-1.2.4-1.fc41 python-ffmpeg-progress-yield-0.9.1-1.fc41 xroar-1.6.3-1.fc41 Pushed to stable: audacity-freeworld-3.6.2-1.fc41 mesa-freeworld-24.2.2-1.fc41 mythtv-34.0-4.28.20240704gitc63d023aa8.fc41 rpmfusion-free-release-41-0.2 vdr-markad-4.1.6-1.fc41 EL 8 ------------- Pushed to testing: Pushed to stable: EL 9 ------------- Pushed to testing: VirtualBox-7.1.0-2.el9 VirtualBox-kmod-7.1.0-1.el9 Pushed to stable: mythtv-34.0-4.28.20240704gitc63d023aa8.el9 Section nonfree: ------------- Fedora 39 ------------- Pushed to testing: discord-0.0.68-1.fc39 lpf-spotify-client-1.2.45.454-1.fc39 xorg-x11-drv-nvidia-560.35.03-5.fc39 Pushed to stable: Fedora 40 ------------- Pushed to testing: discord-0.0.68-1.fc40 lpf-spotify-client-1.2.45.454-1.fc40 xorg-x11-drv-nvidia-560.35.03-5.fc40 zerotier-one-1.14.1-1.fc40 Pushed to stable: unifi-8.4.59-1.fc40 Fedora 41 ------------- Pushed to testing: discord-0.0.68-1.fc41 lpf-spotify-client-1.2.45.454-1.fc41 xorg-x11-drv-nvidia-560.35.03-5.fc41 zerotier-one-1.14.1-1.fc41 Pushed to stable: rpmfusion-nonfree-release-41-0.2 unifi-8.4.59-1.fc41 EL 8 ------------- Pushed to testing: Pushed to stable: unifi-8.4.59-1.el8 EL 9 ------------- Pushed to testing: discord-0.0.68-1.el9 lpf-spotify-client-1.2.45.454-1.el9 Pushed to stable: unifi-8.4.59-1.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

1 month, 3 weeks

1
0
0 / 0

nvidia driver requirement on xorg server

by Gary Buhrmaster

I have not opened a formal "RFE" bug in bugzilla on this (it is not clear it is appropriate there), but do the RPMFusion maintainers of the recent nvidia drivers have a plan to eliminate the requirement for the xorg server? As of Fedora 40 it is (in theory) possible to remove the xorg server itself, but the current nvidia driver/akmods (apparently) still has a hard requirement on the xorg server itself. I would like to be able to remove the xorg server (and associated libraries), and install just the nvidia kernel driver (and use the various drm / wayland functionality). I realize this is likely a large request, but I would like to at least know if the maintainers have a (long term) consideration of moving in that direction. While I have not actually validated it works, one of the alternative nvidia driver repos at least suggests they can install the driver without pulling in the xorg server. Thanks for any insight you can provide.

1 month, 3 weeks

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

rpmfusion-developers September 2024