HELP WANTED: Figure out why svnlite build is sometimes not reproducible
Hi all, Doing freebsd-update builds, I've now had two instances where /usr/bin/svnlite has built inexplicably differently -- changes scattered all over the binary. This is a problem for freebsd-update because it means that at some point in the future the builds may not be able to correctly identify if that binary needs to be distributed as part of a security update. The svn* binaries had build date+time stamps in them until I nuked them in r257129, but those are cleanly self-contained -- this is something else building differently. Unfortunately despite the freebsd-update builds running into this, I haven't been able to reproduce it myself and so I can't track down what is causing this. If anyone can provide assistance with this, it would be very gratefully received. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HELP WANTED: Figure out why svnlite build is sometimes not reproducible
On 10/27/13 14:52, Erik Cederstrand wrote: Den 27/10/2013 kl. 22.03 skrev Colin Percival cperc...@freebsd.org: Doing freebsd-update builds, I've now had two instances where /usr/bin/svnlite has built inexplicably differently -- changes scattered all over the binary. Which kind of changes? Are you aware of the -D flag to ar(1) (wipes timestamps in archives)? Are you always using the same SRCDIR/DESTDIR (this affects the __FILE__ macro)? Same DEBUG_FLAGS? Changes in lots of non-7-bit-ASCII bits all over the file. I'm guessing it's executable code. Yes, aware of -D flag. That's a red herring since this isn't an archive; and all the other binaries are fine. Yes, all the build context is the same -- this is happening inside a chroot with the same build script running every time. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HELP WANTED: Figure out why svnlite build is sometimes not reproducible
Hi Colin, Den 27/10/2013 kl. 22.03 skrev Colin Percival cperc...@freebsd.org: Hi all, Doing freebsd-update builds, I've now had two instances where /usr/bin/svnlite has built inexplicably differently -- changes scattered all over the binary. Which kind of changes? Are you aware of the -D flag to ar(1) (wipes timestamps in archives)? Are you always using the same SRCDIR/DESTDIR (this affects the __FILE__ macro)? Same DEBUG_FLAGS? Erik ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HELP WANTED: Figure out why svnlite build is sometimes not reproducible
Colin Percival wrote this message on Sun, Oct 27, 2013 at 14:03 -0700: Doing freebsd-update builds, I've now had two instances where /usr/bin/svnlite has built inexplicably differently -- changes scattered all over the binary. This is a problem for freebsd-update because it means that at some point in the future the builds may not be able to correctly identify if that binary needs to be distributed as part of a security update. The svn* binaries had build date+time stamps in them until I nuked them in r257129, but those are cleanly self-contained -- this is something else building differently. Unfortunately despite the freebsd-update builds running into this, I haven't been able to reproduce it myself and so I can't track down what is causing this. If anyone can provide assistance with this, it would be very gratefully received. Can you post the binaries somewhere so we can take a look at them? -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org