public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Misleading timestamps on setup-x86_64.exe
Date: Tue, 19 Mar 2019 05:18:00 -0000	[thread overview]
Message-ID: <33439c07-5fc7-e383-4892-c0285ecf810f@SystematicSw.ab.ca> (raw)
In-Reply-To: <d23fa979-bfab-5440-93e8-0a32e7518062@maxrnd.com>

On 2019-03-18 22:38, Mark Geisert wrote:
> On Mon, 18 Mar 2019 01:55:36 -0700, Jim Fehrle wrote:
>> Mark Geisert wrote:
>>> Here are mine:
>>> /c/staging ls -l Cygwin??/setup*.exe
>>> -rwxrwxr-x+ 1 Mark None 1171475 Dec 20 01:18 Cygwin32/setup-x86.exe*
>>> -rwxrwxr-x+ 1 Mark None 1224211 Dec 20 01:17 Cygwin64/setup-x86_64.exe*
>>> Check the size of your v2.895 against the last line above. If it's 
>>> different, you may not have the recent version you think.  I don't want
>>> to speculate why.
>>> How did you download?  Is there a proxy cache in the way?
>> The file length matches exactly.
>> I downloaded by clicking the link at https://cygwin.com/.  No idea about a
>> proxy server.  Is that something an ISP might set up?  I'm working from my
>> home, not an office.  Not work-related.
> Well, having the file size match means you've probably got the latest
> setup-x86_64.exe.  That argues against a proxy cache being in the way.
> FWIW the times shown for my files are the times I downloaded them from the
> Cygwin website, same way you did.  So I can't reproduce what you're seeing.
> I'm out of ideas.  Sorry :-).

With what utilities and options were the files uploaded and downloaded?
Probably depends on the sourceware.org network file server metadata which seems
consistently wacky: Cygwin time machine using Julian month Dec==10?
Possibly from building over test V2.894 on your machine then uploading via lftp
or alternatives.

$ stat mirror/x86_64/setup-x86_64.exe
  File: mirror/x86_64/setup-x86_64.exe
  Size: 1224211         Blocks: 1196       IO Block: 65536  regular file
Device: 6b8d438h/112776248d     Inode: 17451448557505386  Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (uuuuuu/   $USER)   Gid: (  545/   Users)
Access: 2018-12-17 17:56:40.000000000 -0700
Modify: 2018-10-21 10:02:14.000000000 -0600
Change: 2018-12-17 17:56:40.925576800 -0700
 Birth: 2017-12-19 23:10:28.037705900 -0700
$ wget -N -P /tmp/ https://cygwin.com/setup-x86_64.exe{,.sig}
$ stat /tmp/setup-x86_64.exe{,.sig}
  File: /tmp/setup-x86_64.exe
  Size: 1224211         Blocks: 1196       IO Block: 65536  regular file
Device: 6b8d438h/112776248d     Inode: 25614222881940454  Links: 1
Access: (0644/-rw-r--r--)  Uid: (uuuuuu/   $USER)   Gid: (  545/   Users)
Access: 2019-03-18 22:53:38.000000000 -0600
Modify: 2018-10-21 10:02:14.000000000 -0600
Change: 2019-03-18 22:53:38.784884100 -0600
 Birth: 2019-03-18 22:53:36.878740000 -0600
  File: /tmp/setup-x86_64.exe.sig
  Size: 72              Blocks: 1          IO Block: 65536  regular file
Device: 6b8d438h/112776248d     Inode: 52354345669496533  Links: 1
Access: (0644/-rw-r--r--)  Uid: (uuuuuu/   $USER)   Gid: (  545/   Users)
Access: 2019-03-18 22:53:38.000000000 -0600
Modify: 2018-10-21 10:02:34.000000000 -0600
Change: 2019-03-18 22:53:38.878670500 -0600
 Birth: 2019-03-18 22:53:38.862994200 -0600

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-03-19  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  0:28 Jim Fehrle
2019-03-19  4:39 ` Mark Geisert
2019-03-19  5:18   ` Brian Inglis [this message]
2019-03-19 18:34 ` Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2019-03-20  5:30 Jim Fehrle
2019-03-18  6:04 Jim Fehrle
2019-03-18  8:55 ` Mark Geisert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33439c07-5fc7-e383-4892-c0285ecf810f@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /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.
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).