About ELC 8/9 and rpmfusion buildsys
by Nicolas Chauvet
Hi there,
With RHEL 8.6 published today and our repositories still using the
outdated 8.5 CentOS LInux, I've had a look to use our RHEL
subscription to access newer content.
Unfortunately, this didn't went so good and while I haven't saw any
issue to use a subscribed Fedora(34) builders to access RHEL
repositories directly with mock, using some others tools that are
mandated by koji (mergerepo_c among others) are total blocker without
a mean to workaround the design issue anytime soon.
(filled https://bugzilla.rpmfusion.org/show_bug.cgi?id=6295 if anyone
interested in details).
Because of this, the only solution is to use the alma linux
repositories so far. This clone is the only to support ppc64le so we
could benefit for this arch (which usage might be limited, but still
relevant).
I've made the switch and tested a scratch build that succeeded at
https://koji.rpmfusion.org/koji/taskinfo?taskID=543533
In a later step, we can add the alma "devel" repository if we miss
-devel packages there.
Thanks
--
-
Nicolas (kwizart)
1 year, 4 months
RPM Fusion Fedora 36 GA
by Sérgio Basto
Hello,
I happily announce that RPM Fusion Fedora 36 is General Available (GA).
Thank you all that make it happen .
Best regards,
--
Sérgio M. B.
1 year, 4 months
RPM Fusion update report 2022-05-08
by noreply＠rpmfusion.org
RPM Fusion update report
------------------------
Section free:
-------------
Fedora 34
-------------
Pushed to testing:
chromium-freeworld-101.0.4951.54-1.fc34
Pushed to stable:
mock-rpmfusion-free-36.1-1.fc34
Fedora 35
-------------
Pushed to testing:
chromium-freeworld-101.0.4951.54-1.fc35
vdr-markad-3.0.22-1.fc35
Pushed to stable:
mock-rpmfusion-free-36.1-1.fc35
python-ffmpeg-normalize-1.23.0-1.fc35
Fedora 36
-------------
Pushed to testing:
vdr-markad-3.0.22-1.fc36
Pushed to stable:
rpmfusion-free-release-36-1
EL 7
-------------
Pushed to testing:
Pushed to stable:
mock-rpmfusion-free-36.1-1.el7
EL 8
-------------
Pushed to testing:
Pushed to stable:
mock-rpmfusion-free-36.1-1.el8
python-ffmpeg-normalize-1.23.0-1.el8
EL 9
-------------
Pushed to testing:
Pushed to stable:
libheif-1.12.0-4.el9
mock-rpmfusion-free-36.1-1.el9
Section nonfree:
-------------
Fedora 34
-------------
Pushed to testing:
lpf-mscore-fonts-2.2-6.fc34
Pushed to stable:
lpf-spotify-client-1.1.84.716-1.fc34
mock-rpmfusion-nonfree-36.1-1.fc34
Fedora 35
-------------
Pushed to testing:
frogatto-1.3.3-25.fc35
lpf-mscore-fonts-2.2-6.fc35
Pushed to stable:
lpf-spotify-client-1.1.84.716-1.fc35
mock-rpmfusion-nonfree-36.1-1.fc35
Fedora 36
-------------
Pushed to testing:
frogatto-1.3.3-25.fc36
lpf-mscore-fonts-2.2-6.fc36
Pushed to stable:
rpmfusion-nonfree-release-36-1
EL 7
-------------
Pushed to testing:
Pushed to stable:
mock-rpmfusion-nonfree-36.1-1.el7
EL 8
-------------
Pushed to testing:
Pushed to stable:
lpf-spotify-client-1.1.84.716-1.el8
mock-rpmfusion-nonfree-36.1-1.el8
EL 9
-------------
Pushed to testing:
Pushed to stable:
mock-rpmfusion-nonfree-36.1-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 year, 4 months
ABI breaks of CentOS Stream and minimizing damage
by =?UTF-8?B?UGV0ciBNZW7FocOtaw==?=
Hello,
I were thinking about a discussion about CentOS Stream and complaint it
is unusable, because it is breaking ABI not only at release time. It was
about poppler soname change and some depending epel package. But
rpmfusion have similar problem.
If there is change of soname in CentOS, does exist any process to notify
epel or rpmfusion packages maintainers that something would break
depending package(s) in other repositories? Do you think it would be
worth using some kind of automation to create bugs automatically or at
least send mails, if upstream repository were preparing a new change
affecting some packages here?
Does already exist a way to minimize time, when packages conflict
because depending packages were not yet rebuilt? Something different
from maintainer of fedora/centos package doing those notifications
manually? Do you think it would be worth the time?
Regards,
Petr
--
Petr Menšík, Fedora project contributor
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
1 year, 4 months
RPM Fusion update report 2022-05-03
by noreply＠rpmfusion.org
RPM Fusion update report
------------------------
Section free:
-------------
Fedora 34
-------------
Pushed to testing:
mock-rpmfusion-free-36.1-1.fc34
Pushed to stable:
chromium-freeworld-101.0.4951.41-1.fc34
compat-ffmpeg28-2.8.19-1.fc34
Fedora 35
-------------
Pushed to testing:
mock-rpmfusion-free-36.1-1.fc35
python-ffmpeg-normalize-1.23.0-1.fc35
Pushed to stable:
chromium-freeworld-101.0.4951.41-1.fc35
cinelerra-gg-5.1.2022.03-1.fc35
compat-ffmpeg28-2.8.19-1.fc35
ffmpegthumbs-22.04.0-1.fc35
gr-dab-0.4-10.fc35
python-ffmpeg-normalize-1.22.10-1.fc35
rpmfusion-free-appstream-data-35-3.fc35
telegram-desktop-3.7.3-1.fc35
Fedora 36
-------------
Pushed to testing:
Pushed to stable:
chromium-freeworld-101.0.4951.41-1.fc36
chromium-freeworld-101.0.4951.54-1.fc36
cinelerra-gg-5.1.2022.03-1.fc36
compat-ffmpeg28-2.8.19-1.fc36
ffmpeg-5.0.1-3.fc36
ffmpegthumbs-22.04.0-1.fc36
guvcview-2.0.8-1.fc36
kdenlive-22.04.0-1.fc36
mock-rpmfusion-free-36.1-1.fc36
performous-1.2.0-2.fc36
python-ffmpeg-normalize-1.22.10-1.fc36
python-ffmpeg-normalize-1.23.0-1.fc36
rpmfusion-free-release-36-1
telegram-desktop-3.7.3-1.fc36
EL 7
-------------
Pushed to testing:
mock-rpmfusion-free-36.1-1.el7
Pushed to stable:
compat-ffmpeg28-2.8.19-1.el7
ffmpeg-3.4.10-1.el7
EL 8
-------------
Pushed to testing:
mock-rpmfusion-free-36.1-1.el8
python-ffmpeg-normalize-1.23.0-1.el8
Pushed to stable:
EL 9
-------------
Pushed to testing:
libheif-1.12.0-4.el9
mock-rpmfusion-free-36.1-1.el9
Pushed to stable:
Section nonfree:
-------------
Fedora 34
-------------
Pushed to testing:
lpf-spotify-client-1.1.84.716-1.fc34
mock-rpmfusion-nonfree-36.1-1.fc34
Pushed to stable:
Fedora 35
-------------
Pushed to testing:
lpf-spotify-client-1.1.84.716-1.fc35
mock-rpmfusion-nonfree-36.1-1.fc35
Pushed to stable:
rpmfusion-nonfree-appstream-data-35-3.fc35
Fedora 36
-------------
Pushed to testing:
Pushed to stable:
lpf-spotify-client-1.1.84.716-1.fc36
mock-rpmfusion-nonfree-36.1-1.fc36
rpmfusion-nonfree-release-36-1
EL 7
-------------
Pushed to testing:
mock-rpmfusion-nonfree-36.1-1.el7
Pushed to stable:
EL 8
-------------
Pushed to testing:
lpf-spotify-client-1.1.84.716-1.el8
mock-rpmfusion-nonfree-36.1-1.el8
Pushed to stable:
EL 9
-------------
Pushed to testing:
mock-rpmfusion-nonfree-36.1-1.el9
Pushed to stable:
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 year, 4 months
[Bug 6274] New: Wishlist request for SoapySDRPlay3
by RPM Fusion Bugzilla
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6274
Bug ID: 6274
Summary: Wishlist request for SoapySDRPlay3
Product: Package Reviews
Version: Current
Hardware: All
OS: GNU/Linux
Status: NEW
Severity: enhancement
Priority: P1
Component: Review Request
Assignee: rpmfusion-package-review(a)rpmfusion.org
Reporter: mail(a)asciiwolf.com
CC: rpmfusion-package-review(a)rpmfusion.org
namespace: nonfree
I do not have a Wiki account and did not found any way to create one, so I am
adding it here. I would be glad if someone from the RPM Fusion team could add
the wishlist request posted below to https://rpmfusion.org/Wishlist. Thanks!
Request: SoapySDRPlay3
Summary: SoapySDRPlay3 is a module for SoapySDR that adds support for SDRplay
devices. SoapySDR is a Vendor Neutral and Platform Independent Software-Defined
Radio (SDR) Support Library.
URL: https://github.com/pothosware/SoapySDRPlay3
Why not in Fedora: SoapySDR is already packaged in Fedora, however the
SoapySDRPlay3 module is not because it depends on a proprietary SDRplay API
(that has to be downloaded from https://www.sdrplay.com and installed
manually).
Notes: There is not any tag/release of this software yet, however the last
Git commit (b789d59 in the time of writing this) works without any problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
1 year, 4 months
