This is a tracking bug for Change: Remove glibc-all-langpacks from buildroot
For more details, see: https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_buildroot
glibc-minimal-langpack is added to @Buildsystem group and installed into the minimal buildroot instead of glibc-all-langpacks. Packages which need more locales than plain C/C.UTF-8/POSIX need to pull them in through BuildRequires.
Note this will, in addition to koji groups, require changes in the platform:f30 module definition.
According to the Fedora 30 schedule, today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to MODIFIED. If you know your change will not be ready for Fedora 30, you can set the version to rawhide and notify firstname.lastname@example.org. For more information about this milestone, see the Changes Policy.
The comps PR was merged, and srpm-build group in koji was also updated. So I *think* this is all implemented. Nevertheless, I don't have good visibility in the full releng setup, so I can't be sure. I'll set status to ON_QA.
Building Perl packages in Koji does not produce the warning about an unknown locale anymore. build.log also displays that mock invokes rpmbuild with C.UTF-8 locale now. root.log does not manifest glibc-all-langpacks anymore. From an observer point of view this seems to be correctly implemented in Koji now. Example <https://koji.fedoraproject.org/koji/buildinfo?buildID=1214917>.
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This was implemented as planned.