Greetings, Brian Inglis!
>>> The problem is, not all packages are prepared to deal with locked shared
>>> objects (in truth, none are). Which may leave system in an inconsistent
>>> state even after reboot.
> Cygwin setup uses standard Windows wininit processing to perform the
> replacements on r
On 19.3.2018 5:56, Tatsuro MATSUOKA wrote:
Sever survice like cygsever always start after windows re-start if it is
registered.
So restart does not always kill cygwin processes.
I do not want to force to kill cygwin process by setupXX.exe but output the
warning.
Hi,
I use script [1] for yea
On 2018-03-18 22:56, Tatsuro MATSUOKA wrote:
> On 2018-03-18 20:56, Andrey Repin wrote:
>>> On cygwin setup, one has to kill cygwin process to execute
>>> autorebase in the end of setup process. I think it is better to
>>> output warning at start stage setup if cygwin process running.
- Original Message -
> From: Andrey Repin
> To: Brian Inglis ; cygwin
> Cc:
> Date: 2018/3/19, Mon 13:02
> Subject: Re: output warning for cygwin process running at setup__.exe
>
>G reetings, Brian Inglis!
>
>> On 2018-03-18 20:56, Andrey Repin wrote:
&g
Greetings, Brian Inglis!
> On 2018-03-18 20:56, Andrey Repin wrote:
> On cygwin setup, one has to kill cygwin process to execute autorebase
> in the end of setup process. I think it is better to output warning at
> start stage setup if cygwin process running.
>>> Sorry for my inadequ
On 2018-03-18 20:56, Andrey Repin wrote:
On cygwin setup, one has to kill cygwin process to execute autorebase
in the end of setup process. I think it is better to output warning at
start stage setup if cygwin process running.
>> Sorry for my inadequate description.
>> At postinsta
6 matches
Mail list logo
