On Wed, Dec 29, 2021 at 7:15 AM Stephen John Smoogen <[email protected]> wrote:
> > > On Wed, 29 Dec 2021 at 06:29, Mattias Ellert <[email protected]> > wrote: > >> Hi! >> >> Two packages I built for EPEL 9 are now reported by koschei as having >> missing build dependencies. >> >> https://koschei.fedoraproject.org/package/davix?collection=epel9 >> >> https://koschei.fedoraproject.org/package/uglify-js?collection=epel9 >> >> The EPEL 9 builds were built using the following build dependencies >> according to the root.log files: >> >> rapidjson-devel-1.1.0-19.el9 >> > Looks like this is a RHEL buildroot only package, thus can just be built in EPEL9. https://docs.fedoraproject.org/en-US/epel/epel-package-request/ >> web-assets-devel-5-15.el9 >> > Although web-assets is built in RHEL9, they are only releasing web-assets-filesystem Thus, we are missing web-assets-devel and web-assets-httpd https://docs.fedoraproject.org/en-US/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package._how_do_i_build_a_package_that_needs_that_missing__devel_package > nodejs-packaging-2021.01-5.el9 >> > Looks like this is a buildroot only package, thus can just be built in EPEL9. Definitely something we need. I believe I can take that. >> These can no longer be found in the koji buildroot. There are no >> expired buildroot overrides for these builds, which could explain the >> disappearance. >> >> I can't find these builds in EPEL's koji, so I guess they where >> provided by RHEL, but now are no longer? Did RHEL dop these? >> >> > OK there was a period in the EPEL-9 startup where the buildroot was > pointing to a copy of the CentOS Stream-9 koji build root. This was done to > help kickstart things, but it had the issue that packages that RHEL is not > going to ship to customers were available also. About 2-3 weeks ago, the > EPEL steering committee decided to move the buildroot to the properly > shipped chain of packages in CentOS Stream versus the buildroot. This > removed a bunch of packages that were 'available' but not going to be > shipped. These packages will need to be made into epel-only packages or > some other solution. I am fuzzy on this myself as I am from a different > philosophy school of building and shipping packages. >
_______________________________________________ epel-devel 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 on the list, report it: https://pagure.io/fedora-infrastructure
