Hello, On September 6th, the platform:f28 module was retired [1] because the issue in MBS described in #1243 [2] was fixed, but due to a miscommunication, MBS was not updated in Fedora's infrastructure to include the fix. Because of this, any modules that buildrequire a module that was built on a retired platform stream but can be installed on any Fedora version, can no longer build. In practice, this occurs with modules that buildrequire the "javapackages-tools" module. To see more of the backstory, you can read #1243 [2].
The purpose of this email is to request a freeze exception to upgrade MBS from v2.25.0 to v2.27.0.
If this request is denied, I'd like permission to temporarily unretire the platform:f28 stream in the MBS database as an alternative solution. However, this alternative solution will cause any modulemd file that buildrequires all platform streams to trigger a Fedora 28 build which will fail.
1 - https://pagure.io/fedora-infrastructure/issue/7862 2 - https://pagure.io/fm-orchestrator/issue/1243
Thank you for your help. Sincerely, Matt
On 9/9/19 8:25 AM, Matt Prahl wrote:
Hello, On September 6th, the platform:f28 module was retired [1] because the issue in MBS described in #1243 [2] was fixed, but due to a miscommunication, MBS was not updated in Fedora's infrastructure to include the fix. Because of this, any modules that buildrequire a module that was built on a retired platform stream but can be installed on any Fedora version, can no longer build. In practice, this occurs with modules that buildrequire the "javapackages-tools" module. To see more of the backstory, you can read #1243 [2].
The purpose of this email is to request a freeze exception to upgrade MBS from v2.25.0 to v2.27.0.
+1.
This is just updating the rpm on frontends/backends? Or is there more to it?
If this request is denied, I'd like permission to temporarily unretire the platform:f28 stream in the MBS database as an alternative solution. However, this alternative solution will cause any modulemd file that buildrequires all platform streams to trigger a Fedora 28 build which will fail.
I'd really rather not do that...
kevin
Thank you Kevin!
Yes, you are correct. This is just running an Ansible playbook which updates the RPMs on the two frontend servers and the one backend server.
infrastructure@lists.fedoraproject.org