Re: setup release candidate - please test

[Peter A. Castro]

On Fri, 26 May 2017, Jon Turney wrote:


Date: Fri, 26 May 2017 18:25:17 +0100
Subject: Re: setup release candidate - please test

On 26/05/2017 16:01, Ian Lambert via cygwin wrote:

On Fri, 5/26/17, Jon Turney <> wrote:
  Subject: Re: setup release candidate - please test
  Date: Friday, May 26, 2017, 8:05 AM

  > Can you give an example of a setup command
  line containing an invalid
  > option
  which "quietly does nothing" rather than reporting
  an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


Ah, maybe I have misunderstood what you meant: I thought you meant the 
invalid option is silently ignored, but you meant that when started like 
that, an invalid option causes setup to silently do nothing.


That's because the error is being written to a non-existent console. 
Unfortunately, knowing if we've been started from a terminal or not to report 
the error appropriately is a bit of a problem.


It's been a while since I did real Win32 programming, but I seem to recall 
there were some indirect ways of determining if you had a Console 
environment, like calling GetConsoleTitle() and if it returns an error 
then you don't have a console.  Or maybe GetStdHandle() ?


If you detemine you don't have a Console, then create a pop-up dialog box 
showing the error with a dummy OK button?


I'd bet Corinna would have this kind of knowledge at her fingertips. :)

[snip]

--
--=> Peter A. Castro
Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com
"Cats are just autistic Dogs" -- Dr. Tony Attwood

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

Re: setup release candidate - please test

[Jon Turney]

On 26/05/2017 16:01, Ian Lambert via cygwin wrote:

On Fri, 5/26/17, Jon Turney <> wrote:
  Subject: Re: setup release candidate - please test
  To: "The Cygwin Mailing List" <cygwin@cygwin.com>
  Cc: "Ian Lambert" <>
  Date: Friday, May 26, 2017, 8:05 AM




  > Can you give an example of a setup command
  line containing an invalid
  > option
  which "quietly does nothing" rather than reporting
  an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


Ah, maybe I have misunderstood what you meant: I thought you meant the 
invalid option is silently ignored, but you meant that when started like 
that, an invalid option causes setup to silently do nothing.


That's because the error is being written to a non-existent console. 
Unfortunately, knowing if we've been started from a terminal or not to 
report the error appropriately is a bit of a problem.



Depending on the results of the tests suggested with wget, I

  may
  >> consider changing or removing
  the user-agent reported by cygwin setup,
  >> or providing such an option.
  >
  > This snapshot adds a
  --user-agent option, which allows the user agent
  > string to be specified.
  >
  > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
  > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe
  

Ping?
  
  > Could you let me know if this helps, or if

  you've given up, so I know
  what to do
  with these patches?
  

Sorry, I missed seeing this before. The suggestion of testing
combinations of wget, curl and lynx with a few different user agents
was more than I had time for then, but I haven't given up.

I tried the above setup 3 ways. It doesn't help.
With Firefox user agent and proxy entered
With iE user agent and proxy entered


These haven't changed so you don't need to test them.


With iE user agent and use iE settings selected

Setup does not ask for username and password.
Wget needs those and gets them from .wgetrc or .bashrc.


Oh well, thanks for testing.


2017/05/26 10:27:15 HTTP status 403 fetching http://cygwin.com/mirrors.lst


setup doesn't ask for username/password because it doesn't get a "407 
Proxy Authorization Required" response, just a "403 Forbidden".




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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On Fri, 5/26/17, Jon Turney <> wrote:
 Subject: Re: setup release candidate - please test
 To: "The Cygwin Mailing List" <cygwin@cygwin.com>
 Cc: "Ian Lambert" <>
 Date: Friday, May 26, 2017, 8:05 AM
 
 On 17/05/2017 20:38, Jon Turney
 wrote:
 > On 16/05/2017 15:06, Jon Turney wrote:
 >> I don't know why unrecognized
 options aren't fatal errors.
 > 
 > So, I might have been misled by my low
 opinion of setup here:
 > 
 >> $ ./setup-x86_64
 --user-agent=anything
 >>
 >> Error during option processing.
 > [...]
 

