On 1/17/22 16:42, epel-devel@lists.fedoraproject.org wrote:
I'm trying to look into a package test failure on RHEL8 s390x. However,
it seems that my free developer subscription does not give me access to
this platform:
[linux1@rhel8 ~]$ sudo subscription-manager attach
Installed Product
Last week, I retired the `nodejs` package from EPEL 7 because it was
(I believed) stuck on Node.js 6.x due to insufficient dependency
support. Apparently, this broke a few things like uglify-js[1], so I
spent today looking into whether I could get Node.js 16.x to work (the
latest LTS release) and
The following Fedora EPEL 7 Security updates need testing:
Age URL
7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-568a1eb67d
btrbk-0.31.3-1.el7
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2d515d4692
binaryen-104-1.el7
4
I'm trying to look into a package test failure on RHEL8 s390x. However,
it seems that my free developer subscription does not give me access to
this platform:
[linux1@rhel8 ~]$ sudo subscription-manager attach
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for IBM z
On Sat, Jan 15, 2022 at 12:33 PM Orion Poplawski wrote:
>
> I've done some poking, and this is what I've come up with for *new*
> missing -devel packages in CS9 with their approximate number of users in
> rawhide:
>
> 389-ds-base-devel 2
> accel-config-devel 0
> anthy-unicode-devel 3
>
Hello all!
Red Hat subscribed builders (for EPEL 8) have been deployed to production.
So any EPEL 8 build in Fedora Copr is now done against RHEL 8 + EPEL 8. As
always, please report back any issues.
There's though some problem related to the s390x native builders. Please
stay tuned on that
On Fri, 14 Jan 2022 07:02:23 -0500
Josh Boyer wrote:
> 2) Moving content to CRB in RHEL is not a silver bullet solution in
> many scenarios. If it's strictly for build dependencies, CRB works
> well. If an EPEL package has a runtime requires on CRB content, that
> is less desirable. RHEL
