> > *iff* SOURCE_DATE_EPOCH is set: > > > > - mtimes are taken from stat(2). [The FS creator is responsible for > > ensuring they are reproducible, possibly by some "clamping" call > > to `find -newermt | xargs touch …`.] > > > > - atime is copied from mtime [as FS creator "can't" set that]. > > > > - ctime is copied from mtime [ditto]. > > man 2 utime promises to set atime and xorriso tries to restore it when > extracting files to disk.
I put "can't" in quotes as there is no pervasive/widespread shell-level tool for this (cf. touch(1)) so I stand by this. > But for ctime i know no portable method. Mm. > Export SOURCE_DATE_EPOCH and forget about any other time issues which > you don't create yourself by own xorriso arguments. I'm sorry but I don't quite follow and I don't want to read what I want to read. Please could you clarify exactly the behaviour in this case? > Looks like --set_all_file_dates is losing its only user even before it > gets released. (Which is good; the less options the better IMHO.) > > I am therefore not testing them from > > the "Debian" point of view and ACKs are simply my own testcases. > > Any ACK or NAK is highly welcome. I'm sure; I was just trying to avoid the case of — heaven forbid we broke the Debian CD creation! — that we would get the blame as ACKing on their behalf. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- _______________________________________________ Reproducible-builds mailing list Reproduciblefirstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds