From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 21111-done@debbugs.gnu.org
Subject: bug#21111: possibly bogus in binary tarball
Date: Wed, 22 Jul 2015 22:59:05 +0200 [thread overview]
Message-ID: <87pp3j6h9i.fsf@gnu.org> (raw)
In-Reply-To: <87615cszue.fsf@pc102091.liv.ac.uk> (Dave Love's message of "Wed, 22 Jul 2015 21:26:49 +0100")
Dave Love <fx@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Interestingly, I do not get this message, both with ‘tar xf’ and
>> ‘tar xvf’ with GNU tar 1.28.
>>
>> I tried with different timezones, and I can’t trigger it.
>>
>> Dave: What version of GNU tar do you use, and in what timezone?
>>
>> TIA,
>> Ludo’.
>
> It was on RHEL6 in the UK zone
>
> $ grep -I zone /etc/sysconfig/clock
> ZONE="Europe/London"
>
> with:
>
> $ rpm -q tar
> tar-1.23-11.el6.x86_64
>
> There aren't any obviously-relevant patches in the tar package changelog.
According to the 1.28 manual (info "(tar) warnings"), this specific
warning can be explicitly enabled with --warning=timestamp.
However, I tried variations of the following command with no luck:
TZ=Europe/London tar --warning=timestamp --extract -f \
guix-binary-0.8.3.i686-linux.tar.xz
So maybe the fact that 1.28 doesn’t emit the warning is a bug.
> I think it would be worth a note on the timestamps anyway to avoid
> confusion and make sure they're maintained, if they should be. (Excuse
> me if that's done somewhere, but I just went to the current installation
> instructions.)
I’ve added this to the installation instructions in commit aafa0df:
Some versions of GNU tar raise a warning about “implausibly old
time stamps”. This is because all the files in the archive have
their modification time set to zero (which means January 1st,
1970.) This is done on purpose to make sure the archive content is
independent of its creation time, thus making it reproducible.
Thanks!
Ludo’.
prev parent reply other threads:[~2015-07-22 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 11:55 bug#21111: possibly bogus in binary tarball Dave Love
2015-07-22 12:27 ` Andreas Enge
2015-07-22 15:55 ` Ludovic Courtès
2015-07-22 20:26 ` Dave Love
2015-07-22 20:59 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pp3j6h9i.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21111-done@debbugs.gnu.org \
--cc=fx@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).