Version annotated: | 16.2.0-4 |
Comments: |
I think this is exposed by nondeterminstic filesystem ordering but the root cause in that it generates an AST-like graph of all the source files in order to inject debug calls; my clue for this is the "but could not be resolved" error messages in the build log diffs. |
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |