This bug is mine :-(

I added support of TERM in
http://jppy.alioth.debian.org/changeset/bae16bd60932db72de23eb09fc8691f8e41dce6a
But the build fails if TERM is not defined, as is the case in an
automatic build system.

I just corrected the bug upstream in
http://jppy.alioth.debian.org/changeset/67b659e0ca5b61b0adb46d03c74626253e933767

Bye

2009/11/4 Nicholas Piper <n...@nickpiper.co.uk>:
> ----- Forwarded message from Bastian Blank <wa...@debian.org> -----
>
> From: Bastian Blank <wa...@debian.org>
> Subject: Bug#554088: jppy - FTBFS: KeyError: 'TERM'
> To: sub...@bugs.debian.org
> X-Spam-Level:
> Resent-To: debian-bugs-d...@lists.debian.org
> X-Debian-PR-Message: report 554088
> X-Debian-PR-Package: src:jppy
> X-Debian-PR-Keywords:
> X-Debian-PR-Source: jppy
> Date: Mon, 2 Nov 2009 22:41:43 +0100
> X-Debian: PTS
> X-Debian-Package: jppy
> X-PTS-Package: jppy
> X-PTS-Keyword: bts
> X-originally-to: deb...@nickpiper.co.uk
>
> Source: jppy
> Version: 0.0.53-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
>> sbuild (Debian sbuild) 0.58.2 (31 Jul 2009) on debian-31.osdl.marist.edu
> [...]
>> scons: Reading SConscript files ...
>> Please remember that SCons does NOT automatically use your shell
>> environment variables. This script uses PKG_CONFIG_PATH explicitly.
>> KeyError: 'TERM':
>>   File "/build/buildd-jppy_0.0.53-1-s390-4AhqYb/jppy-0.0.53/SConstruct", 
>> line 63:
>>     'TERM' : os.environ['TERM'],}
>>   File "/usr/lib/python2.5/UserDict.py", line 22:
>>     raise KeyError(key)
>> make: *** [build-python2.5-stamp] Error 2
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
>
>
>
>
> ----- End forwarded message -----
>
> _______________________________________________
> Jppy-devel mailing list
> jppy-de...@zanu.org.uk
> http://mail.zanu.org.uk/mailman/listinfo/jppy-devel
>



-- 
 Dr. Ludovic Rousseau



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to