Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read
script nolsbheader: No such file or directory"):
> Thanks for this. However, I am currently unable to repoduce this
> failure in my customary pbuilder setup. And it doesn't appear at
> reproducible builds either[1]
I just tried this myself with my usual sbuild setup and it succeeded
there too[1]. Lucas, I think something from your rebuild environment
(a chroot of some kind I presume) must be triggering this failure. Is
there some way we can reproduce it more precisely (eg, a buildinfo
file?)
I looked at the build log
http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
and compared it to the one from my sbuild, using diff. There are a
lot of changes to the "furniture" but also there are noise changes to
the output of the insserv test suite, including ordring changes of
passing tests. This seemed surprising to me.
Mark, is the insserv test suite supposed to produce deterministic
output ?
Ian.
[1] just-updated sid chroot, "dgit sbuild -wgf build -c build".
