From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Misleading timestamps on setup-x86_64.exe
Date: Mon, 18 Mar 2019 08:55:00 -0000 [thread overview]
Message-ID: <63e2fd40-7d2d-f024-5e13-6c3399b92ec1@maxrnd.com> (raw)
In-Reply-To: <CALrWwX_yeUxiP4nxJzff+dEj462ifp4AhypPc-yM10JTAMK4qA@mail.gmail.com>
Jim Fehrle wrote:
> I downloaded two copies of setup-x86_64.exe, one a year or more
> ago (v2.882) and one today (v2.895). Both of them have timestamps in my
> filesystem of 11/27/2017, which I expect is being copied from the server I
> downloaded from.
>
> It would be helpful if these timestamps reflected when those versions were
> created by Cygwin. It would give you an idea how old or new your version
> is.
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?
..mark
--
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
next prev parent reply other threads:[~2019-03-18 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 6:04 Jim Fehrle
2019-03-18 8:55 ` Mark Geisert [this message]
2019-03-19 0:28 Jim Fehrle
2019-03-19 4:39 ` Mark Geisert
2019-03-19 5:18 ` Brian Inglis
2019-03-19 18:34 ` Achim Gratz
2019-03-20 5:30 Jim Fehrle
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=63e2fd40-7d2d-f024-5e13-6c3399b92ec1@maxrnd.com \
--to=mark@maxrnd.com \
--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).