[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-11 Thread Launchpad Bug Tracker
** Branch linked: lp:debian/postgresql-common -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to start after install if invalid locale is set To manage notifications about this

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-11 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/saucy-proposed/postgresql-common -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to start after install if invalid locale is set To manage

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package postgresql-common - 145 --- postgresql-common (145) unstable; urgency=low [ Christoph Berg ] * pg_ctlcluster: Use install instead of File::Path to create unix_socket_directory. (Introduced in 141, Closes: #710093) [ Martin Pitt ] *

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-10 Thread Martin Pitt
Fixed in p-common packaging branch r1355. ** Changed in: postgresql-common (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-07 Thread Martin Pitt
In the discussion we found the following compromise: The postinst should ignore the locale from the environment (as sudo and ssh make that unreliable), and instead do the following fallback: * if /etc/default/locale defines a locale, use that * otherwise, if /etc/environment defines a locale,

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-04 Thread Robie Basak
picking some random locale How about C or C.UTF-8? These should be suitable non-random fallbacks, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to start after install

Re: [Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-04 Thread Martin Pitt
Robie Basak [2013-06-04 8:37 -]: picking some random locale How about C or C.UTF-8? These should be suitable non-random fallbacks, right? That's still not what you would expect on the server, which is usually to use the server's configured system locale. C or C.UTF-8 basically means

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-04 Thread Robie Basak
I've started a discussion thread at: https://lists.ubuntu.com/archives /ubuntu-devel/2013-June/037195.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to start after install

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-04 Thread Scott Moser
** Description changed: For more information on locale in the cloud-images, see bug 859814. If you install postgresql-9.1 with invalid LC_ALL, then postgres will not be running after install (which causes issues with things that depend on it). Try: $ LC_ALL=fr_FR.UTF-8 ssh

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-03 Thread Scott Moser
** Description changed: For more information on locale in the cloud-images, see bug 859814. If you install postgresql-9.1 with invalid LC_ALL, then postgres will not be running after install (which causes issues with things that depend on it). Try: $ LC_ALL=fr_FR.UTF-8 ssh

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-03 Thread Julian Edwards
I don't understand why this was marked invalid Martin. You're just confirming why the bug exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462 Title: fails to start after install if

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-06-03 Thread Martin Pitt
If anything, this is a bug in ssh for insisting to apply your host's locale to the remote shell. I have always considered that EBW, but I don't want to work around this in PostgreSQL by picking some random locale if the one that's actually set is invalid. -- You received this bug notification

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-03-25 Thread Martin Pitt
$ LC_ALL=fr_FR.UTF-8 ssh ubuntu@$HOSTNAME % locale locale: Cannot set LC_CTYPE to default locale: No such file or directory That means that fr_FR.UTF-8 doesn't actually exist on the target host. ** Changed in: postgresql-9.1 (Ubuntu) Status: Confirmed = Invalid -- You received this bug

[Bug 969462] Re: fails to start after install if invalid locale is set

2013-02-22 Thread Robinpeder
This also affects the result of the installation, even when using a valid locale. If postgresql is installed in a terminal with LC_ALL=C, it is not possible to create unicode databases: $ createdb -E UNICODE test createdb: database creation failed: ERROR: new encoding (UTF8) is incompatible

[Bug 969462] Re: fails to start after install if invalid locale is set

2012-06-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: postgresql-9.1 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969462

[Bug 969462] Re: fails to start after install if invalid locale is set

2012-03-30 Thread Scott Moser
** Description changed: For more information on locale in the cloud-images, see bug 859814. If you install postgresql-9.1 with invalid LC_ALL, then postgres will not be running after install (which causes issues with things that depend on it). - Try: $ LC_ALL=fr_FR.UTF-8 ssh