Right, the : path thing was a separate bug that I have a solution for in hand, but it doesn't solve the second problem, which is that it's never even trying to load coreutils.mo.
If you want to see something amusing, try doing "export LOCPATH=/", and then the : problem that you see there will go away. It treats the default path only like a path where LOCPATH is defined. Otherwise, it sees it as a single block. glibc isn't internally consistant in these cases, which I need to clean up and send upstream. In practice what we're doing is saying "When the user asks for his/her files in /usr/share/locale, also look in /usr/share/locale-langpack". But even with all our patches removed, it's still not searching for the coreutils.mo file. That was the build that I ran overnight last night. More hacking to come. Tks, Jeff Bailey -- locales problems with edgy libc6 https://launchpad.net/bugs/49113 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
