public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Misleading timestamps on setup-x86_64.exe
Date: Tue, 19 Mar 2019 18:34:00 -0000	[thread overview]
Message-ID: <87pnqmzpa9.fsf@Rainer.invalid> (raw)
In-Reply-To: <CALrWwX8hWvZuhd2kZUh3qVuT2CcCo+xjxP2WuxQZQPs=p6Wx+Q@mail.gmail.com>	(Jim Fehrle's message of "Mon, 18 Mar 2019 17:28:40 -0700")

Jim Fehrle writes:
> The file length matches exactly.

Then check the signature as well if you're still unsure.

> 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.

You didn't tell us how exactly you downloaded the file.  If you
donwloaded it onto an already existing file (overwriting it), it may
have kept the old timestamp depending on what software you used and what
timestamp you look at.  So use a fresh directory or move the old file
away first and see if that's helping.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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

  parent reply	other threads:[~2019-03-19 18:34 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
2019-03-19 18:34 ` Achim Gratz [this message]
  -- 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=87pnqmzpa9.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).