setup 2.906 release candidate - please test

setup 2.906 release candidate - please test

[Jon Turney]

A new setup release candidate is available at:

   https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
   https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)

Please test, and report any problems here.

This is not the place for setup feature requests.

Changes compared to 2.905:

- If a selected site URL saved from the last run starts with "http://", 
and an identical URL, except starting with "https://", is in the current 
mirror list, migrate it from "http://" to "https://".

- Propagate the value of the CYGWIN environment variable into 
post-install and pre-remove scripts (Thanks to Michael Wild for this patch).
   Partially addresses: 
https://cygwin.com/pipermail/cygwin/2020-August/245994.html

- Warn about unknown package names used with '--packages' or 
'--remove-packages' options.

- Move (potentially localizable) installation progress and package 
action strings to string table resource.

- Fix new warnings and build issues with gcc 10.

Re: setup 2.906 release candidate - please test

[Jon Turney]

On 17/03/2021 20:02, Jon Turney wrote:
> 
> A new setup release candidate is available at:
> 
>    https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>    https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
> 
> Please test, and report any problems here.
> 
> This is not the place for setup feature requests.

Pretty late in preparing this release, I discovered that in Fedora 33, 
the MinGW-w64 32-bit compiler has been changed from sjlj to dwarf2 
unwinding C++ exception handling.

I believe this means that exceptions cannot propagate up through Windows 
code, so the release needs to be delayed until the source code has been 
inspected to see if there's any place where e.g. we throw an exception 
from a Windows callback, but I'd like to get this out for some testing 
already.

Re: setup 2.906 release candidate - please test

[Thomas Wolff]

Am 17.03.2021 um 21:02 schrieb Jon Turney:
>
> A new setup release candidate is available at:
>
>   https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>   https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
>
> Please test, and report any problems here.
I feel the need to take this occasion to woe about the terrible UI of 
setup. Two years or more ago there was a major revision, sarcastically 
accompanied by the comment the UI would have been pushed forward to the 
90s. Before that, you could simply select a package by clicking one (!) 
checkbox. Since then, you have to open a popup, scroll to the latest 
version and click that. This multiplies the effort to do selections 
significantly and it's quite a nuisance.
>
> This is not the place for setup feature requests.
It's not a feature as it was much better before; it's a regression. Can 
we please get back a fast-usable interface?
Thomas

>
> Changes compared to 2.905:
>
> - If a selected site URL saved from the last run starts with 
> "http://", and an identical URL, except starting with "https://", is 
> in the current mirror list, migrate it from "http://" to "https://".
>
> - Propagate the value of the CYGWIN environment variable into 
> post-install and pre-remove scripts (Thanks to Michael Wild for this 
> patch).
>   Partially addresses: 
> https://cygwin.com/pipermail/cygwin/2020-August/245994.html
>
> - Warn about unknown package names used with '--packages' or 
> '--remove-packages' options.
>
> - Move (potentially localizable) installation progress and package 
> action strings to string table resource.
>
> - Fix new warnings and build issues with gcc 10.

Re: setup 2.906 release candidate - please test

[Ken Brown]

On 3/17/2021 5:16 PM, Thomas Wolff wrote:
> Am 17.03.2021 um 21:02 schrieb Jon Turney:
>>
>> A new setup release candidate is available at:
>>
>>   https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>>   https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
>>
>> Please test, and report any problems here.
> I feel the need to take this occasion to woe about the terrible UI of setup. Two 
> years or more ago there was a major revision, sarcastically accompanied by the 
> comment the UI would have been pushed forward to the 90s. Before that, you could 
> simply select a package by clicking one (!) checkbox. Since then, you have to 
> open a popup, scroll to the latest version and click that. This multiplies the 
> effort to do selections significantly and it's quite a nuisance.

If you double-click in the New column, I think it will do what you want.

Ken

Re: setup 2.906 release candidate - please test

[Brian Inglis]

On 2021-03-17 14:02, Jon Turney wrote:
> A new setup release candidate is available at:
>    https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>    https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
> Please test, and report any problems here.
> This is not the place for setup feature requests.
> Changes compared to 2.905:
> - If a selected site URL saved from the last run starts with "http://", and an 
> identical URL, except starting with "https://", is in the current mirror list, 
> migrate it from "http://" to "https://".
> - Propagate the value of the CYGWIN environment variable into post-install and 
> pre-remove scripts (Thanks to Michael Wild for this patch).
>    Partially addresses: https://cygwin.com/pipermail/cygwin/2020-August/245994.html
> - Warn about unknown package names used with '--packages' or '--remove-packages' 
> options.
> - Move (potentially localizable) installation progress and package action 
> strings to string table resource.
> - Fix new warnings and build issues with gcc 10.

