From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: wget seems to have lost executive capacity
Date: Sat, 17 Sep 2016 10:30:00 -0000 [thread overview]
Message-ID: <07faadce-f43d-0485-8044-e4c4076fd834@SystematicSw.ab.ca> (raw)
In-Reply-To: <082a812e-e192-0dd7-66ca-d3ddf09d6799@t-online.de>
On 2016-09-16 13:05, Hans-Bernhard Bröker wrote:
> Am 16.09.2016 um 15:21 schrieb Fergus:
>
>> ~> ls -al /bin/wget*
>> -rwxr-xr-x 1 Administrator None 514589 Jul 11 18:10 wget.exe*
>>
>> If the size is right,
correct for cygwin32, date/time correct for UTC+1 - BST?
better check is:
$ sha512sum /bin/wget
fc3e0e6b22c09ee60d120e10328f271dce1b575d53168746c1f1a50bdb4f047bfe03e62e5ec140d113d38b45f2cb77b78f129878d3912daae09516735e206d64 */bin/wget
> Actually, it's _not_ right. That size is off by about 25 KiB from the released binary package I have, which is from Cygwin package wget-1.18-1:
>
> -rwxr-xr-x 1 hbbro hbbro 490515 11. Jul 19:10 wget.exe
correct for cygwin64, date/time correct for UTC+2 - CET?
$ sha512sum /bin/wget
e6f28c8e4a0bb8dff5b55f3f455e988ddb581bd0d4b560e949799b53b568ccb06761e03ddd711b3d333c05982d5c70d7ed66d5dddf212a4167f9813ca60ddcef */bin/wget
> That looks like your wget.exe is corrupted.
It's not, it's fine.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
prev parent reply other threads:[~2016-09-16 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:46 Fergus
2016-09-16 14:46 ` Marco Atzeri
2016-09-16 19:05 ` Fergus
2016-09-16 19:39 ` Hans-Bernhard Bröker
2016-09-17 10:30 ` Brian Inglis [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07faadce-f43d-0485-8044-e4c4076fd834@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).