On Wed, Dec 29, 2021 at 7:15 AM Stephen John Smoogen <smooge(a)gmail.com>
On Wed, 29 Dec 2021 at 06:29, Mattias Ellert <mattias.ellert(a)physics.uu.se>
> Two packages I built for EPEL 9 are now reported by koschei as having
> missing build dependencies.
> The EPEL 9 builds were built using the following build dependencies
> according to the root.log files:
Looks like this is a RHEL buildroot only package, thus can just be built
Although web-assets is built in RHEL9, they are only releasing
Thus, we are missing web-assets-devel and web-assets-httpd
Looks like this is a buildroot only package, thus can just be built in
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
> 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.