[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: doxygen and TeXlive 2025.20250727-2



Hi,

see below.

Il 19/08/25 23:41, Hilmar Preuße ha scritto:
Hello,

according to David this looks like an issue in doxygen. The doxygen uses ltabu, which seemed to break with a new version of array. Maybe try the workaround mentioned in the last post. That version of array is contained in texlive-latex-base as /usr/share/texlive/texmf-dist/tex/latex/tools/array-2023-11-01.sty

If its related to tabu, there is a long story of issues related to that in doxygen:
https://github.com/doxygen/doxygen/issues?q=tabu

...
19.08.2025 18:22:07 Rene Engelhard <rene@debian.org>:

Hi,

I got the following on a graphite2 build. (Disabled in 1.3.14-3 for now):

...
[7]) (./structgr__faceinfo.tex
! Undefined control sequence.
<argument> ...rtpbox {\@nextchar }\insert@pcolumn
                                                    \@endpbox \do@row@strut \o...
l.55 \begin{DoxyEnumFields}{Enumerator}
                                         ?
! Emergency stop.
<argument> ...rtpbox {\@nextchar }\insert@pcolumn
                                                    \@endpbox \do@row@strut \o...
l.55 \begin{DoxyEnumFields}{Enumerator}
...
This works in stable with doxygen 1.9.8+ds-2.1 and stables TeXlive (2024.20250309-1) but breaks with unstables new one
(2025.20250727-2).

Yes I am a bit behind with doxygen releases ... apparently latest is 1.14 of 2025-05-24.

There is a Debian doxygen 1.12 package I prepared last year and never had the time to upload even to experimental, you can get it from the artifacts of this CI job:
https://salsa.debian.org/debian/doxygen/-/jobs/6153017

It may be worth trying against that version.

The question is whether it's a doxygen bug (and doxygen needs to be updated...) or a TeXlive bug....

It may be more effective to create directly an issue on upstream's issue tracker, in my experience they are very collaborative. Or if you prefer file a bug in the BTS and I'll forward it.

Much more important than where the bug is filed is to isolate the problem in a simple and easy to test case.

For the doxygen devs it doesn't really help to point to a debian build log file, they need a reproducible example.

Any idea?

Regards,

Rene


Reply to: