When i add

export LC_ALL=*en_US.UTF-8*

in /var/lib/mock/centos-5-x86_64/root/etc/bashrc after make
repo-chroot-init and before make sipxconfig.rpm, it works fine?

Should I add it directly to the file in our build script right after
making repo-chroot-init?

Or is there a way to pass this to mock during making sipxconfig.rpm?


On Wed, Apr 6, 2011 at 3:24 PM, barisyanar <[email protected]> wrote:

> .......
>
> /builddir/build/BUILD/sipxconfig-4.4.0/web/test/org/sipfoundry/sipxconfig/site/dialplan/DialPlanEditTestUi.java:58:
> unmappable character for encoding ASCII
>     private final String AUTO_ATTENDANT = "Robot operat??r";
>                                                        ^
> /builddir/build/BUILD/sipxconfig-4.4.0/web/test/org/sipfoundry/sipxconfig/site/dialplan/DialPlanEditTestUi.java:58:
> unmappable character for encoding ASCII
>     private final String AUTO_ATTENDANT = "Robot operat??r";
>                                                         ^
> 52 errors
> BUILD FAILED
> /builddir/build/BUILD/sipxconfig-4.4.0/ant-targets.xml:190: Compile failed;
> see the compiler error output for details.
> Total time: 7 seconds
> make[2]: *** [all-ant] Error 1
> make[2]: Leaving directory `/builddir/build/BUILD/sipxconfig-4.4.0/web'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/builddir/build/BUILD/sipxconfig-4.4.0'
> make: *** [all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.93031 (%build)
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.93031 (%build)
> Child returncode was: 1
> EXCEPTION: Command failed. See logs for output.
>  # ['bash', '--login', '-c', 'rpmbuild -bb --target x86_64 --nodeps
> builddir/build/SPECS/sipxconfig.spec']
> Traceback (most recent call last):
>   File "/usr/lib/python2.4/site-packages/mock/trace_decorator.py", line 70,
> in trace
>     result = func(*args, **kw)
>   File "/usr/lib/python2.4/site-packages/mock/util.py", line 347, in do
>     raise mock.exception.Error, ("Command failed. See logs for output.\n #
> %s" % (command,), child.returncode)
> Error: Command failed. See logs for output.
>  # ['bash', '--login', '-c', 'rpmbuild -bb --target x86_64 --nodeps
> builddir/build/SPECS/sipxconfig.spec']
> LEAVE do --> EXCEPTION RAISED
>
> On Wed, Apr 6, 2011 at 3:22 PM, Douglas Hubler <[email protected]> wrote:
>
>> I do not see the error message you are getting?
>>
>> On Wed, Apr 6, 2011 at 4:07 AM, barisyanar <[email protected]> wrote:
>> > I am getting unmappable character for encoding ASCII error during rpm
>> > generation on mock. I think I should set LANG as en_us.utf-8 for Turkish
>> > characters.
>> > How can I do that?
>> > Mock Version: 1.0.12
>> > ENTER do(['bash', '--login', '-c', 'rpmbuild -bs --target x86_64
>> --nodeps
>> > builddir/build/SPECS/sipxconfig.spec'], False,
>> > '/var/lib/mock/centos-5-x86_64/root/', None, 0, True, 0, 500, 104, None,
>> > logger=<mock.trace_decorator.getLog object at 0x2b46de81ad90>)
>> > Executing command: ['bash', '--login', '-c', 'rpmbuild -bs --target
>> x86_64
>> > --nodeps builddir/build/SPECS/sipxconfig.spec']
>> > Building target platforms: x86_64
>> > Building for target x86_64
>> > Wrote: /builddir/build/SRPMS/sipxconfig-4.4.0-274.gcff06.src.rpm
>> > Child returncode was: 0
>> > LEAVE do -->
>> > ENTER do(['bash', '--login', '-c', 'rpmbuild -bb --target x86_64
>> --nodeps
>> > builddir/build/SPECS/sipxconfig.spec'], False,
>> > '/var/lib/mock/centos-5-x86_64/root/', None, 0, True, 0, 500, 104, None,
>> > logger=<mock.trace_decorator.getLog object at 0x2b46de81ad90>)
>> > Executing command: ['bash', '--login', '-c', 'rpmbuild -bb --target
>> x86_64
>> > --nodeps builddir/build/SPECS/sipxconfig.spec']
>> > Building target platforms: x86_64
>> > Building for target x86_64
>> > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.89551
>> > + umask 022
>> > + cd /builddir/build/BUILD
>> > + LANG=C
>> > + export LANG
>> >
>> >
>> > _______________________________________________
>> > sipx-dev mailing list
>> > [email protected]
>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> >
>> _______________________________________________
>> sipx-dev mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>>
>
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to