Fw: Build Reproducibility in Debian - Opinion Needed

[Muhammad Hassan]

Hello Chris,

Thanks for your response. Forwarding to the list rb-general at lists.reproducible-builds.org.

Everyone: See attached email for queries. Your kind response is awaited.



Regards,

Muhammad Hassan
M.Math (Computer Science) || University of Waterloo

[https://uwaterloo.ca/brand/sites/ca.brand/files/styles/body-500px-wide/public/uploads/images/logo-vertical-.jpg?itok=rBgJ8S9H]

(+1) 548 994 4717 / LinkedIn<https://www.linkedin.com/in/muhammad1hassan>
________________________________
From: Muhammad Hassan <muhammad.hassan at uwaterloo.ca>
Sent: Sunday, August 21, 2022 3:19 PM
To: chris at chris-lamb.co.uk <chris at chris-lamb.co.uk>
Subject: Build Reproducibility in Debian - Opinion Needed

Hello Chris,

It is hoped that you are doing well. You might recall that we corresponded in the past about my research project on detecting build unreproducibility using commit code features in Debian.


I was hoping to get your opinion on some additional matters about that.



  1.  Do you feel that Build Unreproducibility issues can be captured using Just-In-Time Defect Prediction metrics (such as the amount of code change introduced or the dispersion of changes across different modules)? Basically, do you find that certain types of commits (such as widespread ones) are more problematic for build reproducibility?
  2.  Do you feel there is potential for detecting build unreproducibility statically (without executing adversarial rebuilds)?
  3.  What advice/training are developers given to ensure that they don't induce a build unreproducibility issue?


Your response is awaited. Thank you 🙂

Regards,
Muhammad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20220822/64ce4a5f/attachment.htm>