Re: [buildd-tools-devel] Bug#843773: misleading timestamps in binnmus

2016-11-16 Thread Raphael Hertzog
Hi, On Mon, 14 Nov 2016, Johannes Schauer wrote: > > Can I ask you the converse question: what same-timestamp proposal do > > you think is best and why ? > > I found Guillem's suggestion the most sensible and as far as I understand the > matter also the easiest to implement: > > Quoting Guillem

Re: [buildd-tools-devel] Bug#843773: misleading timestamps in binnmus

2016-11-10 Thread Ximin Luo
(resending again to the correct addresses; I could never get used to debbugs CC behaviour.) Ximin Luo: > Ansgar Burchardt wrote: >> The date from the last sourceful upload should probably still be used >> for any date/time information included in generated files to ensure >> they are identical

Re: [buildd-tools-devel] Bug#843773: misleading timestamps in binnmus

2016-11-10 Thread Holger Levsen
On Thu, Nov 10, 2016 at 08:59:48AM -0200, Johannes Schauer wrote: > One solution would be to increase SOURCE_DATE_EPOCH by 1 second for every > binNMU to a package. > > Any other ideas? set SOURCE_DATE_EPOCH to the creation time of that changelog.$arch entry? -- cheers, Holger

Re: [buildd-tools-devel] Bug#843773: misleading timestamps in binnmus

2016-11-10 Thread Johannes Schauer
Hi, Quoting Emilio Pozuelo Monfort (2016-11-10 07:04:55) > On 10/11/16 10:00, Ansgar Burchardt wrote: > > The date from the last sourceful upload should probably still be used > > for any date/time information included in generated files to ensure > > they are identical on all architectures (or