Hi,
pgAdmin build failed because of the following error related to locale:
--
Traceback (most recent call last):
File
"/Library/Frameworks/Python.framework/Versions/3.2/bin/sphinx-build", line
9, in <module>
load_entry_point('Sphinx==1.1.3', 'console_scripts', 'sphinx-build')()
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/Sphinx-1.1.3-py3.2.egg/sphinx/__init__.py",
line 47, in main
from sphinx import cmdline
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/Sphinx-1.1.3-py3.2.egg/sphinx/cmdline.py",
line 18, in <module>
from docutils.utils import SystemMessage
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/docutils-0.9-py3.2.egg/docutils/utils/__init__.py",
line 19, in <module>
from docutils.io import FileOutput
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/docutils-0.9-py3.2.egg/docutils/io.py",
line 18, in <module>
from docutils.error_reporting import locale_encoding, ErrorString,
ErrorOutput
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/docutils-0.9-py3.2.egg/docutils/error_reporting.py",
line 47, in <module>
locale_encoding = locale.getlocale()[1] or locale.getdefaultlocale()[1]
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/locale.py",
line 522, in getlocale
return _parse_localename(localename)
File
"/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/locale.py",
line 435, in _parse_localename
raise ValueError('unknown locale: %s' % localename)
*ValueError: unknown locale: UTF-8*
make[1]: *** [htmlhelp] Error 1
make: *** [doc] Error 2
--
I set the following two variables in the environment to get through the
build.
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
On Tue, Dec 4, 2012 at 9:07 AM, Sandeep Thakkar <
sandeep.thak...@enterprisedb.com> wrote:
> Sure. I'll update the pgAdmin for PostgreSQL 9.2.
>
> Thanks.
>
>
> On Mon, Dec 3, 2012 at 10:43 PM, Dave Page <dp...@pgadmin.org> wrote:
>
>> I've uploaded the pgAdmin 1.16.1 source tarball to
>> http://www.postgresql.org/ftp/pgadmin3/release/v1.16.1/src/
>>
>> Sandeep; please ensure this is used when you build the PostgreSQL 9.2
>> installers tomorrow (don't update the older branches though).
>>
>> Thanks.
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
>
> --
> Sandeep Thakkar
> Senior Software Engineer
> EnterpriseDB Corporation
> The Enterprise Postgres Company
> Phone: +91.20.30589514
>
> Website: www.enterprisedb.com
> EnterpriseDB Blog: http://blogs.enterprisedb.com/
> Follow us on Twitter: http://www.twitter.com/enterprisedb
>
> This e-mail message (and any attachment) is intended for the use of the
> individual or entity to whom it is addressed. This message contains
> information from EnterpriseDB Corporation that may be privileged,
> confidential, or exempt from disclosure under applicable law. If you are
> not the intended recipient or authorized to receive this for the intended
> recipient, any use, dissemination, distribution, retention, archiving, or
> copying of this communication is strictly prohibited. If you have received
> this e-mail in error, please notify the sender immediately by reply e-mail
> and delete this message.
>
--
Sandeep Thakkar
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise Postgres Company
Phone: +91.20.30589514
Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb
This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