Apparently there is a difference in response when running 
setup from a desktop icon versus command line.
You were not misled. Another detail is I am also using
--no-admin (but that doesn't seem to matter in this case).



 > Can you give an example of a setup command
 line containing an invalid 
 > option
 which "quietly does nothing" rather than reporting
 an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


> Depending on the results of the tests suggested with wget, I
 may
 >> consider changing or removing
 the user-agent reported by cygwin setup,
 >> or providing such an option.
 > 
 > This snapshot adds a
 --user-agent option, which allows the user agent 
 > string to be specified.
 > 
 > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
 > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe
 
> Ping?
 
 > Could you let me know if this helps, or if
 you've given up, so I know 
 what to do
 with these patches?
 

Sorry, I missed seeing this before. The suggestion of testing 
combinations of wget, curl and lynx with a few different user agents
was more than I had time for then, but I haven't given up.

I tried the above setup 3 ways. It doesn't help. 
With Firefox user agent and proxy entered
With iE user agent and proxy entered
With iE user agent and use iE settings selected

Setup does not ask for username and password.
Wget needs those and gets them from .wgetrc or .bashrc.

Logs are below. The first 2 are very similar. 3rd is a little different.
I also re-verified wget still works with the same 2 user agents (or no user 
agent).


$ cat setup.log.full-proxy-ff-ua ; echo ; cat setup.log.full-proxy-ie-ua ; echo 
; cat setup.log.full-iesettings-ie-ua 
2017/05/26 10:23:15 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:23:15 User has NO backup/restore rights
2017/05/26 10:23:15 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:23:15 Could not open Service control manager
2017/05/26 10:23:22 source: network install
2017/05/26 10:23:25 root: E:\cygwin64-3 user
2017/05/26 10:23:27 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:23:30 net: Proxy
Cached mirror list unavailable
Defaulting to empty mirror list
2017/05/26 10:23:32 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:23:32 mbox note: Unable to get setup from 
<http://mirrors.kernel.org/sourceware/cygwin/>
INSTALLED.DB version 3
2017/05/26 10:23:36 Ending cygwin install

2017/05/26 10:25:28 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:25:28 User has NO backup/restore rights
2017/05/26 10:25:28 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:25:28 Could not open Service control manager
2017/05/26 10:25:31 source: network install
2017/05/26 10:25:32 root: E:\cygwin64-3 user
2017/05/26 10:25:33 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:25:39 net: Proxy
Cached mirror list unavailable
Defaulting to empty mirror list
2017/05/26 10:25:40 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:25:40 mbox note: Unable to get setup from 
<http://mirrors.kernel.org/sourceware/cygwin/>
INSTALLED.DB version 3
2017/05/26 10:25:43 Ending cygwin install

2017/05/26 10:27:07 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:27:07 User has NO backup/restore rights
2017/05/26 10:27:07 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:27:07 Could not open Service control manager
2017/05/26 10:27:10 source: network install
2017/05/26 10:27:11 root: E:\cygwin64-3 user
2017/05/26 10:27:12 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:27:15 net: IE5
Cached mirror list unavailable
2017/05/26 10:27:15 HTTP status 403 fetching http://cygwin.com/mirrors.lst
Defaulting to empty mirror list
2017/05/26 10:27:16 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:27:16 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz.sig
2017/05/26 10:27:16 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz
2017/05/26 10:27:

Re: setup release candidate - please test

[Jon Turney]

On 17/05/2017 20:38, Jon Turney wrote:

On 16/05/2017 15:06, Jon Turney wrote:

I don't know why unrecognized options aren't fatal errors.


So, I might have been misled by my low opinion of setup here:


$ ./setup-x86_64 --user-agent=anything

Error during option processing.

[...]

Can you give an example of a setup command line containing an invalid 
option which "quietly does nothing" rather than reporting an error?



Depending on the results of the tests suggested with wget, I may
consider changing or removing the user-agent reported by cygwin setup,
or providing such an option.


This snapshot adds a --user-agent option, which allows the user agent 
string to be specified.


https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe


Ping?

Could you let me know if this helps, or if you've given up, so I know 
what to do with these patches?


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

Re: setup release candidate - please test

[Jon Turney]

On 16/05/2017 15:06, Jon Turney wrote:

On 16/05/2017 14:45, Ian Lambert wrote:

On May 16, 2017 6:52:17 AM EDT, Jon Turney <> wrote:

On 15/05/2017 22:11, Brian Inglis wrote:

On 2017-05-15 14:42, Ian Lambert via cygwin wrote:

On Mon, 5/15/17, Jon Turney wrote:
 On 15/05/2017 16:29, Ian Lambert via cygwin wrote:

When I try --user-agent=anything with setup, it quietly does nothing.


I'm not sure if you missed or ignored that the wget option is referred
to here.


It isn't an option, like proxy username and password aren't?


Correct, it isn't an option.  setup --help will confirm this for you.

I don't know why unrecognized options aren't fatal errors.


So, I might have been misled by my low opinion of setup here:


$ ./setup-x86_64 --user-agent=anything

Error during option processing.

[...]

Can you give an example of a setup command line containing an invalid 
option which "quietly does nothing" rather than reporting an error?



Depending on the results of the tests suggested with wget, I may
consider changing or removing the user-agent reported by cygwin setup,
or providing such an option.


This snapshot adds a --user-agent option, which allows the user agent 
string to be specified.


https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe



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

Re: setup release candidate - please test

[Brian Inglis]

On 2017-05-16 11:08, Ian Lambert wrote:
> On Tue, May 16, 2017, 12:55 PM Brian Inglis wrote:
> Except not using the option, this is the only one I found that works
> here with wget:
> --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64;Trident/7.0; rv:11.0) like 
> Gecko"
> (Note: proxy_user and proxy_password, as well as  are also being set 
> in .wgetrc and .bashrc and https_proxy, http_proxy and ftp_proxy are 
> additionally being set in .bashrc)
>> What about just a plain --user-agent=Mozilla/4.0?
>> That and null are the only values I have hard wired into scripts
>> where there were problems.
>> With your current browser, you can go to
>>  http://www.askapache.com/online-tools/whoami/
>> to find out your current headers.
> No. The plain one does not work. Only the long user agent above, not
> using --user-agent..., or
> --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 
> Firefox/31.0"
> work with wget here. Those 2 are seen in that tool for iE or Firefox
> browsers.

Couple more suggestions to try to see if they can get thru the proxy:

$ curl -J|-O [--user-agent ...] https://cygwin.com/setup-x86_64.exe
$ lynx -source [-useragent ...] https://cygwin.com/setup-x86_64.exe >
setup-x86_64.exe

which might give developers hints how setup could be changed to work.

>From testing curl uses minimal extra headers, wget a few, and lynx
TUI most like GUI products:

