See https://bugzilla.redhat.com/show_bug.cgi?id=1759405
This is possible fix
<img alt="remove-crypto-utils.patch" src="/fedora-comps/issue/raw/files/62b4da297b40f23d86cc9abcb6be94c62d7fc665673a9e7bf15fabeefe2ddbcf-remove-crypto-utils.patch" />
ionly for f31 and master
F31 is in final freeze, so we need a approved freeze break to make changes there.
So, can you ask for a freeze break, or split this out into two PR's and we can merge the master/rawhide one now and the f31 one after release?
See https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process and https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist
you may need a bugzilla bug, which you could just file against comps component...
F31 is in final freeze, so we need a approved freeze break to make changes there. So, can you ask for a freeze break, or split this out into two PR's and we can merge the master/rawhide one now and the f31 one after release?
Not serious enough for requesting a freeze break, splitting into two is preferable.
See https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process and https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist you may need a bugzilla bug, which you could just file against comps component...
Do mean a regular bugzilla bug against comps instead of a https://pagure.io/fedora-comps/issue as this one is?
If you want a freeze break you have to use a bugzilla bug because thats how it tracks them. ;)
If you don't, no need to file a new bug at all.
Thanks for the clarification. I'll split https://pagure.io/fedora-comps/pull-request/420 into two pull requests.
For Rawhide: https://pagure.io/fork/emaldonado/fedora-comps/diff/master..crypto-utils-removed-f32
Two pull requests for Rawhide and F31: https://pagure.io/fedora-comps/pull-request/422 https://pagure.io/fedora-comps/pull-request/423
See https://pagure.io/fedora-comps/issue/425
Login to comment on this ticket.