When glibc is built, it inputs /etc/locales.build and compile. The problem is that when it finishes it always replaces /etc/locales.build with a file exists in the files folder of the ebuild. So emerging glibc twice generate different outputs. I know that one should be careful and not replace /etc files automatically... But in this case there is no reason to replace the file since it was used as input for the compilation. Reproducible: Always Steps to Reproduce: 1. Modify /etc/locales.build 2. Emerge glibc 3. Notice that /etc/locales.build reverted to its defaults. Actual Results: /etc/locales.build always reseted to defaults. Expected Results: If /etc/locales.build existed before ebuild and the userlocales USE was specified, please leave the etc/locales.build file as is (Don't replace with default). I think that if the file was missing it should not be created, so emerging twice will emerge all locales again.
You failed to include the output of emerge --info
Created attachment 58984 [details] emerge --info glibc Sorry, attached emerge --info glibc. But I've look at all the ebuilds, and they are all the same - Overwrite the locales.build with the one located in files.
*** This bug has been marked as a duplicate of 72596 ***
