[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Timestamps in tarballs created by 'patch-and-repack'
From: |
Mark H Weaver |
Subject: |
Timestamps in tarballs created by 'patch-and-repack' |
Date: |
Tue, 14 Jul 2015 15:15:55 -0400 |
Hello Guix,
One of the MIPS build slaves has a malfunctioning clock, and sometimes I
discover that the clock is several days behind or ahead. In the past
I've been able to simply reset the clock and restart builds, but now I
have a more serious problem:
Patched tarballs created by 'patch-and-repack' were built on a build
slave with the clock set about 8 days ahead. Those tarballs are now in
Hydra's store, and include timestamps in the tar file that are set so
far ahead that attempts to build them are failing. I'm currently
attempting to find and delete the bad tarballs from hydra's store.
However, this raises a deeper problem: all of the outputs of
'patch-and-repack' contain non-deterministic timestamps, and these
timestamps can cause problems with future builds.
Would it be sufficient to simply zero out all of the timestamps before
repacking?
Mark
- Timestamps in tarballs created by 'patch-and-repack',
Mark H Weaver <=