Your message dated Mon, 11 Mar 2019 17:50:16 +0100
with message-id 
<ca+7wuswzhrmufe27_kzxg_nzjbv3p6cxubepmzwjh3+-m6n...@mail.gmail.com>
and subject line Re: Bug#921780: esajpip: FTBFS (LaTeX error)
has caused the Debian Bug report #921780,
regarding esajpip: FTBFS (LaTeX error)
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 [email protected]
immediately.)


-- 
921780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:esajpip
Version: 0.1~bzr33-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<<PKGBUILDDIR>>'
/usr/bin/make documentation
make[2]: Entering directory '/<<PKGBUILDDIR>>'
make -C doc
make[3]: Entering directory '/<<PKGBUILDDIR>>/doc'
fig2dev -L pstex jpip_fig.fig > jpip_fig.eps
(fig2dev -L pstex_t -p jpip_fig jpip_fig.fig | sed 
's/includegraphics{/includegraphics{..\//g') > jpip_fig.tex
epstopdf jpip_fig.eps
fig2dev -L pstex partition.fig > partition.eps

[... snipped ...]


LaTeX Warning: Reference `socket_8h' on page 10 undefined on input line 92.


LaTeX Warning: Reference `socket__stream_8cc' on page 10 undefined on input lin
e 93.


LaTeX Warning: Reference `socket__stream_8h' on page 10 undefined on input line
 94.

) [10]
Chapter 5.
(./namespacedata.tex (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
[11]
Underfull \hbox (badness 10000) detected at line 68
[][][]

Underfull \hbox (badness 10000) detected at line 83
[][][]
) (./namespacehttp.tex [12]) (./namespaceipc.tex [13]
! Missing } inserted.
<inserted text> 
                }
l.58 \end{DoxyEnumFields}
                         
? 
! Emergency stop.
<inserted text> 
                }
l.58 \end{DoxyEnumFields}
                         
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/doc/latex'
make[3]: *** [Makefile:23: documentation] Error 2
rm codestream.eps partition.eps client_manager.eps architecture.eps jpip_fig.eps
make[3]: Leaving directory '/<<PKGBUILDDIR>>/doc'
make[2]: *** [Makefile:111: documentation] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:29: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep 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 -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/esajpip.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.

Thanks.

--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix

Hi,

On Sat, Feb 9, 2019 at 1:18 AM Santiago Vila <[email protected]> wrote:
> !  ==> Fatal error occurred, no output PDF file produced!

I cannot also reproduce this Latex issue. Are you sure there has not
been a broken latex package upload recently ?

In any case esajpip should migrate back to testing hopefully.

--- End Message ---

Reply via email to