https://bugzilla.redhat.com/show_bug.cgi?id=1535549 --- Comment #32 from David Auer <dreua@xxxxxxxxx> --- On the linking issue: Thanks Paul, I didn't find this yesterday. I absolutely agree that this is the way to go. (i.e. apply this patch downstream until it is released and disregard my linker workaround) On the old release issue: Would we violate hard rules by packaging Version 2.5.9 which is declared as pre-release / beta on the Github page [1] ? I generally agree that we should ship stable releases but this case may be worth an exception. I asked upstream [2] for clarification because they seem to suggest that 2.5.9 is a release and additionally some distributions [3] are shipping it. 1: https://github.com/mupen64plus/mupen64plus-core/releases 2: https://github.com/mupen64plus/mupen64plus-core/issues/353#issuecomment-633222060 3: https://repology.org/project/mupen64plus/versions -- 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 _______________________________________________ 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
