On Fri, Feb 17, 2023 at 3:28 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
On Fri, Feb 17, 2023 at 9:16 AM Kamil Paral <kparal@xxxxxxxxxx> wrote:
>
> I've spent several days working on this problem and I believe it's time to raise it here, because it can possibly be a disaster for F38 desktops. Please read these reports:
>
> 1. https://ask.fedoraproject.org/t/popular-third-party-rpms-fail-to-install-update-remove-due-to-security-policies-verification/31594
> 2. https://bugzilla.redhat.com/show_bug.cgi?id=2170878
> 3. https://bugzilla.redhat.com/show_bug.cgi?id=2170839
>
> I'm happy to provide further details or debug some additional use cases, but overall this will need developers attention at this point. Even though it only concerns third-party software, and we don't block on third-party software, it has such consequences for our OS and is so likely to happen that I don't think we want to release F38 in this exact state.
Please file a ticket with FESCo to request blocker status. Here's an
example of one that I did last cycle:
https://pagure.io/fesco/issue/2873
I created a FESCo ticket here:
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/desktop@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
