"s390x": ["rust-std-static-wasm*"],

Those rust bits are noarch packages, but couldn't be installed on s390x because there was no lld to provide /usr/bin/wasm-ld -- but it's there as of LLVM 18! So we don't need that filter anymore on rawhide, nor f40 once the update lands.

It turned out that libgcc32 was not needed after all because the required contents has always been shipped as part of gcc.x86_64. We never created that subpackage.

We still need to filter out glibc32, although the DNF5 compatibility cleanup allowed us to make its presence in a compose less harmful (the current glibc32 has much fewer Provides:).

The config file lives here [1].

First step might be to check which packages still actually exist.

• glibc32 is retired [2] so it can be removed.
• libgcc32 was never created, a dist-git repo for it doesn't exist, so it can be removed.
• openh264 was added by me and is there for good reasons, cannot be removed.
• rust-std-static-wasm* can be removed as per one of the comments above.

That's everything for things not under Server.
Maybe we can summon someone from the Server Group SIG that might make us wiser?
And the PR should be opened only against the rawhide (main) branch, correct @kevin ?

[1] https://pagure.io/pungi-fedora/blob/main/f/fedora.conf.
[2] https://src.fedoraproject.org/rpms/glibc32/c/2eeeaa647f454f9e014d1a5accf1599d8c710795?branch=rawhide

@patrikp The glibc32 package lives on as a subpackage of the glibc package. I think it should still be filled. We currently do not need libgcc32. There was a close call recently, but we worked around it without introducing it. I suppose if we ever need it, we can request a filter once we add it.

So... on the server ones:

• This was setup 10 years ago when pungi was first setup. Probibly copied from mash.

• Some of those packages no longer exist

• None of those packages should be pulled into server composes.

I think personally that we can just drop them all.

So, we could:

• Just drop them all and then carefully check the server images from rawhide after we do to make sure none of them somehow got back in
• Test locally? This could be anoying to setup, but we could...

@kevin @patrikp Has some of this been merged?

We are shipping glibc32-2.41-3.fc42.x86_64, glibc32-2.40-24.fc41.x86_64, glibc32-2.39-37.fc40.x86_64, which isn't ideal and likely to cause some problems.

We have made no changes so far... the updates pungi config has [] in filter list... as it has since 2017. :)

We are filtering it for rawhide/branched tho. (as noted in the config at the start of this ticket).

Note that if those things are in the base / GA repo, we don't change that after release, so they will be there... if they are in updates we can filter them out.

Looks like it's updates only:

#  dnf info --disablerepo='*updates*' glibc32
Updating and loading repositories:
 Fedora 41 openh264 (From Cisco) - x86_ 100% |   4.1 KiB/s |   4.8 KiB |  00m01s
 Fedora 41 - x86_64                     100% |  10.8 MiB/s |  35.3 MiB |  00m03s
Repositories loaded.
No matching packages to list

# dnf info --disablerepo='*updates*' glibc32
Updating and loading repositories:
 Fedora 42 openh264 (From Cisco) - x86_ 100% |   3.3 KiB/s |   4.8 KiB |  00m01s
 Fedora 42 - x86_64                     100% |   7.7 MiB/s |  35.4 MiB |  00m05s
Repositories loaded.