https://bugzilla.redhat.com/show_bug.cgi?id=2376217
--- Comment #19 from Mikel Olasagasti Uranga <[email protected]> --- > The upstream openbao requires a newer version of Go than is currently shipped > in EPEL and I believe Fedora although maybe not the latest version of Fedora. > Every release they update to the latest one. The build step compiles the > required version of go using the OS version. Go keeps making it harder to > continue to use an older version by continually updating the version required > in go.mod so I don't see a way around this. I could have it check to see if > the current version is new enough and skip the build. (We can't include a go > binary instead because that only works on one architecture.) Packages for Fedora and EPEL need to be built with whatever Go version is being shipped at that moment. If a package requires a newer Go version, then it's up to the packager to workaround it (reverting a change, disabling features, working with Golang mantainers, not updating the package, ...), but using a custom Go is not an acceptable method. If you think openbao can't work this way, then the package may not be acceptable for Fedora/EPEL and COPR would be a better place for it. -- 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=2376217 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202376217%23c19 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
