Your message dated Sun, 05 Oct 2014 15:11:19 +0200
with message-id <2751906.1yOaaDVCff@sephirot>
and subject line Builds fine
has caused the Debian Bug report #759856,
regarding <stdio.h> not included anymore before <jpeglib.h> (causes
tuxonice-userui to FTBFS)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
759856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tuxonice-userui
Version: 1.1+dfsg1.gc3bdd83-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -O3
> -DUSE_FBSPLASH -Wall -O3 -g -I/usr/include/freetype2/ -I. -c mng_callbacks.c
> -o mng_callbacks.o
> In file included from /usr/include/libmng_types.h:210:0,
> from /usr/include/libmng.h:386,
> from mng_callbacks.c:12:
> /usr/include/jpeglib.h:954:30: error: unknown type name 'FILE'
> EXTERN(void) jpeg_stdio_dest JPP((j_compress_ptr cinfo, FILE * outfile));
> ^
> /usr/include/jpeglib.h:955:29: error: unknown type name 'FILE'
> EXTERN(void) jpeg_stdio_src JPP((j_decompress_ptr cinfo, FILE * infile));
> ^
> make[3]: *** [mng_callbacks.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/tuxonice-userui_1.1+dfsg1.gc3bdd83-1_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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---
Now builds ok; closing it.
--
David
--- End Message ---
