Bug 2034903 - No llvm-devel package for s390x in RHEL 9
Summary: No llvm-devel package for s390x in RHEL 9
Keywords:
Status: CLOSED DUPLICATE of bug 2035398
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: llvm
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tom Stellard
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-22 13:02 UTC by Mattias Ellert
Modified: 2022-01-05 05:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-05 05:30:14 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-106408 0 None None None 2021-12-22 13:03:14 UTC

Description Mattias Ellert 2021-12-22 13:02:38 UTC
Description of problem:

I tried to build a package I maintain for EPEL 9 and it failed to build on s390x because the llvm-devel package is missing. It built OK on the other architectures.

https://koji.fedoraproject.org/koji/taskinfo?taskID=80314576

Version-Release number of selected component (if applicable):

llvm-devel-13.0.0-1.el9.s390x (missing, the corresponding package exists for the other architectures).

How reproducible:

Always.

Steps to Reproduce:
1. Build a package that build-requires llvm-devel for EPEL 9
2. See it fail for s390x due to missing llvm-devel

Actual results:

Failed build

Expected results:

Successful build

Additional info:

Comment 1 Tom Stellard 2021-12-23 00:13:53 UTC
Is this bug for RHEL or CentOS Stream?

Comment 2 Mattias Ellert 2021-12-31 08:48:35 UTC
(In reply to Tom Stellard from comment #1)
> Is this bug for RHEL or CentOS Stream?

It is a bug for RHEL.

The missing build is available in the centos stream koji:
https://kojihub.stream.centos.org/koji/buildinfo?buildID=14668

Comment 3 Tom Stellard 2022-01-05 05:30:14 UTC

*** This bug has been marked as a duplicate of bug 2035398 ***


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