Looks like this was a Doxygen bug which was recently fixed upstream in https://github.com/doxygen/doxygen/commit/d763a8c1f6c73982ae83ddd3b390528b3e00770e.

It was released in Doxygen 1.8.16. Our current Debian channel (Stretch) packages 1.8.13. But, someone has already made and published a Doxygen 1.18.16 package in the experimental channel (https://packages.debian.org/experimental/doxygen). Perhaps this can be backported?

Tagging CPT as team I suspect would be most interested in seeing this get deployed. Tagging RelEng as owner of the doc1001 server.

Untagging Platform Engineering as @apaskulin is tagged as a watcher to track.

Talked with @hashar. While the CI container and Dockerfile is managed by RelEng, the package itself comes directly from the prod apt repo.

Tagging ServiceOps: Would it be possible to build (or re-use from debian/experimental) Doxygen 1.8.16 to eg buster-wikimedia component/doxygen for use in CI?

@Krinkle given it's a CI container, why not install doxygen with pip (properly frozen) instead of importing a package?

EDIT: nevermind, I confused softwares. Doxygen needs a proper build as it's in C++.

So we'd need to backport the package - I'd rather recommend the use of a build container (or a multi-stage build) to obtain the software, but we can try a simple rebuild probably.

A backport of the package made available as a component would fit nicely. If we follow what we do for other CI containers we would so something like:

FROM {{ "docker-registry.wikimedia.org/wikimedia-buster" | image_tag }}

USER root
RUN echo "deb http://apt.wikimedia.org/wikimedia stretch-wikimedia component/doxygen" \
    > /etc/apt/sources.list.d/buster-doxygen.list \
    && {{ "doxygen" | apt_install }}

USER nobody
ENTRYPOINT ["doxygen"]

Which is super easy :] If an upgrade is needed later on:

• build the new Debian package
• upload to apt
• bump image changelog
• docker-pkg
• done \o/

Happy to do the CI container/config stuff once a package is around (either upstream or in our magic repo).