Source: pygame
Version: 1.9.1release+dfsg-5
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> dh clean --with python2
>    dh_testdir
>    dh_auto_clean
> 
> 
> WARNING, No "Setup" File Exists, Running "config.py"
> Using UNIX configuration...
> 
> 
> Hunting dependencies...
> SDL     : found 1.2.15
> FONT    : found
> IMAGE   : found
> MIXER   : found
> SMPEG   : found 0.4.5
> PNG     : not found
> JPEG    : not found
> SCRAP   : found
> PORTMIDI: found
> PORTTIME: found
> V4L2    : found
> 
> 
> Warning, some of the pygame dependencies were not found. Pygame can still
> compile and install, but games that depend on those missing dependencies
> Traceback (most recent call last):
>   File "setup.py", line 132, in <module>
>     config.main()
>   File "/«BUILDDIR»/pygame-1.9.1release+dfsg/config.py", line 137, in main
>     deps = CFG.main()
>   File "/«BUILDDIR»/pygame-1.9.1release+dfsg/config_unix.py", line 188, in 
> main
>     will not run. Would you like to continue the configuration?"""):
>   File "/«BUILDDIR»/pygame-1.9.1release+dfsg/config_unix.py", line 27, in 
> confirm
>     reply = raw_input('\n' + message + ' [Y/n]:')
> EOFError: EOF when reading a line
> dh_auto_clean: python2.6 setup.py clean -a returned exit code 1
> make: *** [clean] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/04/19/pygame_1.9.1release+dfsg-5_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to