Dave Korn wrote on Wednesday, September 10, 2008 7:22 PM::
> Rob wrote on 10 September 2008 19:03:
>
>> Since I'll be doing this upgrade on close to 100 boxes,
>> I've been trying to devise a *relatively* unattended process.
>> In case it helps anyone in the future, here's a snippet of my cmd
>>
Christopher Faylor wrote:
> Dave did suggest a possible workaround - delay any postinstall scripts
> until the next reboot.
That's more graceful than requiring the user to re-run setup to catch
the failed postinstalls. But it still results in a broken system until
the next reboot since those bin
On Wed, Sep 10, 2008 at 02:53:20PM -0700, Brian Dessent wrote:
>Dave Korn wrote:
>
>> Err, that should never happen, unless you're updating from a
>> several-years-old DLL. The Cygwin DLL is intended to be backwardly
>> compatible, and only rarely have their been ABI breaks. So this aspect of
>
Dave Korn wrote:
> Err, that should never happen, unless you're updating from a
> several-years-old DLL. The Cygwin DLL is intended to be backwardly
> compatible, and only rarely have their been ABI breaks. So this aspect of
> updating doesn't get tested very often.
No, that's wrong. It is e
Dave Korn writes:
> That seems like a good start, but it's perhaps just a little bit crude in
> the way it handles services; if you kill them stone dead like that, the SCM
> will try and restart any that are set for auto-restart-on-fail. It would
> probably be a minor improvement if you add an e
Rob wrote on 10 September 2008 19:03:
> I think the safest bet for me in this case is to just kill off everything
> and run setup.
It's really for the best. Upgrading Cygwin while *anything* is still
running is basically something we don't support, and the replace-on-reboot
option is really j
Dave Korn writes:
> Err, that should never happen, unless you're updating from a
> several-years-old DLL. The Cygwin DLL is intended to be backwardly
> compatible, and only rarely have their been ABI breaks. So this aspect of
> updating doesn't get tested very often.
>
Yes, I was testing an u
Rob wrote on 10 September 2008 18:24:
> Dave Korn artimi.com> writes:
>> It might be worth trying a snapshot of 2.602, I think we fixed this on
>> mainline: it should automatically choose the "ok" or "continue" option
>> in any dialogs that would be generated.
>>
>> http://cygwin.com/setup/sna
Dave Korn artimi.com> writes:
> It might be worth trying a snapshot of 2.602, I think we fixed this on
> mainline: it should automatically choose the "ok" or "continue" option in any
> dialogs that would be generated.
>
> http://cygwin.com/setup/snapshots
Dave, I tried running this snapshot se
>> until you click the OK button. This clearly is not "unattended". It
>> would be better if it could just exit with a specific error code that
>> you could read and take some action (restart).
>
> I agree that it's not correct, but I disagree about the conclusion. It
> should silently schedule a
Brian Dessent wrote on 04 September 2008 20:05:
> Rob wrote:
>
>> until you click the OK button. This clearly is not "unattended". It
>> would be better if it could just exit with a specific error code that
>> you could read and take some action (restart).
>
> I agree that it's not correct, but
Rob wrote:
> until you click the OK button. This clearly is not "unattended". It would be
> better if it could just exit with a specific error code that you could read
> and
> take some action (restart).
I agree that it's not correct, but I disagree about the conclusion. It
should silently sche
Bertalan Fodor wrote:
Hello,
how can I tell setup.exe in quiet mode to install e.g. the current
version of lilypond with all of its dependencies. I'm thinking of
something like this:
setup.exe -q -l g:\setup-cygwin -R c:\cygwin -s
http://favoritemirror.sg.com lilypond
No way exists at present.
You
13 matches
Mail list logo
