Control: tags -1 + moreinfo

Hi Santiago!

2019-02-26 23:28 Santiago Vila:
Package: src:ftgl
Version: 2.4.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:

(Yes, I know that it built ok 4 hours ago, but apparently not anymore)

--------------------------------------------------------------------------------
[...]
debian/rules binary-arch
dh binary-arch
  dh_update_autotools_config -a
  dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.auto'.
libtoolize: copying file '.auto/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:31: installing '.auto/compile'
configure.ac:12: installing '.auto/config.guess'

[... snipped ...]

! Missing \cr inserted.
<inserted text>
               \cr
l.40 \end{DoxyEnumFields}

I'm guessing that you meant to end an alignment here.

! Misplaced \cr.
<inserted text> \cr

l.40 \end{DoxyEnumFields}

I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.

! Missing \cr inserted.
<inserted text>
               \cr
l.40 \end{DoxyEnumFields}

(That makes 100 errors; please try again.)
Here is how much of TeX's memory you used:
15019 strings out of 494561
215980 string characters out of 6177454
308954 words of memory out of 5000000
18251 multiletter control sequences out of 15000+600000
61038 words of font info for 84 fonts, out of 8000000 for 9000
14 hyphenation exceptions out of 8191
53i,16n,92p,802b,557s stack positions out of 5000i,500n,10000p,200000b,80000s

!  ==> Fatal error occurred, no output PDF file produced!
make[4]: *** [Makefile:619: stamp-latex] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/docs'
make[3]: *** [Makefile:519: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: *** [Makefile:428: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 "GLUT_LIBS=-lglut -lGLU -lGL -lm" returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
--------------------------------------------------------------------------------

(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ftgl.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

This was due to bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 , as mentioned
in the changelog.

Since I saw it marked as closed, I enabled the PDF doc again and it
worked, despite the bug in the documentation generator not having
actually been fixed at the time.

I don't know why it worked, if due to older versions than the ones
affected being used, or something else.  The texlive maintainer mentions
"clean up the mess due to delayed acceptance" and closing it for a
second time yesterday, so I don't know what really happened.

Also, the network of mirrors had problems and haven't been updated for a
couple of days, including some buildds, so it's possible that this might
have played a role?

In any case, it built for me at the time of uploading, it built in
almost all buildds except unimportant ones, and I just tested and it
builds for me again locally with git-pbuilder and an up-to-date chrrot,
so I think that everything is fine now?

Thanks for caring!

--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>

Reply via email to