Bug 1940686 - glibc: Remove glibc-headers-x86 and glibc-headers-s390
Summary: glibc: Remove glibc-headers-x86 and glibc-headers-s390
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.0
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: pre-dev-freeze
: ---
Assignee: Florian Weimer
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-18 21:50 UTC by Florian Weimer
Modified: 2023-07-18 14:29 UTC (History)
7 users (show)

Fixed In Version: glibc-2.33-13.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:42:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Florian Weimer 2021-03-18 21:50:24 UTC
From email:

* Sergey Kolosov:

> The second test fails on /install /update /downgrade /remove phases,
> because it can't install(update/downgrade/remove) glibc-headers-s390-
> 0:2.33-5.el9.noarch because of conflicted files between glibc-headers-
> s390 and glibc-headers-x86 [2] I guess glibc-headers-s390 can't be
> installed in same time with glibc-headers-x86, so should I reach #osci
> to fix osci.brew-build.installability.functional test?

Hmm.  This came up recently here:

  <https://pagure.io/releng/issue/8337#comment-713404>

The side effects from those noarch packages are quite bad as well.
Someone needs to follow up with Kevin Fenzi and Lubomír Sedlář to check
if the infrastructure issues we were trying to work around have been
fixed, than we can revert this construct on the glibc side [in Fedora[.

In RHEL 9, we never saw these issues, so we can do this change downstream
after inheritance from Fedora 34 has stopped, in CentOS Stream 9.
This way, the second problem should go away in early April.


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