There doesn't seem to be any need to install with the C locale; en_US.UTF-8 works just as well. As does installing the language pack(s) to match the session's locale settings. The real problem is that we have no hook for doing either before apt installs our dependencies: it installs the dependencies first, and only then do we get a say.
As Julian pointed out on the bug that was merged into this one, it's arguably a bug in the postgres packaging for neither failing nor falling back on unicode when the system does not support the session's locale, or openssh for keeping a locally unsupported locale in the session. Maybe sudo is to blame even for neglicence in sanitising the environment. Addressing the problem there would have wider consequences. Personally I think we should create our own postgres cluster during installation, with settings we dictate, instead of relying on the default one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382774 Title: MAAS can't connect to postgresql To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
