On 28/05/2025 22:19, Chris Adams wrote:
So it's been another month and this still isn't resolved. I know people on the Fedora side have been trying (don't want to complain about effort). But if Fedora can't reliably get timely updates to a package that has high security implications, it should NOT be enabled by default, or even shipped by Fedora at all.
I have a better option than completely removing it: adding this package to the RPM Fusion repository (rpmfusion-free) with a higher Release number (starting from 100, for example).
Users who have RPM Fusion enabled will get a well-maintained and updated version from this repository.
I think this is the best option at the moment. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
