Re: What to do with nondeterministic_ordering_in_documentation_generated_by_doxygen?

Chris Lamb chris at
Mon Jan 11 23:38:03 GMT 2021

Hi Ferenc,

> I decided it's best to ask: is there anything for me (as the
> maintainer of the affected packages) to do here?  Does this issue
> require further investigation?  If all is clear, is anybody working
> on fixing Doxygen, is there an upstream issue about this?

Thanks for reaching out. As a bit of background, a package that has
been "tagged" as being caused by X or Y (in this case, Doxygen) does
not imply that much, beyond it being a method to help me focus on
the outstanding issues that have the highest priority.

Sometimes these tags are too broad (Doxygen has many similar-looking
reproducibility issues that have been categorised under an
wide-reaching tag), and sometimes they are wrong through some
oversight. They are meant to be short, helpful pointers to get
started, rather than the product of rigorous checking and

However, to answer your specific questions (and assuming that Doxygen
is indeed the root cause), unless you see an open issue against the
Doxygen package that I cannot, I don't believe anyone is working on
this particular problem with Doxygen upstream. So yes, this issue
does require further investigation. As a maintainer of an affected
package I suppose you could consider this to be an invitation to
be able to contribute.

Best wishes,

     : :'  :     Chris Lamb
     `. `'`      lamby at 🍥

More information about the Reproducible-builds mailing list