[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2021-05-03 Thread Filipe Laíns
Change by Filipe Laíns : -- nosy: +FFY00 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2020-08-24 Thread Maarten
Maarten added the comment: My previous comment should have contained: Because I noticed the timestamp was not included in the CRC, ... -- ___ Python tracker ___

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2020-08-24 Thread Maarten
Maarten added the comment: I have the same issue. The timestamp is inserted here: https://github.com/python/cpython/blob/802726acf6048338394a6a4750835c2cdd6a947b/Lib/tarfile.py#L419-L420 Because I noticed the timestamp was not included in the timestamp, I could zero it by doing: ``` with

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2017-11-10 Thread Martin Panter
Martin Panter added the comment: Perhaps you can compress the tar file using the “gzip.GzipFile” class. It accepts a custom “mtime” parameter (see Issue 4272, added in 2.7 and 3.1+): >>> gztar = BytesIO() >>> tar = GzipFile(fileobj=gztar, mode="w", mtime=0) >>>

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2017-11-08 Thread Jonas H.
Jonas H. added the comment: This affects me too. -- nosy: +jonash ___ Python tracker ___

[issue31526] Allow setting timestamp in gzip-compressed tarfiles

2017-09-19 Thread Jack Lloyd
New submission from Jack Lloyd: Context: I have a script which checks out a software release (tagged git revision) and builds an archive to distribute to end users. One goal of this script is that the archive is reproducible, ie if the script is run twice (at different times, on different