Hi,

as you can read below upstream can not reproduce this problem.  I
checked the last upstream version and the problem persists - probably
due to different doxygen versions?  I've moved the packaging of cimg
to Git

      https://anonscm.debian.org/git/debian-science/packages/cimg.git

and injected the latest upstream version there.  Any help from an
doxygen expert would be welcome.

Kind regards

      Andreas.

On Fri, Apr 29, 2016 at 08:49:07AM +0200, David Tschumperlé wrote:
> Hello Andreas,
> 
> I've just tested here with the latest version available (1.7.1), and
> everything works as expected, without error.
> Maybe there was an error in 1.6.5, but so far it seems to have been fixed.
> 
> Regards,
> 
> David.
> 
> 2016-04-28 16:45 GMT+02:00 Andreas Tille <andr...@an3as.eu>:
> 
> > Hi David,
> >
> > there is an error when trying to build the cimg documentation that did
> > not happened before (= at the time when I have created the package).
> >
> > The log which you can find in the Debian bug tracking system[1] in full
> > length says:
> >
> > ...
> > Runaway argument?
> > {\texorpdfstring {operator\%=(const t value)}{operator\begin {DoxyPar\ETC.
> > ! Paragraph ended before \@sect was complete.
> > <to be read again>
> >                    \par
> > l.4286
> >
> > ?
> > ! Emergency stop.
> > <to be read again>
> >                    \par
> > l.4286
> >
> > !  ==> Fatal error occurred, no output PDF file produced!
> > Transcript written on refman.log.
> > Makefile:6: recipe for target 'refman.pdf' failed
> >
> >
> > Have you ever heard of similar issues?  Is there perhaps an explanation
> > or a known patch?
> >
> > Kind regards
> >
> >        Andreas.
> >
> >
> > [1]
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;filename=cimg_1.6.5%2Bdfsg-1_amd64.build;msg=5;bug=819606
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to