Re: Two questions about build-path reproducibility in Debian

2024-03-06 Thread John Neffenger
Thank you, Vagrant, for taking my concerns seriously. I realize you've been working on this much longer than I have, so I appreciate your perspective. On 3/6/24 10:55 AM, Vagrant Cascadian wrote: That means that we do not always support each other in all things, but we can support each other

Re: Two questions about build-path reproducibility in Debian

2024-03-06 Thread Vagrant Cascadian
On 2024-03-05, John Neffenger wrote: > On 3/5/24 2:11 PM, Vagrant Cascadian wrote: >>> I have no way to change these choices. >> >> Then clearly you have not been provided sufficient information, >> configuration, software, etc. in order to reproduce the build! > > Rather, I really can't change

Re: Two questions about build-path reproducibility in Debian

2024-03-06 Thread Vagrant Cascadian
On 2024-03-05, John Gilmore wrote: > A quick note: > Vagrant Cascadian wrote: >> It would be pretty impractical, at least for Debian tests, to test >> without SOURC_DATE_EPOCH, as dpkg will set SOURCE_DATE_EPOCH from >> debian/changelog for quite a few years now. > > Making a small patch to the

Re: Two questions about build-path reproducibility in Debian

2024-03-06 Thread Holger Levsen
On Tue, Mar 05, 2024 at 11:51:16PM +, Richard Purdie wrote: > FWIW Yocto Project is a strong believer in build reproducibiity > independent of build path and we've been quietly chipping away at those > issues. [...] > OpenEmbedded-Core (around 1000 pieces of software) is 100% reproducible >

Re: Two questions about build-path reproducibility in Debian

2024-03-06 Thread James Addison via rb-general
Hi Vagrant, Narrowing in on (or perhaps nitpicking) a detail: On Mon, 4 Mar 2024 at 20:41, Vagrant Cascadian wrote: > > On 2024-03-04, John Gilmore wrote: > > Vagrant Cascadian wrote: > >> > > to make it easier to debug other issues, although deprioritizing them > >> > > makes sense, given