[Pkg-rust-maintainers] Bug#976369: timestamp too far in the past

[Geert Stappers]

Control: retitle -1 timestamp too far in the past

On Fri, Dec 04, 2020 at 08:54:48AM +0100, Aurelien Jarno wrote:
> ----- Forwarded message from Debian FTP Masters <ftpmaster at ftp-master.debian.org> -----
> To: mips64el Build Daemon <buildd_mips64el-mipsel-osuosl-01 at buildd.debian.org>

Good forward.   Yes, that is a compliment


> Date: Fri, 04 Dec 2020 01:51:38 +0000
> Subject: rust-csv_1.1.5-1_mips64el-buildd.changes REJECTED
> Message-Id: <E1kl0G2-0002tk-Mf at fasolo.debian.org>
> 
> librust-csv-dev_1.1.5-1_mips64el.deb: has 66 file(s) with a timestamp too far in the past:
> usr/share/cargo/registry/csv-1.1.5/.gitignore (Thu Jan  1 00:00:00 1970)
> usr/share/cargo/registry/csv-1.1.5/COPYING (Thu Jan  1 00:00:00 1970)
> usr/share/cargo/registry/csv-1.1.5/ISSUE_TEMPLATE.md (Thu Jan  1 00:00:00 1970)
      ...
> usr/share/cargo/registry/csv-1.1.5/src/tutorial.rs (Thu Jan  1 00:00:00 1970)
> usr/share/cargo/registry/csv-1.1.5/src/writer.rs (Thu Jan  1 00:00:00 1970)
> usr/share/cargo/registry/csv-1.1.5/tests/tests.rs (Thu Jan  1 00:00:00 1970)
> ----- End forwarded message -----

In the build for  arm64,
 https://buildd.debian.org/status/fetch.php?pkg=rust-csv&arch=arm64&ver=1.1.5-1&stamp=1607044951&raw=0
lots of the same "1970-01-01 00:00"


FWIW  I agree with the mips64el buildd to report this
too far in the past in the past time stamp.
 


Regards
Geert Stappers
-- 
Silence is hard to parse