>
> It was indeed locales. Do note, however, that the new locales
> require a new
> glibc, which may have been the real fix.
>
Nothing personal, but I'm really surprised to read about problems due to so
called "new" locales and glibc that were released several weeks ago.
It is mostly pointless to report bugs unless you have up to date state.
Nobody can garantee downward compatibility and if program was built under
newer glibc it may break with earlier versions. What d'you expect? Probably,
RPM build process could implicitly add dependency to glibc version that was
used (not less than). But it applies to any shared library as well.
-andrej
