On 02/26/2016 04:47 AM, Carlos O'Donell wrote:
With glibc-2.23.90-3.fc25 and glibc-2.23.1-5.fc24 we have now fixed
the issue in several important ways.
The `glibc-all-langpacks` continues to be the correct way to get all
locales, but now things are a bit smoother.
(1) Virtual provides to make upgrade smoother.
All glibc languages packs now provide `glibc-langpack`, that includes
the glibc-all-langpacks (all language support).
The core runtime depends on `glibc-langpack` and so when upgrading
on systems without dnf, yum, or langpack plugin support, plain rpm
dependency solving via suggests will install `glibc-all-langpack`
for you and provide all the existing locales you previously had.
This makes for a complete rpm solution with no other support
required.
This means that upgrading from a non-langpack supporting F23
to any future langpack supporting distribution will upgrade
you to the newest set of supported locales.
(2) Optimized "all languages" performance.
In addition the `glibc-all-langpack` is optimized to again use
the locale cache (locale-archive) to accelerate lookups for those
users who prefer to have all languages installed. Previously we
had `glibc-all-langpack` as a meta-package of all the other language
packs, but that is no longer the case.
(3) Provide glibc-minimal-langpack
We add a minimal language pack that provides no languages. This
allows you to install glibc-minimal-langpack and then uninstall
glibc-all-langpacks and operate entirely under C, POSIX, and C.UTF-8
locales.
This should resolve all problems that users have been seeing with
the upgrade.
Thank you for your patience. We really messed up here. In the future
we'll make sure we cover all the upgrade cases more carefully.
(4) Remove all languages to minimize installed size
You can still minimize your installed size, but it's slighltly
harder now. First you must install a valid language pack, and then
remove `glibc-all-langpacks` to reduce the size of installed languages.
Cheers,
Carlos.