User-Agent: curl/7.54.0  Wget/1.19.1 (cygwin)  Lynx/2.8.7rel.1
libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/1.0.2k
Accept: */*  */*   text/html, text/plain, 
text/css, text/sgml,
*/*;q=0.01
Accept-Encoding: identity  gzip, bzip2
Connection:  Keep-Alive
Accept-Language:   en

I don't use emacs or I would have tested it, so perhaps someone
who lives in it could; I find vim's "browser" less than useful,
although I can otherwise live in it, as others can with emacs:
so many scripts and plugins, so little time to try them and
tweak them.

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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On Tue, 5/16/17, Brian Inglis <> wrote:

 Subject: Re: setup release candidate - please test
 To: cygwin@cygwin.com
 Date: Tuesday, May 16, 2017, 12:55 PM
 
 >
 Except not using the option, this is the only one I found
 that works here with wget:
 >
 --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64;
 Trident/7.0; rv:11.0) like Gecko"
 >
 (Note: proxy_user and proxy_password, as well as  are also
 being set
 > in .wgetrc and .bashrc and
 https_proxy, http_proxy and ftp_proxy are
 > additionally being set in .bashrc)
 
 What about just a plain
 --user-agent=Mozilla/4.0?
 That and null are
 the only values I have hard wired into scripts where
 there were problems.
 
 With your current browser, you can go to
     http://www.askapache.com/online-tools/whoami/
 to find out your current headers.

= = = 

No. The plain one does not work. Only the long user agent above, 
not using --user-agent..., 
or
--user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 
Firefox/31.0"

work with wget here. Those 2 are seen in that tool
for iE or Firefox browsers.

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

Re: setup release candidate - please test

[Brian Inglis]

On 2017-05-16 09:18, Ian Lambert via cygwin wrote:
>> Does it work if you try user agent combos of 
>> {Cygwin-Setup,CygwinSetup}/{2.878-3,2.878}?
> None of these work with wget.
>>> You might also try with no user-agent (wget --user-agent="" apparently)
> This also does not work with wget.
>>> Depending on the results of the tests suggested with wget, I may
>>> consider changing or removing the user-agent reported by cygwin
>>> setup, or providing such an option.
> Except not using the option, this is the only one I found that works here 
> with wget:
> --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like 
> Gecko"
> (Note: proxy_user and proxy_password, as well as  are also being set
> in .wgetrc and .bashrc and https_proxy, http_proxy and ftp_proxy are
> additionally being set in .bashrc)

What about just a plain --user-agent=Mozilla/4.0?
That and null are the only values I have hard wired into scripts where
there were problems.

With your current browser, you can go to
http://www.askapache.com/online-tools/whoami/
to find out your current headers.

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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

 >
 >>> Does it work if you try user agent
 combos of
 >>>
 {Cygwin-Setup,CygwinSetup}/{2.878-3,2.878}?

None of these work with wget.

 >>
 >> You might
 also try with no user-agent (wget --user-agent=""
 apparently)

This also does not work with wget.


 
>  Depending on the results of
 the tests suggested with wget, I may 
 consider changing or removing the user-agent
 reported by cygwin setup, 
 or providing such
 an option.
 

Except not using the option, this is the only one I found that works here with 
wget:

--user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like 
Gecko"

(Note: proxy_user and proxy_password, as well as  are also being set in .wgetrc 
and .bashrc
and https_proxy, http_proxy and ftp_proxy are additionally being set in .bashrc)

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

Re: setup release candidate - please test

[Jon Turney]

On 16/05/2017 14:45, Ian Lambert wrote:

On May 16, 2017 6:52:17 AM EDT, Jon Turney <> wrote:

On 15/05/2017 22:11, Brian Inglis wrote:

On 2017-05-15 14:42, Ian Lambert via cygwin wrote:

On Mon, 5/15/17, Jon Turney wrote:
 On 15/05/2017 16:29, Ian Lambert via cygwin wrote:

On Sun, 5/14/17, Jon Turney wrote:

I think that "403 forbidden" means that this request is prohibited
by the configuration of the proxy, so really you need to contact
whoever administers it.

The proxy admins have no interest in helping with this. :)


My point was more that your administrator has configured things to
prevent what you are trying to do (however foolish trying to control
access by user-agent might be)



Does it work if you try user agent combos of
{Cygwin-Setup,CygwinSetup}/{2.878-3,2.878}?


You might also try with no user-agent (wget --user-agent="" apparently)


When I try --user-agent=anything with setup, it quietly does nothing.


I'm not sure if you missed or ignored that the wget option is referred 
to here.



It isn't an option, like proxy username and password aren't?


Correct, it isn't an option.  setup --help will confirm this for you.

I don't know why unrecognized options aren't fatal errors.

Depending on the results of the tests suggested with wget, I may 
consider changing or removing the user-agent reported by cygwin setup, 
or providing such an option.



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

Re: setup release candidate - please test

[Jon Turney]

On 15/05/2017 22:11, Brian Inglis wrote:

On 2017-05-15 14:42, Ian Lambert via cygwin wrote:

On Mon, 5/15/17, Jon Turney wrote:
 On 15/05/2017 16:29, Ian Lambert via cygwin wrote:

On Sun, 5/14/17, Jon Turney wrote:

I think that "403 forbidden" means that this request is prohibited
by the configuration of the proxy, so really you need to contact
whoever administers it.

The proxy admins have no interest in helping with this. :)


My point was more that your administrator has configured things to 
prevent what you are trying to do (however foolish trying to control 
access by user-agent might be)




Indeed, user-agent of Cygwin Setup is a problem:

$ wget --user-agent="Cygwin Setup" 
https://cygwin.com/setup/setup-2.878.x86_64.exe
--2017-05-15 16:33:25--  https://cygwin.com/setup/setup-2.878.x86_64.exe
Resolving our.glorious.proxy... pr.ox.yi.p
Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
Proxy tunneling failed: ForbiddenUnable to establish SSL connection.

$ wget  https://cygwin.com/setup/setup-2.878.x86_64.exe
--2017-05-15 16:33:40--  https://cygwin.com/setup/setup-2.878.x86_64.exe
Resolving our.glorious.proxy... pr.ox.yi.p
Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
Proxy request sent, awaiting response... 200 OK
Length: 907283 (886K) [application/octet-stream]
Saving to: ‘setup-2.878.x86_64.exe’

setup-2.878.x86_64.exe  
100%[>]
 886.02K   764KB/sin 1.2s

2017-05-15 16:33:41 (764 KB/s) - ‘setup-2.878.x86_64.exe’ saved [907283/907283]


Does it work if you try user agent combos of
{Cygwin-Setup,CygwinSetup}/{2.878-3,2.878}?



You might also try with no user-agent (wget --user-agent="" apparently)

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

Re: setup release candidate - please test

[Brian Inglis]

On 2017-05-15 14:42, Ian Lambert via cygwin wrote:
> On Mon, 5/15/17, Jon Turney wrote:
>  On 15/05/2017 16:29, Ian Lambert via cygwin wrote:
>> On Sun, 5/14/17, Jon Turney wrote:
> I think that "403 forbidden" means that this request is prohibited
> by the configuration of the proxy, so really you need to contact 
> whoever administers it.
>  
> Since curl/wget works to fetch the same URLs through that proxy, it 
> might be that the user-agent is disallowed, possibly you could test
> this by attempting trying with --user-agent="Cygwin Setup"? 
> 
> The proxy admins have no interest in helping with this. :)
> 
> Indeed, user-agent of Cygwin Setup is a problem:
> 
> $ wget --user-agent="Cygwin Setup" 
> https://cygwin.com/setup/setup-2.878.x86_64.exe
> --2017-05-15 16:33:25--  https://cygwin.com/setup/setup-2.878.x86_64.exe
> Resolving our.glorious.proxy... pr.ox.yi.p
> Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
> Proxy tunneling failed: ForbiddenUnable to establish SSL connection.
> 
> $ wget  https://cygwin.com/setup/setup-2.878.x86_64.exe
> --2017-05-15 16:33:40--  https://cygwin.com/setup/setup-2.878.x86_64.exe
> Resolving our.glorious.proxy... pr.ox.yi.p
> Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
> Proxy request sent, awaiting response... 200 OK
> Length: 907283 (886K) [application/octet-stream]
> Saving to: ‘setup-2.878.x86_64.exe’
> 
> setup-2.878.x86_64.exe  
> 100%[>]
>  886.02K   764KB/sin 1.2s
> 
> 2017-05-15 16:33:41 (764 KB/s) - ‘setup-2.878.x86_64.exe’ saved 
> [907283/907283]

Does it work if you try user agent combos of
{Cygwin-Setup,CygwinSetup}/{2.878-3,2.878}?

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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On Mon, 5/15/17, Jon Turney <> wrote:

 Subject: Re: setup release candidate - please test
 To: "The Cygwin Mailing List" <cygwin@cygwin.com>
 Cc: "Ian Lambert" <>
 Date: Monday, May 15, 2017, 12:12 PM
 
 On 15/05/2017 16:29, Ian Lambert
 via cygwin wrote:
 >
 
 > On Sun, 5/14/17, Jon Turney <>
 wrote:
 [...]
 
 I think that "403
 forbidden" means that this request is prohibited by 
 the configuration of the proxy, so really you
 need to contact whoever 
 administers it.
 
 Since curl/wget works to fetch
 the same URLs through that proxy, it 
 might
 be that the user-agent is disallowed, possibly you could
 test this 
 by attempting trying with
 --user-agent="Cygwin Setup"?

= = =

The proxy admins have no interest in helping with this. :)

Indeed, user-agent of Cygwin Setup is a problem:

$ wget --user-agent="Cygwin Setup" 
https://cygwin.com/setup/setup-2.878.x86_64.exe
--2017-05-15 16:33:25--  https://cygwin.com/setup/setup-2.878.x86_64.exe
Resolving our.glorious.proxy... pr.ox.yi.p
Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
Proxy tunneling failed: ForbiddenUnable to establish SSL connection.

$ wget  https://cygwin.com/setup/setup-2.878.x86_64.exe
--2017-05-15 16:33:40--  https://cygwin.com/setup/setup-2.878.x86_64.exe
Resolving our.glorious.proxy... pr.ox.yi.p
Connecting to our.glorious.proxy|pr.ox.yi.p|:port... connected.
Proxy request sent, awaiting response... 200 OK
Length: 907283 (886K) [application/octet-stream]
Saving to: ‘setup-2.878.x86_64.exe’

setup-2.878.x86_64.exe  
100%[>]
 886.02K   764KB/sin 1.2s

2017-05-15 16:33:41 (764 KB/s) - ‘setup-2.878.x86_64.exe’ saved [907283/907283]

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

Re: setup release candidate - please test

[Jon Turney]

On 15/05/2017 16:29, Ian Lambert via cygwin wrote:


On Sun, 5/14/17, Jon Turney <> wrote:

[...]


 However, since I had the code open in my
 editor, I took look at this...

 Please test.

 https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86.exe
 https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86_64.exe

 [1]
 
https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=shortlog;h=refs/heads/ntlm-proxy-debugging
= = = =

I didn't expect it to work, but didn't hurt to try it. Thanks for looking at it.


Thanks for testing.


Behavior is still the same - no prompt for a password, and fails to get setup 
(popup message).
I tried both use IE settings, and Use HTTP/FTP proxy with proxy name and port.
Logs are as follows:

$ cat setup.log.full-ie

[...]

Fetching URL: http://cygwin.com/mirrors.lst
2017/05/15 11:17:12 HTTP status 403 fetching http://cygwin.com/mirrors.lst


I think that "403 forbidden" means that this request is prohibited by 
the configuration of the proxy, so really you need to contact whoever 
administers it.


Since curl/wget works to fetch the same URLs through that proxy, it 
might be that the user-agent is disallowed, possibly you could test this 
by attempting trying with --user-agent="Cygwin Setup"?



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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On Sun, 5/14/17, Jon Turney <> wrote:

 Subject: Re: setup release candidate - please test
 To: "The Cygwin Mailing List" <cygwin@cygwin.com>
 Cc: "Ian Lambert" <>
 Date: Sunday, May 14, 2017, 9:53 AM
 
 On 08/05/2017 17:19, Ian Lambert
 via cygwin wrote:
 > On May 8, 2017
 7:06:31 AM EDT, Jon Turney  wrote:
 >
 > As reported before, _64 still can't
 make it through my location's
 >
 apparently unusual proxy, although cygwin's wget given
 proxy and
 > password still can. Install
 with local mirror option works ok still.
 > Windows 7 Enterprise SP1.
 
 It's unsurprising that
 2.878 didn't fix this, as it didn't contain any 
 changes intended to.
 
 However, since I had the code open in my
 editor, I took look at this...
 
 Please test.
 
 https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86.exe
 https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86_64.exe
 
 [1] 
 
https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=shortlog;h=refs/heads/ntlm-proxy-debugging
= = = = 

I didn't expect it to work, but didn't hurt to try it. Thanks for looking at it.

Behavior is still the same - no prompt for a password, and fails to get setup 
(popup message).
I tried both use IE settings, and Use HTTP/FTP proxy with proxy name and port.
Logs are as follows:

$ cat setup.log.full-ie
2017/05/15 11:17:03 Starting cygwin install, version 2.878-3-gf41e2e
2017/05/15 11:17:03 User has NO backup/restore rights
2017/05/15 11:17:03 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/15 11:17:03 Could not open Service control manager
2017/05/15 11:17:06 source: network install
2017/05/15 11:17:06 root: E:\cygwin64-3 user
2017/05/15 11:17:07 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/15 11:17:11 net: IE5
Cached mirror list unavailable
Fetching URL: http://cygwin.com/mirrors.lst
2017/05/15 11:17:12 HTTP status 403 fetching http://cygwin.com/mirrors.lst
Defaulting to empty mirror list
2017/05/15 11:17:13 site: http://mirrors.kernel.org/sourceware/cygwin/
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz.sig
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2.sig
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini.sig
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
2017/05/15 11:17:13 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
2017/05/15 11:17:13 mbox note: Unable to get setup from 
<http://mirrors.kernel.org/sourceware/cygwin/>
INSTALLED.DB version 3
2017/05/15 11:17:19 Ending cygwin install



$ cat setup.log.full-proxy
2017/05/15 11:11:17 Starting cygwin install, version 2.878-3-gf41e2e
2017/05/15 11:11:17 User has NO backup/restore rights
2017/05/15 11:11:17 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/15 11:11:17 Could not open Service control manager
2017/05/15 11:11:23 source: network install
2017/05/15 11:11:25 root: E:\cygwin64-3 user
2017/05/15 11:11:26 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/15 11:11:41 net: Proxy
Cached mirror list unavailable
Fetching URL: http://cygwin.com/mirrors.lst
Defaulting to empty mirror list
2017/05/15 11:13:38 net: Proxy
2017/05/15 11:13:39 site: http://mirrors.kernel.org/sourceware/cygwin/
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini.sig
Fetching URL: http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
2017/05/15 11:13:39 mbox note: Unable to get setup from 
<http://mirrors.kernel.org/sourceware/cygwin/>
INSTALLED.DB version 3
2017/05/15 11:13:44 Ending cygwin install



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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 17:19, Ian Lambert via cygwin wrote:

On May 8, 2017 7:06:31 AM EDT, Jon Turney  wrote:

As reported before, _64 still can't make it through my location's
apparently unusual proxy, although cygwin's wget given proxy and
password still can. Install with local mirror option works ok still.
Windows 7 Enterprise SP1.


It's unsurprising that 2.878 didn't fix this, as it didn't contain any 
changes intended to.


However, since I had the code open in my editor, I took look at this...

This is pretty difficult to investigate without access to a (working) 
NTLM proxy (getting even ntlm_fake_auth working in squid is beyond me...).


Nevertheless, testing with that did suggest something, so I built a 
snapshot (See [1] for source) which tries something different, and does 
a bit more logging, so setup.log.full might shed a bit more light on why 
this doesn't work.


Please test.

https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86.exe
https://cygwin.com/setup/setup-2.878-3-gf41e2e.x86_64.exe

[1] 
https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=shortlog;h=refs/heads/ntlm-proxy-debugging


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

Re: setup release candidate - please test

[Jim Reisert AD1C]

Symantec Endpoint Protection v. 12.1.6  did not like this file, but I
was able to exclude it.

-- 
Jim Reisert AD1C, , http://www.ad1c.us

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

Re: setup release candidate - please test

[Andrey Repin]

Greetings, Jon Turney!

> On 08/05/2017 17:27, Brian Inglis wrote:
>>
>> wget download no longer sets x bits and won't run from Explorer,
>> cygstart, or bash:

> No longer?  I don't think wget ever did this.

>> $ cygstart ./setup-2.878.x86_64
>> Unable to start 'setup-2.878.x86_64.exe': The operating system denied access 
>> to the specified file.
>> $ cygstart ./setup-2.878.x86_64.exe
>> Unable to start 'setup-2.878.x86_64.exe': The operating system denied access 
>> to the specified file.
>> $ ./setup-2.878.x86_64
>> -bash: ./setup-2.878.x86_64: Permission denied
>> $ ./setup-2.878.x86_64.exe
>> -bash: ./setup-2.878.x86_64.exe: Permission denied
>>
>> - requires chmod +x to run.

It never did by itself, but if you download to a location with
windows-controlled ACL, the executable bit will be set by OS.


-- 
With best regards,
Andrey Repin
Tuesday, May 9, 2017 20:52:27

Sorry for my terrible english...


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

Re: setup release candidate - please test

[Brian Inglis]

On 2017-05-09 03:57, Jon Turney wrote:
> On 08/05/2017 17:27, Brian Inglis wrote:
>> wget download no longer sets x bits and won't run from Explorer, 
>> cygstart, or bash:
> No longer?  I don't think wget ever did this.
>> $ cygstart ./setup-2.878.x86_64
>> Unable to start 'setup-2.878.x86_64.exe': The operating system denied access 
>> to the specified file.
>> $ cygstart ./setup-2.878.x86_64.exe
>> Unable to start 'setup-2.878.x86_64.exe': The operating system denied access 
>> to the specified file.
>> $ ./setup-2.878.x86_64
>> -bash: ./setup-2.878.x86_64: Permission denied
>> $ ./setup-2.878.x86_64.exe
>> -bash: ./setup-2.878.x86_64.exe: Permission denied
>> - requires chmod +x to run.

Never had to chmod -x setup in my download, check, launch script 
until now - it used to just check it was -x and complain if not, 
which it did this time, pre-fix! 
Did not require that on my last (wget -N) download of the current 
setup release, but now does. 
Consistent across directories, Cygwin, and Windows DACLs. 
Could be Windows, Cygwin, or wget change - not worried about cause.

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

Re: setup release candidate - please test

[Eliot Moss]

On 5/9/2017 6:03 AM, Jon Turney wrote:

On 08/05/2017 14:33, Eliot Moss wrote:

On 5/8/2017 7:06 AM, Jon Turney wrote:


A setup release candidate is available at:

   https://cygwin.com/setup/setup-2.878.x86.exe
   https://cygwin.com/setup/setup-2.878.x86_64.exe


Both worked flawlessly for me.  I run Windows 10,
Creator Update (most recent release AFAIK).

One difference from before is that I get a Windows
Defender SmartScreen pop-up.  I have to click the
"More info" option and then a "Run anyway" button
appears, allowing me to run the setup program.

AFAICT, this happens only the *first* time I run
the setup program.  Thereafter, WIndows Defender
does not complain.


Thanks for testing.

Is Windows 10 1703 more picky about letting you run unsigned executables?


I think so - I don't recall needing to do this with setup ever before.


As discussed previously, the problems with getting setup signed are logistical 
rather than technical.


It's not a huge deal, particularly since it happens only the
first time I run setup.  I suppose the concern would be users
who don't figure out the right clicks or who are suspicious
of doing that, and automated installs.

Regards - EM

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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 14:33, Eliot Moss wrote:

On 5/8/2017 7:06 AM, Jon Turney wrote:


A setup release candidate is available at:

   https://cygwin.com/setup/setup-2.878.x86.exe
   https://cygwin.com/setup/setup-2.878.x86_64.exe


Both worked flawlessly for me.  I run Windows 10,
Creator Update (most recent release AFAIK).

One difference from before is that I get a Windows
Defender SmartScreen pop-up.  I have to click the
"More info" option and then a "Run anyway" button
appears, allowing me to run the setup program.

AFAICT, this happens only the *first* time I run
the setup program.  Thereafter, WIndows Defender
does not complain.


Thanks for testing.

Is Windows 10 1703 more picky about letting you run unsigned executables?

As discussed previously, the problems with getting setup signed are 
logistical rather than technical.


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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 12:38, Steven Penny via cygwin wrote:

On Mon, 8 May 2017 12:06:31, Jon Turney wrote:



Looks good, but I still hate the last screen. The "Create Icons" screen.


Thanks for testing.


We should be able to add the icon preference to this list.


'We' take patches.


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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 17:27, Brian Inglis wrote:


wget download no longer sets x bits and won't run from Explorer,
cygstart, or bash:


No longer?  I don't think wget ever did this.


$ cygstart ./setup-2.878.x86_64
Unable to start 'setup-2.878.x86_64.exe': The operating system denied access to 
the specified file.
$ cygstart ./setup-2.878.x86_64.exe
Unable to start 'setup-2.878.x86_64.exe': The operating system denied access to 
the specified file.
$ ./setup-2.878.x86_64
-bash: ./setup-2.878.x86_64: Permission denied
$ ./setup-2.878.x86_64.exe
-bash: ./setup-2.878.x86_64.exe: Permission denied

- requires chmod +x to run.


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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 19:26, Peter A. Castro wrote:

On Mon, 8 May 2017, Jon Turney wrote:

[...]


- Add --allow-unsupported-windows option
Don't check the windows version.


Huzzah!!  Thanks for this!!


No problem.


The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time
machine circa) should be given with --site or via the GUI.

- Remove support for some long-obsolete setup.ini syntax (omitted
version:, omitted size and checksum, various undocumented tokens)


Can you tell me what Setup will do if it encounters one of these
"obsolete" setup.ini?  Throw an error?  Ignore the omission (how?)?
Ignore the entire package entry??  Allow the user to continue anyway?


I'm afraid I'd have to test it to be sure, but I think that setup will 
report a syntax error and attempt to continue processing the setup.ini file.


I suspect the package will not be in very useful state lacking version 
or archive information.


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

Re: setup release candidate - please test

[Peter A. Castro]

On Mon, 8 May 2017, Jon Turney wrote:


Date: Mon, 8 May 2017 12:06:31 +0100
From: Jon Turney
To: The Cygwin Mailing List
Subject: setup release candidate - please test


Greetings, Jon,


A setup release candidate is available at:

 https://cygwin.com/setup/setup-2.878.x86.exe
 https://cygwin.com/setup/setup-2.878.x86_64.exe


Huzzah!!

Got some questions below:

Since this changes the way we download files, I think this can use some wider 
testing before release.


Please test and give feedback to cygwin@cygwin.com. If no regressions are 
discovered in the next few days, it will be promoted to release.



Changes compared to 2.877:

- "Direct Connection" now uses the WinINet API to fetch URLs.

This enables HTTPS and FTPS protocol support, and caching of mirrors.lst and 
setup.ini.


The existing, hand-built URL fetching, which only supports HTTP and FTP, is 
still available by choosing "Direct (legacy)".


- Fixes to "Use Internet Explorer Proxy Settings" mode

Progress is now reported for downloads.

Unwanted caching in "Temporary Internet Files" of package archives has been 
fixed.

(Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00403.html)

A bug causing a long delay before downloading setup.ini from package 
repositories without a compressed setup.ini has been fixed.


- Add --allow-unsupported-windows option
Don't check the windows version.


Huzzah!!  Thanks for this!!

The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time machine 
circa) should be given with --site or via the GUI.


- Remove support for some long-obsolete setup.ini syntax (omitted version:, 
omitted size and checksum, various undocumented tokens)


Can you tell me what Setup will do if it encounters one of these 
"obsolete" setup.ini?  Throw an error?  Ignore the omission (how?)? 
Ignore the entire package entry??  Allow the user to continue anyway?


I'm thinking that I may need to go update some of the older circa to 
"conform" to the new normal (if possible...some circa of setup.ini were 
terribly broken and never really worked to begin with!) so customers can 
use the latest Setup with the Time Machine.


Thanks for all the great work, btw!


- Remove cruft

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


--
--=> Peter A. Castro
Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com
"Cats are just autistic Dogs" -- Dr. Tony Attwood

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

Re: setup release candidate - please test

[Eric Fahlgren]

Henry S. Thompson wrote:
> Dave Caswell via cygwin writes:
>
> > Execution blocked by Windows 10 anti-virus.  (Microsoft Security
> > Essentials.)
>
> Not in my case, all went smoothly, around 40 packages updated.

Likewise, everything worked fine for me on our Win 10 x64 test box,
running setup 64, updated maybe 10 packages.  Similar results on a
Win7 x64 machine.  Both machines are running Microsoft Security
Essentials.

Eric

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

Re: setup release candidate - please test

[Brian Inglis]

On 2017-05-08 05:11, Dave Caswell via cygwin wrote:
> Execution blocked by Windows 10 anti-virus.(Microsoft Security 
> Essentials.)
> On Mon, May 8, 2017 at 5:10 AM, Dave Caswell  wrote:
>> Execution blocked by Windows 10 anti-virus.(Microsoft Security
>> Essentials.)
>> On Mon, May 8, 2017 at 5:06 AM, Jon Turney 
>> wrote:
>>> A setup release candidate is available at:
>>>   https://cygwin.com/setup/setup-2.878.x86.exe
>>>   https://cygwin.com/setup/setup-2.878.x86_64.exe
>>> Since this changes the way we download files, I think this can
>>> use some wider testing before release.
>>> Please test and give feedback to cygwin@cygwin.com. If no
>>> regressions are discovered in the next few days, it will be
>>> promoted to release.
>>> Changes compared to 2.877:
>>> - "Direct Connection" now uses the WinINet API to fetch URLs.
>>> This enables HTTPS and FTPS protocol support, and caching of
>>> mirrors.lst and setup.ini.
>>> The existing, hand-built URL fetching, which only supports HTTP
>>> and FTP, is still available by choosing "Direct (legacy)".
>>> - Fixes to "Use Internet Explorer Proxy Settings" mode
>>> Progress is now reported for downloads.
>>> Unwanted caching in "Temporary Internet Files" of package
>>> archives has been fixed.
>>> (Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00403.html)
>>> A bug causing a long delay before downloading setup.ini from
>>> package repositories without a compressed setup.ini has been
>>> fixed.
>>> - Add --allow-unsupported-windows option
>>> Don't check the windows version.
>>> The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time
>>> machine circa) should be given with --site or via the GUI.
>>> - Remove support for some long-obsolete setup.ini syntax
>>> (omitted version:, omitted size and checksum, various
>>> undocumented tokens)
>>> - Remove cruft

$ *cmd /c ver*
Microsoft Windows [Version 10.0.14393]
$ *uname -srvmo*
CYGWIN_NT-10.0 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin

Firefox download gives W10 Windows Defender Run warning 
"from an unknown publisher" and [Don't Run] button - 
/More info/ link also displays [Run Anyway] button - runs okay.

wget download no longer sets x bits and won't run from Explorer, 
cygstart, or bash:

$ cygstart ./setup-2.878.x86_64
Unable to start 'setup-2.878.x86_64.exe': The operating system denied access to 
the specified file.
$ cygstart ./setup-2.878.x86_64.exe
Unable to start 'setup-2.878.x86_64.exe': The operating system denied access to 
the specified file.
$ ./setup-2.878.x86_64
-bash: ./setup-2.878.x86_64: Permission denied
$ ./setup-2.878.x86_64.exe
-bash: ./setup-2.878.x86_64.exe: Permission denied

- requires chmod +x to run.


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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On May 8, 2017 7:06:31 AM EDT, Jon Turney  wrote:
>
>A setup release candidate is available at:
>
>   https://cygwin.com/setup/setup-2.878.x86.exe
>   https://cygwin.com/setup/setup-2.878.x86_64.exe
>

As reported before, _64 still can't make it through my location's apparently 
unusual proxy, although cygwin's wget given proxy and password still can. 
Install with local mirror option works ok still. Windos 7 Enterprise SP1.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: setup release candidate - please test

[Eliot Moss]

On 5/8/2017 7:06 AM, Jon Turney wrote:


A setup release candidate is available at:

   https://cygwin.com/setup/setup-2.878.x86.exe
   https://cygwin.com/setup/setup-2.878.x86_64.exe


Both worked flawlessly for me.  I run Windows 10,
Creator Update (most recent release AFAIK).

One difference from before is that I get a Windows
Defender SmartScreen pop-up.  I have to click the
"More info" option and then a "Run anyway" button
appears, allowing me to run the setup program.

AFAICT, this happens only the *first* time I run
the setup program.  Thereafter, WIndows Defender
does not complain.

Regards - Eliot

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

Re: setup release candidate - please test

[Henry S. Thompson]

Dave Caswell via cygwin writes:

> Execution blocked by Windows 10 anti-virus.  (Microsoft Security
> Essentials.)

Not in my case, all went smoothly, around 40 packages updated.

ht
-- 
   Henry S. Thompson, School of Informatics, University of Edinburgh
  10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk
   URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

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

Re: setup release candidate - please test

[Jon Turney]

On 08/05/2017 12:11, Dave Caswell via cygwin wrote:

Execution blocked by Windows 10 anti-virus.(Microsoft Security Essentials.)

On Mon, May 8, 2017 at 5:10 AM, Dave Caswell  wrote:

Execution blocked by Windows 10 anti-virus.(Microsoft Security
Essentials.)


Thanks for the report.

These files were built in a fresh Fedora Linux VM created for this 
purpose, so I think they are pretty unlikely to be compromised.


Can you provide some more details, e.g. which file you tried to execute 
(x86 or x86_64)?  What reason MSE gives for blocking execution?



On Mon, May 8, 2017 at 5:06 AM, Jon Turney
wrote:


A setup release candidate is available at:

  https://cygwin.com/setup/setup-2.878.x86.exe
  https://cygwin.com/setup/setup-2.878.x86_64.exe


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

Re: setup release candidate - please test

[Steven Penny via cygwin]

On Mon, 8 May 2017 12:06:31, Jon Turney wrote:


A setup release candidate is available at:

   https://cygwin.com/setup/setup-2.878.x86.exe
   https://cygwin.com/setup/setup-2.878.x86_64.exe

Since this changes the way we download files, I think this can use some 
wider testing before release.


Please test and give feedback to cygwin@cygwin.com. If no regressions 
are discovered in the next few days, it will be promoted to release.


Looks good, but I still hate the last screen. The "Create Icons" screen. I do
not now or ever want to create these icons, but Cygwin asks me every single
time. So I must uncheck the boxes every single time.

Yes, I know I can just make a shortcut with the proper flags included, but why
should I? Setup already remembers via /etc/setup/setup.rc:

- last-action
- last-cache
- last-mirror
- mirrors-lst
- net-method

We should be able to add the icon preference to this list.


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

Re: setup release candidate - please test

[Dave Caswell via cygwin]

Execution blocked by Windows 10 anti-virus.(Microsoft Security Essentials.)

On Mon, May 8, 2017 at 5:10 AM, Dave Caswell  wrote:
> Execution blocked by Windows 10 anti-virus.(Microsoft Security
> Essentials.)
>
> On Mon, May 8, 2017 at 5:06 AM, Jon Turney 
> wrote:
>>
>>
>> A setup release candidate is available at:
>>
>>   https://cygwin.com/setup/setup-2.878.x86.exe
>>   https://cygwin.com/setup/setup-2.878.x86_64.exe
>>
>> Since this changes the way we download files, I think this can use some
>> wider testing before release.
>>
>> Please test and give feedback to cygwin@cygwin.com. If no regressions are
>> discovered in the next few days, it will be promoted to release.
>>
>>
>> Changes compared to 2.877:
>>
>> - "Direct Connection" now uses the WinINet API to fetch URLs.
>>
>> This enables HTTPS and FTPS protocol support, and caching of mirrors.lst
>> and setup.ini.
>>
>> The existing, hand-built URL fetching, which only supports HTTP and FTP,
>> is still available by choosing "Direct (legacy)".
>>
>> - Fixes to "Use Internet Explorer Proxy Settings" mode
>>
>> Progress is now reported for downloads.
>>
>> Unwanted caching in "Temporary Internet Files" of package archives has
>> been fixed.
>> (Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00403.html)
>>
>> A bug causing a long delay before downloading setup.ini from package
>> repositories without a compressed setup.ini has been fixed.
>>
>> - Add --allow-unsupported-windows option
>>
>> Don't check the windows version.
>>
>> The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time machine
>> circa) should be given with --site or via the GUI.
>>
>> - Remove support for some long-obsolete setup.ini syntax (omitted
>> version:, omitted size and checksum, various undocumented tokens)
>>
>> - Remove cruft
>>
>> --
>> 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

setup release candidate - please test

[Jon Turney]

A setup release candidate is available at:

  https://cygwin.com/setup/setup-2.878.x86.exe
  https://cygwin.com/setup/setup-2.878.x86_64.exe

Since this changes the way we download files, I think this can use some 
wider testing before release.


Please test and give feedback to cygwin@cygwin.com. If no regressions 
are discovered in the next few days, it will be promoted to release.



Changes compared to 2.877:

- "Direct Connection" now uses the WinINet API to fetch URLs.

This enables HTTPS and FTPS protocol support, and caching of mirrors.lst 
and setup.ini.


The existing, hand-built URL fetching, which only supports HTTP and FTP, 
is still available by choosing "Direct (legacy)".


- Fixes to "Use Internet Explorer Proxy Settings" mode

Progress is now reported for downloads.

Unwanted caching in "Temporary Internet Files" of package archives has 
been fixed.

(Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00403.html)

A bug causing a long delay before downloading setup.ini from package 
repositories without a compressed setup.ini has been fixed.


- Add --allow-unsupported-windows option

Don't check the windows version.

The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time machine 
circa) should be given with --site or via the GUI.


- Remove support for some long-obsolete setup.ini syntax (omitted 
version:, omitted size and checksum, various undocumented tokens)


- Remove cruft

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