From: Maarten Jacobs <maarten256@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Error installing/updating Cygwin on Windows 10
Date: Mon, 25 Jan 2016 21:00:00 -0000 [thread overview]
Message-ID: <BLU170-W37B2B8618ADFCC351F47959EC70@phx.gbl> (raw)
In-Reply-To: <56A58E78.7010607@cygwin.com>
Hi Larry,
My apologies - I now see the email that indicates the package was updated to address this specific issue!
Problem's solved.
Thanks,
Maarten
----------------------------------------
> Subject: Re: Error installing/updating Cygwin on Windows 10
> To: cygwin@cygwin.com
> From: reply-to-list-only-lh@cygwin.com
> Date: Sun, 24 Jan 2016 21:54:48 -0500
>
> On 1/24/2016 8:53 PM, Maarten Jacobs wrote:
>> Duncan - thanks for the suggestion!
>>
>> Larry - I'm not sure what you mean by " If you use the latest Cygwin
>> package, you won't see this error.". This error started when I installed
>> Cygwin from scratch, using the latest setup.exe from the website.
>> Presumably using the setup.exe from the website, and starting with a
>> clean install should ensure I have the "latest Cygwin package" -
>> whichever package this maye be?
>
> the Cygwin distribution is a rolling release so at any point in time,
> you're installing the latest packages, assuming you don't specify other
> available versions. But, since you installed, the Cygwin package itself has
> been updated to address the specific issue you're seeing. If you want the
> benefits of that, you should upgrade (or reinstall). If you don't, that's
> fine. But my response was as much for others that may see this thread as
> for you. In other words, regardless of whether you find Duncan's
> information helpful, others should not need to use it. If someone finds
> that's not true, the problem should be reported to the list using the
> problem reporting guidelines found at the link below:
>
> <http://cygwin.com/problems.html>
>
> --
> Larry
>
> _____________________________________________________________________
>
> A: Yes.
>> Q: Are you sure?
>>> A: Because it reverses the logical flow of conversation.
>>>> Q: Why is top posting annoying in email?
>
> --
> 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
>
--
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-01-25 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU170-W2358ECF40AEBE4116058499EC60@phx.gbl>
2016-01-24 22:51 ` FW: " Maarten Jacobs
2016-01-24 22:52 ` Duncan Roe
[not found] ` <BLU170-W72425FD134EFE7E1A072399EC60@phx.gbl>
2016-01-24 23:39 ` Duncan Roe
2016-01-25 6:42 ` Larry Hall (Cygwin)
2016-01-25 7:04 ` Maarten Jacobs
2016-01-25 9:10 ` Larry Hall (Cygwin)
2016-01-25 21:00 ` Maarten Jacobs [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=BLU170-W37B2B8618ADFCC351F47959EC70@phx.gbl \
--to=maarten256@hotmail.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).