Bug 2035398 - Please add llvm-devel to all arches in RHEL9
Summary: Please add llvm-devel to all arches in RHEL9
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-02-14
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: llvm
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Josh Boyer
QA Contact: Jesus Checa
URL:
Whiteboard:
: 2034903 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 21:44 UTC by Troy Dawson
Modified: 2022-05-17 13:19 UTC (History)
7 users (show)

Fixed In Version: llvm-devel-13.0.0-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 13:02:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-106543 0 None None None 2021-12-23 21:47:25 UTC
Red Hat Product Errata RHBA-2022:2442 0 None None None 2022-05-17 13:02:48 UTC

Description Troy Dawson 2021-12-23 21:44:09 UTC
I am building the KDE Plasma desktop in EPEL9.  A couple packages require llvm-devel to build.

Currently in RHEL9 llvm-devel is missing on s390x.  llvm is available on all the architectures, it's just the -devel package that is missing on s390x.

For me, it's only affecting qt-creator and umbrello, which are not critical KDE packages.  But I suspect that many other EPEL packages are going to hit the same problem.

I checked the latest production compose - CentOS-Stream-9-20211222.0
and latest development compose - CentOS-Stream-9-20211223.d.0

Comment 1 Tom Stellard 2021-12-24 03:16:14 UTC
The package exists in koji.  Is it possible the compose is filtering it out?

Comment 2 Troy Dawson 2021-12-24 06:19:42 UTC
I believe instead of being filtered out, it is not being pulled in.
If you look at pungi-centos/prepopulate.json it shows
        "llvm-devel.aarch64", 
        "llvm-devel.ppc64le", 
        "llvm-devel.i686", 
        "llvm-devel.x86_64", 

I don't know why we aren't prepopulating llvm-devel for s390x.
There might be a reason, or it might be an oversight.

Also, this isn't urgent.  I don't want to disturb anyones Holidays or shutdowns.  I just wanted to get this bug created before I took my holidays.  We can talk about it next year.  Happy Holidays.

Comment 3 Josh Boyer 2022-01-04 12:45:39 UTC
(In reply to Troy Dawson from comment #2)
> I believe instead of being filtered out, it is not being pulled in.
> If you look at pungi-centos/prepopulate.json it shows
>         "llvm-devel.aarch64", 
>         "llvm-devel.ppc64le", 
>         "llvm-devel.i686", 
>         "llvm-devel.x86_64", 
> 
> I don't know why we aren't prepopulating llvm-devel for s390x.
> There might be a reason, or it might be an oversight.

prepopulate.json was generated from a point-in-time compose to set a baseline post-RHEL 9 Beta.  At that time, llvm-devel.s390x wasn't included.

It's a case of "not being pulled in", essentially.  The only thing that pulls it into the compose on the other arches is lld-test.  lld isn't built for s390x at all, so llvm-devel isn't pulled in.

Adding llvm-devel to s390x is simple to do, after the bug is approved.

Comment 4 Tom Stellard 2022-01-05 05:30:14 UTC
*** Bug 2034903 has been marked as a duplicate of this bug. ***

Comment 5 Tom Stellard 2022-01-05 05:32:22 UTC
@jwboyer Should I assign this to you?

Comment 7 Josh Boyer 2022-01-05 13:34:02 UTC
Sure

Comment 15 Troy Dawson 2022-01-12 14:35:05 UTC
I just want to chime in and say I'm now seeing llvm-devel on all arches on my EPEL9 builds.
Thank You.

Comment 17 errata-xmlrpc 2022-05-17 13:02:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: llvm-toolset), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2442


Note You need to log in before you can comment on or make changes to this bug.