On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
On Fri, 9 May 2025 22:41:09 GMT, Mikael Vidstedt wrote:
> The cmp-baseline builds expect the source-date to be stable across the two
> builds (really: invocations of configure). For CI builds the source-date gets
> set based on information from the job, but for local builds it gets the
> defau
