https://bugzilla.redhat.com/show_bug.cgi?id=2173751 --- Comment #19 from Scott Williams <vwfoxguru@xxxxxxxxx> --- "We don't necessarily need to wait for upstream to merge that and the pcre2 change. We can include them in the package as patch files, with comments linking to their upstream PRs. In fact I recommend doing that." The m4 one should be trivially easy. The pcre2 PR was submitted against HEAD, so I might create a branch against current release tag and see if I can cherry-pick the commits into it to make the patch. It's been over a decade since I've rolled a significant custom .patch and last time I used regular old diff, so this'll give me a chance to try out using `git format-patch`. Tim, how about I create the patches and you can plug them into the spec with the other change? I'll submit the patch files in a PR against your repo. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2173751 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
