[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

On Thu, Mar 29, 2018 at 04:41:50PM +0100, Wookey wrote:
> On 2018-03-29 14:41 +0200, Jean-Michel Vourgère wrote:
> > 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 that. It's a reproducibility failure as well as breaking
> multi-arch co-installability.
> > Please advise how to proceed!
> I'm surprised the reproducibility people have not nobbled pod2man to
> stop this behaviour already. Is there a bg about it somewhere?

We met a lot of push backs when originally we were trying to *remove* as
many datetimes as possible.
Since then we found it was much easier to ask people to programatically
set those datetimes to the value of SOURCE_DATE_EPOCH, which in Debian
we set to the time in the topmost pargraph of d/changelog.
pod2man has been patched exactly to that goal, and it does make rrdtools
reproducible indeed.

I don't have an opinion on how to best approach this issue.

                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply to: