Re: multi-arch:same failures when bin-nmus changelog dates are not the same

2018-03-29 Thread Julien Cristau
On 03/29/2018 06:35 PM, Jean-Michel Vourgère wrote: > Some thoughs: > > On arm64 [1] the binnmu .buildinfo contains: > Environment: > DEB_BUILD_OPTIONS="parallel=3" > LC_ALL="POSIX" > SOURCE_DATE_EPOCH="1522153653" > > while on armhf [2] the binnmu .buildinfo contains: > Environment: >

Re: multi-arch:same failures when bin-nmus changelog dates are not the same

2018-03-29 Thread Jean-Michel Vourgère
Some thoughs: On arm64 [1] the binnmu .buildinfo contains: Environment: DEB_BUILD_OPTIONS="parallel=3" LC_ALL="POSIX" SOURCE_DATE_EPOCH="1522153653" while on armhf [2] the binnmu .buildinfo contains: Environment: DEB_BUILD_OPTIONS="parallel=4" LC_ALL="POSIX" SOURCE_DATE_EPOCH="154789"

Re: multi-arch:same failures when bin-nmus changelog dates are not the same

2018-03-29 Thread Wookey
On 2018-03-29 14:41 +0200, Jean-Michel Vourgère wrote: > Hello > > My package rrdtool [1] got some multi-arch failures since last bin-nmu. > > The problem is that pod2man uses the changelog date to generate the man > footer, and that date is no longer the same on all architectures ! Don't do

Re: multi-arch:same failures when bin-nmus changelog dates are not the same

2018-03-29 Thread Julien Cristau
On 03/29/2018 02:41 PM, Jean-Michel Vourgère wrote: > Hello > > My package rrdtool [1] got some multi-arch failures since last bin-nmu. > > The problem is that pod2man uses the changelog date to generate the man > footer, and that date is no longer the same on all architectures ! > >