Hi Guillem, thanks for this bug report and X-Debbugs-Cc:ing us! On Mon, Feb 25, 2019 at 10:53:36PM +0100, Guillem Jover wrote: > The reproducible build state is currently only provided for «testing», > because «sid» contains additional checks that are deemed would annoy > maintainers. the problem with the unreproducibility issues in unstable currently is that they are mostly unactionable as the way forward for build path issues is not yet clear. thus such warnings can and will be seen as annoying. > I've been aware of this in the past, but was still caught off guard > when checking my DDPO page and seeing that inetutils was still marked > as non-reproducible, even though the tests for sid said it was. And > thought there was some stale data going on. basically currently we are only targetting testing/buster with our efforts. > I think it would be ideal if the reproducible states was shown > explicitly for both testing and sid, even though for now the sid > column would just print a sigil for N/A data (‘-’? with an alt text > mentioning the suite), this would make the information immediately > obvious. Also I think that in the future the reproducible people > might want to expose the state for sid too, at which point the N/A > marker can just be switched to provide the actual state. I'm not sure N/A will be less confusing as we do have data for unstable.. but maybe thats a way forward. -- tschau, Holger ------------------------------------------------------------------------------- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
Attachment:
signature.asc
Description: PGP signature