Re: setup-*.exe --help default explanation re -D/-L options [Was: [ANNOUNCEMENT] Updated: setup (2.917)]
On 01/02/2022 21:46, Adam Dinwoodie wrote: On Tue, Feb 01, 2022 at 04:53:47PM +, Jon Turney wrote: [...] Note that I tweaked the behaviour of this a bit in [1] [1] https://cygwin.com/git/?p=cygwin-apps/setup.git;a=commit;h=147fc15d0222e050779b18a209991c258d85944f I think that makes the current help text accurately describe non-interactive mode. There are some cases in interactive mode which are obscure (e.g. '-M' without '-D' or '-L' gets you whatever mode you used last time without showing you what it was, but I'm not sure if that needs to be here. Ah, okay. I think I hit this with `-M` and assumed -- evidently incorrectly -- that the same behaviour would exist for `-q`. I agree the current text is entirely accurate for the fully non-interactive mode. [...]> I definitely see no harm in that approach, and I agreed that'd make things clearer again. But, as above, I think the key thing from my perspective would be for `-M` and `-q` to have consistent behaviour. Yes, on reflection, I think that change isn't quite right, and '-M' should be handled the same as '-q' there (i.e. '-D' & '-L' is the default, unless explicitly specified otherwise)
Re: setup-*.exe --help default explanation re -D/-L options [Was: [ANNOUNCEMENT] Updated: setup (2.917)]
Greetings, Jon Turney!
>> If neither --download nor --local-install is specified, the default
>> is to repeat the same action as from the previous run. If no
>> previous run can be found, the default is to perform both actions,
>> and both actions can be explicitly requested by specifying both
>> --download and --local-install.
> Note that I tweaked the behaviour of this a bit in [1]
> [1]
> https://cygwin.com/git/?p=cygwin-apps/setup.git;a=commit;h=147fc15d0222e050779b18a209991c258d85944f
> I think that makes the current help text accurately describe
> non-interactive mode.
> There are some cases in interactive mode which are obscure (e.g. '-M'
> without '-D' or '-L' gets you whatever mode you used last time without
> showing you what it was, but I'm not sure if that needs to be here.
>> In particular, the fact that the two options currently say they will
>> "only" do their action, and that the default is to perform both, lead me
>> to believe (a) the options were mutually exclusive and one would
>> presumably override the other, (b) this was probably a legacy from
>> before setup.rc stored the previous action, and therefore (c) if I was
>> running setup with `-q` or `-M`, there was no way to get the supposedly
>> default "do both" behaviour; I'd instead need to go through the full
>> GUI.
>>
>> Having now seen how this setting is stored, I've realised I can just
>> call setup with `-DL` and it'll perform both actions again. But I think
>> my assumption that "default" was supposed to mean "default always" not
>> "default only on first run" wasn't *entirely* PEBCAK (even if it mostly
>> was), so that help text would definitely benefit from being made a bit
>> more explicit.
>>
>> (I'm aware my suggestion above is decidedly wordy; it's not intended to
>> be exactly what I think is required, only a first pass at clarifying the
>> key details I think are missing.)
> Perhaps the best thing would be to have something like
> '--mode={download, install, somebetterwordforboth}' and document '-D'
> and '-L' as short aliases for forms of that (which makes the modality
> clear).
Definitely no. You'd have to invent a "better word" first and that would be
a whole new layer of explanation.
I'd vote for removal of -M for unattended operations instead. (I.e. make -q
and -M mutually exclusive.)
I mean, this is an unattended operation, right? You HAVE TO be explicit in
what results are expected from it.
--
With best regards,
Andrey Repin
Thursday, February 3, 2022 11:35:30
Sorry for my terrible english...
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: setup-*.exe --help default explanation re -D/-L options [Was: [ANNOUNCEMENT] Updated: setup (2.917)]
On Tue, Feb 01, 2022 at 04:53:47PM +, Jon Turney wrote:
> On 31/01/2022 22:11, Adam Dinwoodie wrote:
> > On Mon, 31 Jan 2022 12:56:13 -0700, Brian Inglis wrote:
> > > On 2022-01-31 08:46, Andrey Repin wrote:
> > > > Greetings, Jon Turney!
> > > >
> > > > > Probably what's wanted is to remember the state of those checkboxes,
> > > > > if
> > > > > this isn't the first time setup has been run?
> > > >
> > > > That's a feature silently longed for for a loong time. :) But this is
> > > > such a
> > > > low priority, very few people actually mentioned it in the past years.
> > >
> > > It could usefully be added similarly to last-action:
> > >
> > > $ fgrep -A1 action /etc/setup/setup.rc
> > > last-action
> > > Download,Install
> > >
> > > last-shortcut:
> > > Desktop|StartMenu|none,...
> >
> > This reminded me of a bug report I've been meaning to properly
> > characterise and report for a while, and also pointed me at a
> > workaround...
> >
> > Currently, running `setup-*.exe --help` produces output that includes
> > the following:
> >
> > -D --download Download packages from internet only
> > -L --local-install Install packages from local directory only
> >
> > The default is to both download and install packages, unless either
> > --download or --local-install is specified.
> >
> > I think the descriptions for the `-D` and `-L` options are misleading,
> > at least in combination with that final line, which is definitely wrong.
> > As I understand it, the actual behaviour would be better described by
> > something like the below:
> >
> > -D --download Download packages from internet only, unless -L
> > is also specified
> > -L --local-install Install packages from local directory only,
> > unless -D is also specified
>
> One could just remove the word 'only'?
...yes, that would in fact work, and is clear.
> > If neither --download nor --local-install is specified, the default
> > is to repeat the same action as from the previous run. If no
> > previous run can be found, the default is to perform both actions,
> > and both actions can be explicitly requested by specifying both
> > --download and --local-install.
>
> Note that I tweaked the behaviour of this a bit in [1]
>
> [1]
> https://cygwin.com/git/?p=cygwin-apps/setup.git;a=commit;h=147fc15d0222e050779b18a209991c258d85944f
>
> I think that makes the current help text accurately describe non-interactive
> mode.
>
> There are some cases in interactive mode which are obscure (e.g. '-M'
> without '-D' or '-L' gets you whatever mode you used last time without
> showing you what it was, but I'm not sure if that needs to be here.
Ah, okay. I think I hit this with `-M` and assumed -- evidently
incorrectly -- that the same behaviour would exist for `-q`. I agree
the current text is entirely accurate for the fully non-interactive
mode.
I think this caught me out because I frequently run with `-M` -- I don't
care about most of the options, but I do want to see what packages are
about to be updated -- and I almost never want to use the download-only
or install-only modes. But I used `-L` as a one-off when I was
uninstalling and reinstalling a bunch of packages and didn't want to hit
the network every time, then forgot about it. And it wasn't until I was
musing about the fact that I hadn't seen any package updates for a few
weeks when trying to do my regular updates with `-M` that I realised
what had happened...
Given all that, I think everything seems sensible except for the fact
that `-M` doesn't follow the same behaviour as `-q`.
> > In particular, the fact that the two options currently say they will
> > "only" do their action, and that the default is to perform both, lead me
> > to believe (a) the options were mutually exclusive and one would
> > presumably override the other, (b) this was probably a legacy from
> > before setup.rc stored the previous action, and therefore (c) if I was
> > running setup with `-q` or `-M`, there was no way to get the supposedly
> > default "do both" behaviour; I'd instead need to go through the full
> > GUI.
> >
> > Having now seen how this setting is stored, I've realised I can just
> > call setup with `-DL` and it'll perform both actions again. But I think
> > my assumption that "default" was supposed to mean "default always" not
> > "default only on first run" wasn't *entirely* PEBCAK (even if it mostly
> > was), so that help text would definitely benefit from being made a bit
> > more explicit.
> >
> > (I'm aware my suggestion above is decidedly wordy; it's not intended to
> > be exactly what I think is required, only a first pass at clarifying the
> > key details I think are missing.)
>
> Perhaps the best thing would be to have something like '--mode={download,
> install, somebetterwordforboth}' and document '-D' and '-L' as short aliases
> for forms of
Re: setup-*.exe --help default explanation re -D/-L options [Was: [ANNOUNCEMENT] Updated: setup (2.917)]
On 31/01/2022 22:11, Adam Dinwoodie wrote:
On Mon, 31 Jan 2022 12:56:13 -0700, Brian Inglis wrote:
On 2022-01-31 08:46, Andrey Repin wrote:
Greetings, Jon Turney!
Probably what's wanted is to remember the state of those checkboxes, if
this isn't the first time setup has been run?
That's a feature silently longed for for a loong time. :) But this is such a
low priority, very few people actually mentioned it in the past years.
It could usefully be added similarly to last-action:
$ fgrep -A1 action /etc/setup/setup.rc
last-action
Download,Install
last-shortcut:
Desktop|StartMenu|none,...
This reminded me of a bug report I've been meaning to properly
characterise and report for a while, and also pointed me at a
workaround...
Currently, running `setup-*.exe --help` produces output that includes
the following:
-D --download Download packages from internet only
-L --local-install Install packages from local directory only
The default is to both download and install packages, unless either
--download or --local-install is specified.
I think the descriptions for the `-D` and `-L` options are misleading,
at least in combination with that final line, which is definitely wrong.
As I understand it, the actual behaviour would be better described by
something like the below:
-D --download Download packages from internet only, unless -L
is also specified
-L --local-install Install packages from local directory only,
unless -D is also specified
One could just remove the word 'only'?
If neither --download nor --local-install is specified, the default
is to repeat the same action as from the previous run. If no
previous run can be found, the default is to perform both actions,
and both actions can be explicitly requested by specifying both
--download and --local-install.
Note that I tweaked the behaviour of this a bit in [1]
[1]
https://cygwin.com/git/?p=cygwin-apps/setup.git;a=commit;h=147fc15d0222e050779b18a209991c258d85944f
I think that makes the current help text accurately describe
non-interactive mode.
There are some cases in interactive mode which are obscure (e.g. '-M'
without '-D' or '-L' gets you whatever mode you used last time without
showing you what it was, but I'm not sure if that needs to be here.
In particular, the fact that the two options currently say they will
"only" do their action, and that the default is to perform both, lead me
to believe (a) the options were mutually exclusive and one would
presumably override the other, (b) this was probably a legacy from
before setup.rc stored the previous action, and therefore (c) if I was
running setup with `-q` or `-M`, there was no way to get the supposedly
default "do both" behaviour; I'd instead need to go through the full
GUI.
Having now seen how this setting is stored, I've realised I can just
call setup with `-DL` and it'll perform both actions again. But I think
my assumption that "default" was supposed to mean "default always" not
"default only on first run" wasn't *entirely* PEBCAK (even if it mostly
was), so that help text would definitely benefit from being made a bit
more explicit.
(I'm aware my suggestion above is decidedly wordy; it's not intended to
be exactly what I think is required, only a first pass at clarifying the
key details I think are missing.)
Perhaps the best thing would be to have something like
'--mode={download, install, somebetterwordforboth}' and document '-D'
and '-L' as short aliases for forms of that (which makes the modality
clear).
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
setup-*.exe --help default explanation re -D/-L options [Was: [ANNOUNCEMENT] Updated: setup (2.917)]
On Mon, 31 Jan 2022 12:56:13 -0700, Brian Inglis wrote: > On 2022-01-31 08:46, Andrey Repin wrote: > > Greetings, Jon Turney! > > > > > Probably what's wanted is to remember the state of those checkboxes, if > > > this isn't the first time setup has been run? > > > > That's a feature silently longed for for a loong time. :) But this is such a > > low priority, very few people actually mentioned it in the past years. > > It could usefully be added similarly to last-action: > > $ fgrep -A1 action /etc/setup/setup.rc > last-action > Download,Install > > last-shortcut: > Desktop|StartMenu|none,... This reminded me of a bug report I've been meaning to properly characterise and report for a while, and also pointed me at a workaround... Currently, running `setup-*.exe --help` produces output that includes the following: -D --download Download packages from internet only -L --local-install Install packages from local directory only The default is to both download and install packages, unless either --download or --local-install is specified. I think the descriptions for the `-D` and `-L` options are misleading, at least in combination with that final line, which is definitely wrong. As I understand it, the actual behaviour would be better described by something like the below: -D --download Download packages from internet only, unless -L is also specified -L --local-install Install packages from local directory only, unless -D is also specified If neither --download nor --local-install is specified, the default is to repeat the same action as from the previous run. If no previous run can be found, the default is to perform both actions, and both actions can be explicitly requested by specifying both --download and --local-install. In particular, the fact that the two options currently say they will "only" do their action, and that the default is to perform both, lead me to believe (a) the options were mutually exclusive and one would presumably override the other, (b) this was probably a legacy from before setup.rc stored the previous action, and therefore (c) if I was running setup with `-q` or `-M`, there was no way to get the supposedly default "do both" behaviour; I'd instead need to go through the full GUI. Having now seen how this setting is stored, I've realised I can just call setup with `-DL` and it'll perform both actions again. But I think my assumption that "default" was supposed to mean "default always" not "default only on first run" wasn't *entirely* PEBCAK (even if it mostly was), so that help text would definitely benefit from being made a bit more explicit. (I'm aware my suggestion above is decidedly wordy; it's not intended to be exactly what I think is required, only a first pass at clarifying the key details I think are missing.) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On 2022-01-31 08:46, Andrey Repin wrote: Greetings, Jon Turney! Probably what's wanted is to remember the state of those checkboxes, if this isn't the first time setup has been run? That's a feature silently longed for for a loong time. :) But this is such a low priority, very few people actually mentioned it in the past years. It could usefully be added similarly to last-action: $ fgrep -A1 action /etc/setup/setup.rc last-action Download,Install last-shortcut: Desktop|StartMenu|none,... -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
Greetings, Jon Turney! > Probably what's wanted is to remember the state of those checkboxes, if > this isn't the first time setup has been run? That's a feature silently longed for for a loong time. :) But this is such a low priority, very few people actually mentioned it in the past years. -- With best regards, Andrey Repin Monday, January 31, 2022 18:45:55 Sorry for my terrible english... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On 31.01.2022 06:36, © Fxzx mic wrote: Hello, I want to know how to change the default value of the check boxes when creating a program shortcut after installation so that it is no longer checked by default. Which part of the program needs to be changed? [...]> Can you please clarify with an example ? Which shortcut do you mean ? Maybe you should look on the Command Line options for already available options : $ ./setup-x86_64.exe --help Cygwin setup 2.917 Command Line Options: ... -d --no-desktop Disable creation of desktop shortcut ... On 31/01/2022 06:43, © Fxzx mic wrote: > > After installing (or updating) through the GUI, the program will > finally have two check boxes to choose whether to create shortcuts, > and the default status of these two check boxes is checked. I just > want to know how to cancel this default behavior. I want to know > where this behavior is written in the setup program source code. If you search for that option text in the source code you'll end up looking at: https://cygwin.com/git/?p=cygwin-apps/setup.git;a=blob;f=desktop.cc Note that a patch to simply reverse the default setting of that option (i.e. make it unset by default, and require the user to click that checkbox to create the shortcuts (meaning that most users will have to do that) would not be acceptable. Probably what's wanted is to remember the state of those checkboxes, if this isn't the first time setup has been run? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
2022-01-31 06:43 UTC, © Fxzx mic: > > Marco Atzeri, 2022年1月31日 14:25: > > > On 31.01.2022 06:36, © Fxzx mic wrote: > > > Hello, > > > I want to know how to change the default value of [...] > > > > Hi, > > > > bottom posting on this mailing list, please. [...] > > Hello, > Sorry, I just want to ask the author first. I don't know this rule. Sorry. See this explanation of posting styles: https://en.wikipedia.org/wiki/Posting_style -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
Hello, Sorry, I just want to ask the author first. I don't know this rule. Sorry. After installing (or updating) through the GUI, the program will finally have two check boxes to choose whether to create shortcuts, and the default status of these two check boxes is checked. I just want to know how to cancel this default behavior. I want to know where this behavior is written in the setup program source code. Thanks. --- From: Fxzx mic fxzx...@outlook.com<mailto:fxzx...@outlook.com> --- 发件人: Marco Atzeri<mailto:marco.atz...@gmail.com> 发送时间: 2022年1月31日 14:25 收件人: cygwin@cygwin.com<mailto:cygwin@cygwin.com> 抄送: fxzx...@outlook.com<mailto:fxzx...@outlook.com> 主题: Re: [ANNOUNCEMENT] Updated: setup (2.917) On 31.01.2022 06:36, © Fxzx mic wrote: > Hello, > I want to know how to change the default value of the check boxes when > creating a program shortcut after installation so that it is no longer > checked by default. > Which part of the program needs to be changed? > Hi, bottom posting on this mailing list, please. Can you please clarify with an example ? Which shortcut do you mean ? Maybe you should look on the Command Line options for already available options : $ ./setup-x86_64.exe --help Cygwin setup 2.917 Command Line Options: ... -d --no-desktop Disable creation of desktop shortcut ... Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On 31.01.2022 06:36, © Fxzx mic wrote: Hello, I want to know how to change the default value of the check boxes when creating a program shortcut after installation so that it is no longer checked by default. Which part of the program needs to be changed? Hi, bottom posting on this mailing list, please. Can you please clarify with an example ? Which shortcut do you mean ? Maybe you should look on the Command Line options for already available options : $ ./setup-x86_64.exe --help Cygwin setup 2.917 Command Line Options: ... -d --no-desktop Disable creation of desktop shortcut ... Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
Hello, I want to know how to change the default value of the check boxes when creating a program shortcut after installation so that it is no longer checked by default. Which part of the program needs to be changed? --- From: Fxzx mic fxzx...@outlook.com<mailto:fxzx...@outlook.com> --- 发件人: Jon Turney<mailto:jon.tur...@dronecode.org.uk> 发送时间: 2022年1月25日 4:04 收件人: cygwin@cygwin.com<mailto:cygwin@cygwin.com> 主题: [ANNOUNCEMENT] Updated: setup (2.917) A new version of Setup (2.917) has been uploaded to: https://cygwin.com/setup-x86_64.exe (64 bit version) https://cygwin.com/setup-x86.exe (32 bit version) Changes compared to 2.915: - Show a warning if running on a deprecated Windows version Support for: - Windows 6.0 (Windows Vista, Windows Server 2008) - 32-bit Windows (including WoW64) in Cygwin is deprecated and will be removed in the next major version, sometime this year. This warning can be disabled with the '--no-warn-deprecated-windows' or '-w' option, or using a "In the future, do not show me this dialogue box" checkbox. - Fix setup silently exiting if elevated and 'CYGWIN=winsymlinks:lnk' is in the environment (by ignoring that environment variable) Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250523.html - Fix creating bogus versions of obsoleted packages (under certain specific circumstances), which then fail to download because they don't exist! Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250604.html For instructions on obtaining and building the source code for setup, see https://sourceware.org/cygwin-apps/setup.html Please send bug reports, as usual, to the public mailing list cygwin AT cygwin DOT com. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
Hi Jon, On 29/1/22 1:56 am, Jon Turney wrote: Thanks for reporting this. This seems to be a crash which occurs if you're not using 'download and install' mode, and have cached setup.ini files from multiple mirrors, and those differ in if any install package for a given source package is available. I've uploaded an updated setup with an attempted fix for this: https://cygwin.com/setup/setup-2.917-3-g489d9c.x86_64.exe https://cygwin.com/setup/setup-2.917-3-g489d9c.x86.exe Perhaps you could try that and see if it improves things for you? It does. That's fixed it. Thank you for your prompt response. -- Regards, Shaddy Baddah -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On 27/01/2022 07:28, Shaddy Baddah wrote: Hi, On 25/1/22 7:02 am, Jon Turney wrote: > A new version of Setup (2.917) has been uploaded to: > > https://cygwin.com/setup-x86_64.exe (64 bit version) > https://cygwin.com/setup-x86.exe (32 bit version) > > Changes compared to 2.915: ... I've had a new problem with this version, which I have been able to work around. I guess this means 2.915 didn't have this problem. I normally do a two stage update of Cygwin, with the second stage being running down the "Install from Local Directory" path. This was silently existing. As it turned out, it was doing so as I had an old, setup.ini from a mirror I had unintentionally selected (rather than my preferred mirror). Here's the preamble to that setup.ini: [...] I moved that out of the way, and then was able to proceed. I was fortunate that I acted on a hunch. Otherwise, even with -v on command line, there was nothing that could indicate to me what was causing the issue. I'm hoping that this silent exit can be fixed, to at least give an indication, via logging or pop-up or other, of what is blocking the install. Thanks for reporting this. This seems to be a crash which occurs if you're not using 'download and install' mode, and have cached setup.ini files from multiple mirrors, and those differ in if any install package for a given source package is available. I've uploaded an updated setup with an attempted fix for this: https://cygwin.com/setup/setup-2.917-3-g489d9c.x86_64.exe https://cygwin.com/setup/setup-2.917-3-g489d9c.x86.exe Perhaps you could try that and see if it improves things for you? Thanks. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
Hi, On 25/1/22 7:02 am, Jon Turney wrote: > A new version of Setup (2.917) has been uploaded to: > > https://cygwin.com/setup-x86_64.exe (64 bit version) > https://cygwin.com/setup-x86.exe (32 bit version) > > Changes compared to 2.915: ... I've had a new problem with this version, which I have been able to work around. I normally do a two stage update of Cygwin, with the second stage being running down the "Install from Local Directory" path. This was silently existing. As it turned out, it was doing so as I had an old, setup.ini from a mirror I had unintentionally selected (rather than my preferred mirror). Here's the preamble to that setup.ini: == # This file was automatically generated at 2021-09-28 15:09:17 GMT. # # If you edit it, your edits will be discarded next time the file is # generated. # # See https://sourceware.org/cygwin-apps/setup.ini.html for a description # of the format. release: cygwin arch: x86_64 setup-timestamp: 1632841757 include-setup: setup <2.878 not supported setup-minimum-version: 2.895 setup-version: 2.909 == I moved that out of the way, and then was able to proceed. I was fortunate that I acted on a hunch. Otherwise, even with -v on command line, there was nothing that could indicate to me what was causing the issue. I'm hoping that this silent exit can be fixed, to at least give an indication, via logging or pop-up or other, of what is blocking the install. -- Regards, Shaddy Baddah -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On Tue, Jan 25, 2022 at 10:33:52PM +, Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote: > On Mon, Jan 24, 2022 at 6:12 PM Bill Stewart wrote: > > > >On Mon, Jan 24, 2022 at 3:49 PM Buchbinder, Barry (NIH/NIAID) [E] via Cygwin > >wrote: > > > >Windows protected your PC > >> Microsoft Defender SmartScreen prevented an unrecognized app from starting. > >> Running this app might put your PC at risk. > >> > > > >Not to state the obvious, but this means that the Microsoft antivirus > >program prevented it from running. > > > >Exclude it. > > I have no control over the antivirus, so cannot exclude it. > > The point was that this wasn't a problem with 2.915, so most likely is the > result of some change made in 2.917. > > However, this morning, after a reboot, it seems to work OK. The difference was entirely that the new setup installer was new. Microsoft Defender SmartScreen learns what programs are safe by seeing how many people download and use them, on the basis that things that are downloaded by lots of people and don't become known as a specific threat should be fine, whereas something unknown may well be some new malware. This flag doesn't indicate there's anything about 2.917 that had changed to worry about, only that it had changed and that you were one of the first to try to use it. If you don't have the ability to override the spurious warning, your only options will be to wait longer before using the new version, so SmartScreen has a chance to learn it's safe from people who can click past the warning, or to take it up with whoever manages your systems. There is nothing the Cygwin project folks could do to help other than never release new software. There's a bit more information on the "reputation" checking under "How Microsoft Defender SmartScreen works when a user tries to run an app" at https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device (For the sake of explicitness, I am a Microsoft employee these days, but SmartScreen is nothing to do with my role at Microsoft, and Cygwin is at best tangential. I don't have any more knowledge or influence in this area than any non-employee.) Adam -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On Mon, Jan 24, 2022 at 6:12 PM Bill Stewart wrote: > >On Mon, Jan 24, 2022 at 3:49 PM Buchbinder, Barry (NIH/NIAID) [E] via Cygwin > wrote: > >Windows protected your PC >> Microsoft Defender SmartScreen prevented an unrecognized app from starting. >> Running this app might put your PC at risk. >> > >Not to state the obvious, but this means that the Microsoft antivirus program >prevented it from running. > >Exclude it. I have no control over the antivirus, so cannot exclude it. The point was that this wasn't a problem with 2.915, so most likely is the result of some change made in 2.917. However, this morning, after a reboot, it seems to work OK. Sorry for any bother. Thanks, - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: setup (2.917)
On Mon, Jan 24, 2022 at 3:49 PM Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote: Windows protected your PC > Microsoft Defender SmartScreen prevented an unrecognized app from starting. > Running this app might put your PC at risk. > [Responding to mailing list] Not to state the obvious, but this means that the Microsoft antivirus program prevented it from running. Exclude it. Bill -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: [ANNOUNCEMENT] Updated: setup (2.917)
I cannot run setup 2.917. When trying to start setup-x86_64 -n -B under cmd.exe or by cygstart under bash, I get the following error message. Unable to start 'C:\cygwin\usr\local\bin\setup-x86_64.exe': The operating system denied access to the specified file. Adding -w to the command line does not help. Opening direct from Chrome gets the following error message. Windows protected your PC Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk. Setup 2.915 still works fine. Thanks - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: setup (2.917)
A new version of Setup (2.917) has been uploaded to: https://cygwin.com/setup-x86_64.exe (64 bit version) https://cygwin.com/setup-x86.exe (32 bit version) Changes compared to 2.915: - Show a warning if running on a deprecated Windows version Support for: - Windows 6.0 (Windows Vista, Windows Server 2008) - 32-bit Windows (including WoW64) in Cygwin is deprecated and will be removed in the next major version, sometime this year. This warning can be disabled with the '--no-warn-deprecated-windows' or '-w' option, or using a "In the future, do not show me this dialogue box" checkbox. - Fix setup silently exiting if elevated and 'CYGWIN=winsymlinks:lnk' is in the environment (by ignoring that environment variable) Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250523.html - Fix creating bogus versions of obsoleted packages (under certain specific circumstances), which then fail to download because they don't exist! Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250604.html For instructions on obtaining and building the source code for setup, see https://sourceware.org/cygwin-apps/setup.html Please send bug reports, as usual, to the public mailing list cygwin AT cygwin DOT com. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
