Bug#1082135: sumo: FTBFS randomly due to dh_installdocs misbehavior (?)

[Santiago Vila]

owner 1082135 !
severity 1082135 serious
thanks

Hello. After I recently switched to 4th generation EPYC processors
from AMD for archive rebuilds, this package now fails to build
always in bookworm, using machines with 2 CPUs:

Status: successful  sumo_1.15.0+dfsg-1_amd64-20240404T064207.173Z
Status: successful  sumo_1.15.0+dfsg-1_amd64-20240705T061342.785Z
Status: successful  sumo_1.15.0+dfsg-1_amd64-20240902T032618.520Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T043747.568Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T093515.959Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T093517.172Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T121904.457Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T121904.386Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T121904.349Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T122003.109Z
Status: failed      sumo_1.15.0+dfsg-1_amd64-20241020T122003.066Z

I honestly do not consider this suitable for release.

So, unless anybody has a better idea, I'll add --no-parallel to dh invocation
at the top of debian/rules (the package never failed to build for me
on machines with a single CPU).

Before doing so, I still would like some input from debhelper and doxygen maintainers (and of course other members of Debian Science).

(Cc to the last uploader and the usual uploader in the control file).

Thanks.