[EPEL-devel] Re: Modules for EPEL9
On Thu, Mar 24, 2022 at 07:09:33PM -0400, Neal Gompa wrote: > On Thu, Mar 24, 2022 at 6:38 PM Kevin Fenzi wrote: > > > > On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote: > > > It was talked about December 2021, and pushed off to the new year. > > > https://pagure.io/epel/issue/135 > > > It's the new year, and you are the first this year to ask for it. So, > > > time > > > to get it back in the discussions. > > > Could you please put what modules you want to build in that ticket, so we > > > can help prioritize it. > > > > Personally, I'd be happy just not doing modules at all for epel9 given > > the limitations we have (cannot build any module that requires rhel > > modules). I'd prefer we have folks just use compatiblity packages > > instead. > > > > What's stopping us from being able to depend on RHEL modules? Koji now > supports enabling module streams on a per tag basis, so it *should* be > possible now. As far as I know, MBS has no way of handling this case. It only knows about modules it itself has built, it doesn't have a way to tag in an externally built RHEL module to be used as a BuildRequires for another module. https://pagure.io/fm-orchestrator/issue/1653 kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Modules for EPEL9
On Thu, Mar 24, 2022 at 6:38 PM Kevin Fenzi wrote: > > On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote: > > It was talked about December 2021, and pushed off to the new year. > > https://pagure.io/epel/issue/135 > > It's the new year, and you are the first this year to ask for it. So, time > > to get it back in the discussions. > > Could you please put what modules you want to build in that ticket, so we > > can help prioritize it. > > Personally, I'd be happy just not doing modules at all for epel9 given > the limitations we have (cannot build any module that requires rhel > modules). I'd prefer we have folks just use compatiblity packages > instead. > What's stopping us from being able to depend on RHEL modules? Koji now supports enabling module streams on a per tag basis, so it *should* be possible now. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Modules for EPEL9
On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote: > It was talked about December 2021, and pushed off to the new year. > https://pagure.io/epel/issue/135 > It's the new year, and you are the first this year to ask for it. So, time > to get it back in the discussions. > Could you please put what modules you want to build in that ticket, so we > can help prioritize it. Personally, I'd be happy just not doing modules at all for epel9 given the limitations we have (cannot build any module that requires rhel modules). I'd prefer we have folks just use compatiblity packages instead. kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Modules for EPEL9
It was talked about December 2021, and pushed off to the new year. https://pagure.io/epel/issue/135 It's the new year, and you are the first this year to ask for it. So, time to get it back in the discussions. Could you please put what modules you want to build in that ticket, so we can help prioritize it. On Wed, Mar 23, 2022 at 5:24 PM Orion Poplawski wrote: > Is there a timeline for supporting building modules for EPEL9? At the > moment I get: > > Could not execute module_build: The build failed with: > None of the base module (platform or bootstrap) streams in the > buildrequires section could be found > > -- > Orion Poplawski > he/him/his - surely the least important thing about me > IT Systems Manager 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > 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/epel-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