Not seeing any issues with this test release.
Sometime in the last while, Cygwin Setup started making the default chooser 
column widths 100-200px wide, and I don't see any obviously relevant change in 
the log, nor any issues in setup.log.full.
Only unusual occurrence may be /etc/setup/setup.rc chooser_window_settings has 
4G-1 in fields 4-7 of window placement, and wondered if those could be getting 
used incorrectly for column width calculations?
I'm on Windows 1909 19H1 10.0.18363.1379 until my next update which says it has 
20H? pending.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

Re: setup 2.906 release candidate - please test

[Jon Turney]

On 17/03/2021 20:08, Jon Turney wrote:
> On 17/03/2021 20:02, Jon Turney wrote:
>>
>> A new setup release candidate is available at:
>>
>>    https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>>    https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
>>
>> Please test, and report any problems here.
>>
>> This is not the place for setup feature requests.
> 
> Pretty late in preparing this release, I discovered that in Fedora 33, 
> the MinGW-w64 32-bit compiler has been changed from sjlj to dwarf2 
> unwinding C++ exception handling.
> 
> I believe this means that exceptions cannot propagate up through Windows 
> code, so the release needs to be delayed until the source code has been 
> inspected to see if there's any place where e.g. we throw an exception 
> from a Windows callback, but I'd like to get this out for some testing 
> already.

I think that this does effect some error cases, where we throw an error 
and expect it to get propagated through a callback.

So for the moment, I've added a configure time check that the x86 
compiler is configured with sjlj exceptions, and dropped back to 
building on Fedora 32.

Long term, I'm not sure what the best approach is.  Using 
-fno-exceptions and adjusting the code not to use exceptions would be a 
start, but that just leaves us silently exiting if an exception is 
thrown from libstdc++...

Re: setup 2.906 release candidate - please test

[Jon Turney]

On 25/03/2021 20:22, kaptain.biwouak@gmail.com wrote:
>>
>> I have tested version 2.906 of setup and I am facing one issue on windows
>> 10:
> 
> Thanks for testing.
> 
>> I got this message: In order to use libusb0, you must download and rune
>> the LibUSB-Win32 driver from:
>> https://sourceforge.net/projects/libusb-win32/files.../libusb-win32-devel-filter-1.2.6.0.exe
> 
> It's unclear if you mean that this message is new with this version of
> setup, or has always been a problem.
> 
> This message is correct (and expected) if you are installing libusb0.
> 
> (this is the package for the deprecated 0.1 libUSB API, so we shouldn't
> have any packages which require it, but it seems we still have a few...)
> 
> Quoted from:
> http://cygwin.1069669.n5.nabble.com/setup-2-906-release-candidate-please-test-tp157282p157374.html
> 
> It is new with this version.
> I have never seen this kind of message by the past.

I'm not able to reproduce this problem.

Can you tell me:
- are you using the 32- or 64-bit version of setup 2.906?
- is the libusb0 package installed?
- do you get this message every time you run setup 2.906?

Re: setup 2.906 release candidate - please test

[Jon Turney]

On 22/03/2021 16:35, kaptain.biwouak@gmail.com wrote:
> <quote author='Jon TURNEY'>
> 
> A new setup release candidate is available at:
> 
>     https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>     https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
> 
> Please test, and report any problems here.
> 
> This is not the place for setup feature requests.
> 
> Changes compared to 2.905:
> 
[...]
> 
> </quote>
> Quoted from:
>   http://cygwin.1069669.n5.nabble.com/setup-2-906-release-candidate-please-test-tp157282.html
> 
> I have tested version 2.906 of setup and I am facing one issue on windows 10:

Thanks for testing.

> I got this message: In order to use libusb0, you must download and rune the LibUSB-Win32 driver from:
> https://sourceforge.net/projects/libusb-win32/files.../libusb-win32-devel-filter-1.2.6.0.exe

It's unclear if you mean that this message is new with this version of 
setup, or has always been a problem.

This message is correct (and expected) if you are installing libusb0.

(this is the package for the deprecated 0.1 libUSB API, so we shouldn't 
have any packages which require it, but it seems we still have a few...)