RPM Fusion update report 2021-02-28
by noreply＠rpmfusion.org
RPM Fusion update report
------------------------
Section free:
-------------
Fedora 32
-------------
Pushed to testing:
mythtv-31.0-15.139.20210226gitb6ddf202a4.fc32
shotcut-21.02.27-1.fc32
vdr-markad-2.6.3-1.fc32
vdr-softhddevice-1.0.14-1.fc32
Pushed to stable:
shotcut-21.02.15-1.fc32
v4l2loopback-0.12.5-2.fc32
v4l2loopback-kmod-0.12.5-3.fc32
xtables-addons-3.15-1.fc32
xtables-addons-kmod-3.15-1.fc32
Fedora 33
-------------
Pushed to testing:
mythtv-31.0-15.139.20210226gitb6ddf202a4.fc33
shotcut-21.02.27-1.fc33
vdr-markad-2.6.3-1.fc33
vdr-softhddevice-1.0.14-1.fc33
Pushed to stable:
shotcut-21.02.15-1.fc33
telegram-desktop-2.6.1-1.fc33
tg_owt-0-7.20210203gita198773.fc33
v4l2loopback-0.12.5-2.fc33
v4l2loopback-0.12.5-3.fc32
v4l2loopback-0.12.5-3.fc33
v4l2loopback-kmod-0.12.5-3.fc33
xtables-addons-3.15-1.fc33
xtables-addons-kmod-3.15-1.fc33
Fedora 34
-------------
Pushed to testing:
bino-1.6.7-8.fc34
gstreamer1-libav-1.18.2-4.fc34
libopenshot-0.2.5-8.fc34
mythtv-31.0-15.139.20210226gitb6ddf202a4.fc34
rpmfusion-free-obsolete-packages-34-1.fc34
shotcut-21.02.27-1.fc34
vdr-markad-2.6.3-1.fc34
vdr-softhddevice-1.0.14-1.fc34
Pushed to stable:
chromium-freeworld-88.0.4324.150-1.fc34
deadbeef-1.8.7-1.fc34
gr-dab-0.4-7.fc34
shotcut-21.02.15-1.fc34
telegram-desktop-2.6.1-1.fc34
tg_owt-0-7.20210203gita198773.fc34
v4l2loopback-0.12.5-2.fc34
v4l2loopback-0.12.5-3.fc34
v4l2loopback-kmod-0.12.5-3.fc34
xtables-addons-3.15-1.fc34
xtables-addons-kmod-3.15-1.fc34
EL 7
-------------
Pushed to testing:
Pushed to stable:
EL 8
-------------
Pushed to testing:
mythtv-31.0-15.139.20210226gitb6ddf202a4.el8
v4l2loopback-0.12.5-3.el8
Pushed to stable:
v4l2loopback-0.12.5-2.el8
v4l2loopback-kmod-0.12.5-3.el8
xtables-addons-3.15-1.el8
xtables-addons-kmod-3.15-1.el8
Section nonfree:
-------------
Fedora 32
-------------
Pushed to testing:
Pushed to stable:
Fedora 33
-------------
Pushed to testing:
Pushed to stable:
Fedora 34
-------------
Pushed to testing:
Pushed to stable:
EL 7
-------------
Pushed to testing:
Pushed to stable:
EL 8
-------------
Pushed to testing:
Pushed to stable:
nvidia-kmod-460.56-1.el8
nvidia-modprobe-460.56-1.el8
nvidia-persistenced-460.56-1.el8
nvidia-settings-460.56-1.el8
nvidia-xconfig-460.56-1.el8
xorg-x11-drv-nvidia-460.56-1.el8
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
3 years, 8 months
Re: [mythtv] Update to latest fixes/31.
by Andrew Bauer
The way the specfile pulls in the latest git commit as a patch against the release tarball is new to me. I interpretated that workflow to mean those before me thought it was important to document all the commits that were made. That's why I did not add the patch as a rfpkg source and instead included it with our git history.
However, if I do add the patch file as a rfpkg source per the original request, then why bother pulling down the changes as a separate patch at all? Rpmfusion github won't track the changes this way. Why not keep it simple and pull in one tarball that contains everything?
Just looking to understand.
Le dim. 28 févr. 2021 à 08:08, Gary Buhrmaster
<gary.buhrmaster(a)gmail.com> a écrit :
>
> On Sun, Feb 28, 2021 at 4:14 AM Sérgio Basto <sergio(a)serjux.com> wrote:
>
> > Maybe we should change the guidelines.
>
> I suspect your formal proposal will generate some
> interesting discussion.
I think it will be even more relevant to compress (gz, xz, etc) the
patches from upstream
Then you can just apply them compressed, the %patch macro will deal
with the compression while applying.
The reason why I think this is revelant for lookaside is that the
patches where already applied/reviewed upstream, So having "peer
reviewing", on the rpmfusion mailing list, for any eventual other
downstream patch will be hidden or much more difficult.
_______________________________________________
rpmfusion-developers mailing list -- rpmfusion-developers(a)lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-leave(a)lists.rpmfusion.org
3 years, 8 months
Re: [mythtv] Update to latest fixes/31.
by Sérgio Basto
On Fri, 2021-02-26 at 21:49 +0100, Andrew Bauer wrote:
> commit a754140ac1e6b1c4100a29b2bc7437a0339c49b0
> Author: Andrew Bauer <zonexpertconsulting(a)outlook.com>
> Date: Fri Feb 26 14:48:19 2021 -0600
>
> Update to latest fixes/31.
>
> mythtv.spec | 13 +-
> sources | 3 +-
> v31.0..b6ddf202a4.patch | 28604
IMHO, Please use `rfpkg new-sources v31.0..b6ddf202a4.patch` to avoid
at least send 28K bytes of text in email, btw sometimes it breaks my
gnome evolution
Thank you.
--
Sérgio M. B.
3 years, 8 months
Re: Could not auth with koji
by Andrew Bauer
Ah, right. That's the package you asked us to bless with karma earlier this week. Done, and fixed. Thank you.
Thanks,
Andy
________________________________
From: Sérgio Basto <sergio(a)serjux.com>
Sent: Friday, February 26, 2021 5:46 PM
To: RPM Fusion developers discussion list <rpmfusion-developers(a)lists.rpmfusion.org>
Subject: Re: Could not auth with koji
Please update yours rpkg [1]
for F32 I used [2] see what advisor fits to you .
Best regards,
[1]
https://bodhi.fedoraproject.org/updates/?packages=rpkg
[2]
dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-
cce45055c3
On Fri, 2021-02-26 at 21:34 +0000, Andrew Bauer wrote:
> I am unable to initiate a build with koji:
> > $ rfpkg build --nowait
> > You might want to run rpmfusion-packager-setup or rpmfusion-cert -n
> > to regenerate SSL certificate. For more info see
> > https://rpmfusion.org/Contributors#If_SSL_certificate_expired
> > Could not execute build: Could not auth with koji. Login failed:
> > 'ca'
>
> It is odd that the login is 'ca'. My FAS account name is kni and it
> is set correctly in .rpmfusion.user
>
> I've regenerated a new cert multiple times, using rpmfusion-cert and
> doing it the old way. Doesn't help.
>
> Here is the output of rpmfusion-cert:
> > $ rpmfusion-cert -v
> > Verifying Certificate
> > cert expires: 2021-08-25
> > We haven't crl.pem (https://admin.rpmfusion.org/accounts/ca/crl.pem
> > ) to check revocation list
>
> That url returns HTTP 404 by the way.
>
> It is difficult to tell if the error is on my side or with koji.
> Looking for some advice. Thanks.
> _______________________________________________
> rpmfusion-developers mailing list --
> rpmfusion-developers(a)lists.rpmfusion.org
> To unsubscribe send an email to
> rpmfusion-developers-leave(a)lists.rpmfusion.org
--
Sérgio M. B.
_______________________________________________
rpmfusion-developers mailing list -- rpmfusion-developers(a)lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-leave(a)lists.rpmfusion.org
3 years, 8 months
Re: [mythtv] Update to latest fixes/31.
by Andrew Bauer
Thanks for the feedback. I'll include the patch files as sources from now on. I did consider that before commiting. Ironically, I thought you would have wanted it the other way around. I guessed wrong.
Thanks,
Andy
________________________________
From: Sérgio Basto <sergio(a)serjux.com>
Sent: Friday, February 26, 2021 5:39 PM
To: rpmfusion-developers(a)lists.rpmfusion.org <rpmfusion-developers(a)lists.rpmfusion.org>; mythtv-owner(a)rpmfusion.org <mythtv-owner(a)rpmfusion.org>; rpmfusion-commits(a)lists.rpmfusion.org <rpmfusion-commits(a)lists.rpmfusion.org>
Subject: Re: [mythtv] Update to latest fixes/31.
On Fri, 2021-02-26 at 21:49 +0100, Andrew Bauer wrote:
> commit a754140ac1e6b1c4100a29b2bc7437a0339c49b0
> Author: Andrew Bauer <zonexpertconsulting(a)outlook.com>
> Date: Fri Feb 26 14:48:19 2021 -0600
>
> Update to latest fixes/31.
>
> mythtv.spec | 13 +-
> sources | 3 +-
> v31.0..b6ddf202a4.patch | 28604
IMHO, Please use `rfpkg new-sources v31.0..b6ddf202a4.patch` to avoid
at least send 28K bytes of text in email, btw sometimes it breaks my
gnome evolution
Thank you.
--
Sérgio M. B.
_______________________________________________
rpmfusion-developers mailing list -- rpmfusion-developers(a)lists.rpmfusion.org
To unsubscribe send an email to rpmfusion-developers-leave(a)lists.rpmfusion.org
3 years, 8 months
Could not auth with koji
by Andrew Bauer
I am unable to initiate a build with koji:
> $ rfpkg build --nowait
> You might want to run rpmfusion-packager-setup or rpmfusion-cert -n to regenerate SSL certificate. For more info see https://rpmfusion.org/Contributors#If_SSL_certificate_expired
> Could not execute build: Could not auth with koji. Login failed: 'ca'
It is odd that the login is 'ca'. My FAS account name is kni and it is set correctly in .rpmfusion.user
I've regenerated a new cert multiple times, using rpmfusion-cert and doing it the old way. Doesn't help.
Here is the output of rpmfusion-cert:
> $ rpmfusion-cert -v
> Verifying Certificate
> cert expires: 2021-08-25
> We haven't crl.pem (https://admin.rpmfusion.org/accounts/ca/crl.pem) to check revocation list
That url returns HTTP 404 by the way.
It is difficult to tell if the error is on my side or with koji. Looking for some advice. Thanks.
3 years, 8 months
RPM Fusion update report 2021-02-25
by noreply＠rpmfusion.org
RPM Fusion update report
------------------------
Section free:
-------------
Fedora 32
-------------
Pushed to testing:
shotcut-21.02.15-1.fc32
v4l2loopback-0.12.5-2.fc32
v4l2loopback-kmod-0.12.5-3.fc32
xtables-addons-3.15-1.fc32
xtables-addons-kmod-3.15-1.fc32
Pushed to stable:
ffmpegthumbs-20.12.2-1.fc32
kdenlive-20.12.2-1.fc32
Fedora 33
-------------
Pushed to testing:
shotcut-21.02.15-1.fc33
telegram-desktop-2.6.1-1.fc33
tg_owt-0-7.20210203gita198773.fc33
v4l2loopback-0.12.5-2.fc33
v4l2loopback-kmod-0.12.5-3.fc33
xtables-addons-3.15-1.fc33
xtables-addons-kmod-3.15-1.fc33
Pushed to stable:
ffmpeg-4.3.2-1.fc33
ffmpegthumbs-20.12.2-1.fc33
kdenlive-20.12.2-1.fc33
kodi-19.0-1.fc33
telegram-desktop-2.5.9-1.fc33
Fedora 34
-------------
Pushed to testing:
chromium-freeworld-88.0.4324.150-1.fc34
deadbeef-1.8.7-1.fc34
gr-dab-0.4-7.fc34
shotcut-21.02.15-1.fc34
telegram-desktop-2.6.1-1.fc34
tg_owt-0-7.20210203gita198773.fc34
v4l2loopback-0.12.5-2.fc34
v4l2loopback-kmod-0.12.5-3.fc34
xtables-addons-3.15-1.fc34
xtables-addons-kmod-3.15-1.fc34
Pushed to stable:
ffmpegthumbs-20.12.2-1.fc34
kdenlive-20.12.2-1.fc34
kodi-19.0-1.fc34
libheif-1.11.0-1.fc34
ppsspp-1.11-3.fc34
qmmp-plugins-freeworld-1.4.2-3.fc34
telegram-desktop-2.5.9-1.fc34
vcmi-0.99^20190113gitf06c8a8-4.fc34
EL 7
-------------
Pushed to testing:
Pushed to stable:
mythweb-31.0-3.el7
EL 8
-------------
Pushed to testing:
v4l2loopback-0.12.5-2.el8
v4l2loopback-kmod-0.12.5-3.el8
xtables-addons-3.15-1.el8
xtables-addons-kmod-3.15-1.el8
Pushed to stable:
mythweb-31.0-3.el8
Section nonfree:
-------------
Fedora 32
-------------
Pushed to testing:
nvidia-kmod-460.56-1.fc32
nvidia-modprobe-460.56-1.fc32
nvidia-persistenced-460.56-1.fc32
nvidia-settings-460.56-1.fc32
nvidia-xconfig-460.56-1.fc32
xorg-x11-drv-nvidia-460.56-1.fc32
Pushed to stable:
Fedora 33
-------------
Pushed to testing:
nvidia-kmod-460.56-1.fc33
nvidia-modprobe-460.56-1.fc33
nvidia-persistenced-460.56-1.fc33
nvidia-settings-460.56-1.fc33
nvidia-xconfig-460.56-1.fc33
xorg-x11-drv-nvidia-460.56-1.fc33
Pushed to stable:
Fedora 34
-------------
Pushed to testing:
nvidia-kmod-460.56-1.fc34
nvidia-modprobe-460.56-1.fc34
nvidia-persistenced-460.56-1.fc34
nvidia-settings-460.56-1.fc34
nvidia-xconfig-460.56-1.fc34
xorg-x11-drv-nvidia-460.56-1.fc34
Pushed to stable:
EL 7
-------------
Pushed to testing:
Pushed to stable:
EL 8
-------------
Pushed to testing:
nvidia-kmod-460.56-1.el8
nvidia-modprobe-460.56-1.el8
nvidia-persistenced-460.56-1.el8
nvidia-settings-460.56-1.el8
nvidia-xconfig-460.56-1.el8
xorg-x11-drv-nvidia-460.56-1.el8
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
3 years, 8 months
