#7576 Block glibc32, libgcc32 (sub)packages from all composes
Closed: Fixed Opened by fweimer.

I'm looking into a new workaround for https://pagure.io/koji/issue/273.

Is it possible to block a subpackage from appearing in all composes? If it is, we could perhaps build glibc32.x86_64 from the glibc source package (and the required libgcc32.x86_64 from the gcc source package).


@fweimer Sorry but we cannot block subpackages in koji.

Closing the ticket as we cannot do anything right now.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

I'm not asking about Koji specifically. It's okay if the package goes into the buildroot. Doesn't pungi have this functionality?

This should be doable by adding the package to filter_packages in fedora.conf.

This should do the trick to remove the package from all variants and all architectures:

filter_packages = [
    ("^.*$", {"*": ["glibc32"]),
]

Metadata Update from @fweimer:
- Issue status updated to: Open (was: Closed)

Would you be willing to make this change?

We would likely have to make a similar change for libgcc32 (which we will need to build glibc32 as a subpackage).

Oh, by the way: I will file a (non-system-wide) Change for Fedora 29 for some changes to the glibc32 package (which have to happen independently of the outcome of this discussion).

Relevant Fedora 29 Change: https://fedoraproject.org/wiki/Changes/glibc32_Build_Adjustments

I believe you can start filtering glibc32/libgcc32 packages without further coordination with us: glibc32 should not be present in composes due to Koji tags, and libgcc32 does not exist yet.

@fweimer Yes, once the change request is approved we will add the necessary changes to our configs.

Fesco has approved the change: https://pagure.io/fesco/issue/1923

And the needed config is in place. ;)

Let us know if you see anything still needing to be done here.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @fweimer:
- Issue status updated to: Open (was: Closed)

Metadata Update from @fweimer:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @fweimer:
- Issue status updated to: Open (was: Closed)

Metadata Update from @fweimer:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata