Your message dated Sun, 17 Mar 2019 23:03:45 -0400
with message-id <udlbm28994e....@mit.edu>
and subject line Re: Bug#924820: fltk1.3: FTBFS: cp: cannot stat 
'latex/refman.pdf': No such file or directory
has caused the Debian Bug report #924820,
regarding fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or 
directory
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.)


-- 
924820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fltk1.3
Version: 1.3.4-7
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/documentation'
> echo "Generating Doxyfile ..."
> Generating Doxyfile ...
> sed -e's,@FL_VERSION@,1.3.4,' \
>     -e's,@GENERATE_HTML@,YES,' \
>     -e's,@GENERATE_LATEX@,NO,' \
>     -e's, @LATEX_HEADER@,,' \
>     -e's,@CMAKE_CURRENT_SOURCE_DIR@/,,' \
>     -e's,@CMAKE_SOURCE_DIR@/,../,' \
>     < Doxyfile.in > Doxyfile
> echo "Generating HTML documentation..."
> Generating HTML documentation...
> rm -rf html
> /usr/bin/install -c -d  html
> /usr/bin/doxygen
> if test "x/usr/bin/doxygen" = "x" ; then \
>   echo "Sorry - doxygen not found. Please install doxygen and run 
> configure."; \
> fi
> test -d html && cp src/tiny.png html/
> echo "Generating Doxybook ..."
> Generating Doxybook ...
> sed -e's,@FL_VERSION@,1.3.4,' \
>     -e's,@GENERATE_HTML@,NO,' \
>     -e's,@GENERATE_LATEX@,YES,' \
>     -e's,@LATEX_HEADER@,src/fltk-book.tex,' \
>     -e's,@CMAKE_CURRENT_SOURCE_DIR@/,,' \
>     -e's,@CMAKE_SOURCE_DIR@/,../,' \
>     < Doxyfile.in > Doxybook
> DOXY_VERSION=`/usr/bin/doxygen --version`; \
> YEAR=`date -ud'Thu, 15 Mar 2018 22:20:20 -0400' +%Y`; \
> FLTK_VERSION=`cat ../VERSION`; \
> TODAY=`date -ud'Thu, 15 Mar 2018 22:20:20 -0400' +'%B %e, %Y'`; \
> sed -e"s/@YEAR@/$YEAR/g" \
>     -e"s/@FL_VERSION@/1.3.4/g" \
>     -e"s/@DOXY_VERSION@/$DOXY_VERSION/g" \
>     -e"s/\\\\today{}/$TODAY/g" \
> < src/fltk-book.tex.in > src/fltk-book.tex
> rm -rf latex
> echo "Generating PDF documentation ..."
> Generating PDF documentation ...
> /usr/bin/doxygen Doxybook
> ./make_pdf
> cp -f latex/refman.pdf fltk.pdf
> cp: cannot stat 'latex/refman.pdf': No such file or directory
> make[2]: *** [Makefile:178: pdf] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2019/03/15/fltk1.3_1.3.4-7_testing.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.

--- End Message ---
--- Begin Message ---
Source: fltk1.3
Version: 1.3.4-9

Lucas Nussbaum <lu...@debian.org> writes:

> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.

Hi, Lucas.

Thanks for the report, which I will however close as a duplicate of
#921294 (in turn fallout from texlive-latex-extra bug #920459).  I
definitively addressed this failure in unstable with 1.3.4-9 on Feb. 27.
At the time of the freeze, the only thing keeping this version from
migrating was the fact that I addressed the failure by insisting on a
fixed version of texlive-latex-extra, which turned out to be blocked for
unclear reasons (and still is, alas).

I presume we won't release with a broken texlive-latex-extra, so my plan
at this point is to file an unblock request once TeX Live migrates.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

--- End Message ---

Reply via email to