On Sun, 2023-02-19 at 23:04 +, Leigh Scott via rpmfusion-developers
wrote:
> I don't think a +2 release upgrade is a valid test case, I believe
> f37
> is SHA256 signed.
>
All packages are signed except the packages that are in skip list of
mass rebuild for F37 [1]
On Sun, Feb 19, 2023 at 11:05 PM Leigh Scott via rpmfusion-developers
wrote:
>
> I don't think a +2 release upgrade is a valid test case, I believe f37
> is SHA256 signed.
>
Fedora officially supports a +2 release upgrade, and
for reasons[0][1], some people only upgrade to N when
N-2 is about to
I don't think a +2 release upgrade is a valid test case, I believe f37
is SHA256 signed.
On 19/02/2023 22:41, Sérgio Basto via rpmfusion-developers wrote:
Hi,
I spent this weekend understanding why when update my vm to F38
branched I got a lot of [1] the key ID d651ff2e is "our" key
Hi,
I spent this weekend understanding why when update my vm to F38
branched I got a lot of [1] the key ID d651ff2e is "our" key RPM-GPG-
KEY-rpmfusion-free-fedora-2020
For an introduction to this topic I recommend this 2 articles [2] .
In resume rpm sign with SHA1 aren't installed in F38
RPM Fusion update report
Section free:
-
Fedora 36
-
Pushed to testing:
chromium-freeworld-110.0.5481.100-1.fc36
jellyfin-10.8.9-2.fc36
telegram-desktop-4.6.3-1.fc36
Pushed to stable:
Fedora 37
-
Pushed to testing:
