On Tue, Mar 19, 2024 at 04:36:03PM +0100, Florian Weimer wrote: > * Kevin Fenzi: > > > So, seems glibc32 was updated to update license headers? > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd577e1535 > > > > So, it's in f40-updates-testing now. > > > > It's not in rawhide or f40 composes because pungi filters it out, but > > it's currently not filtered in updates-testing. I can fix that, but... > > isn't this package just going to be retired/blocked now? > > Uh-oh? Does this mean that glibc32 (the binary package) will land in > updates-testing as well, each time we have glibc in gating? Yep. So I will filter it there too... > I planned to retire glibc32 after my vacation, in early April, but I can > retire it now if that's better. Naw, I can add it to filter out and then it shouldn't matter. However, our filter config is... quite possibly out of date. :) Currently it is: filter_packages = [ ("^.*$", { "*": ["glibc32", "libgcc32"], "s390x": ["rust-std-static-wasm*"], }), ('(Server)$', { '*': [ 'kernel*debug*', 'kernel-kdump*', 'kernel-tools*', 'syslog-ng*', 'astronomy-bookmarks', 'generic*', 'GConf2-dbus*', 'bluez-gnome', 'java-11-openjdk', 'community-mysql*', 'jruby*', 'gimp-help-*', ] }), ] Does libgcc32 exist anymore? Do we need that exclude on wasm on s390x? Those sever ones look... weird. Anyhow, I have filed: https://pagure.io/releng/issue/12023 on this, so if you want something to stay in there that's listed above, please note it there. ;) kevin
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
