On Sep 21, 2015, at 7:11 PM, Michael Enright wrote:
>
> The blindness was blindness to the fact that new users were getting a
> different version than existing users in some way other than fixing
> vulns.
Why should you believe that in the first place? There is only one Cygwin, so
why would you
On Tue, Sep 22, 2015 at 10:54 AM, Yaakov Selkowitz wrote:
>
> Installing with Cygwin Setup.
>
>
> This is the only supported installation method.
>
On Tue, Sep 22, 2015 at 10:59 AM, David Stacey wrote:
> We're drifting off topic, but never mind...
Thanks Yaakov, David, Achim, Vince and whoever e
Michael Enright writes:
> I am interested to hear if anyone has managed a group of Cygwin users
> and the configuration they use, and how they went about it.
I do and the only sane way is to have a local mirror with exactly the
packages and versions that you are going to install and your own
setup
On 22/09/15 18:16, Michael Enright wrote:
New workers needed new Windows boxes with Cygwin
on them. What is the process for putting Cygwin on a new Windows box?
It isn't "rsync Cygwin from IT".
Cygwin's default (or only) distribution method has a role to play in
this. Does anyone ever setup Cygw
On Tue, 2015-09-22 at 10:16 -0700, Michael Enright wrote:
> No one was updating. New workers needed new Windows boxes with Cygwin
> on them. What is the process for putting Cygwin on a new Windows box?
Installing with Cygwin Setup.
> Cygwin's default (or only) distribution method has a role to pl
On Mon, Sep 21, 2015 at 9:16 PM, Vince Rice wrote:
>
> The blindness was, as I’ve already pointed out, caused by blindly
> updating software
No one was "updating"! I have diagnosed what I did "wrong" before and
I am satisfied with my conclusion. I don't yet know of a way to keep
changes from affe
On Sep 21, 2015, at 8:11 PM, Michael Enright wrote:
>
> On Mon, Sep 21, 2015 at 5:50 PM, Vince Rice wrote:
>
>> blindly
>
> The blindness was blindness to the fact that new users were getting a
> different version than existing users in some way other than fixing
> vulns.
> …
The blindness wa
On Mon, Sep 21, 2015 at 5:50 PM, Vince Rice wrote:
>blindly
The blindness was blindness to the fact that new users were getting a
different version than existing users in some way other than fixing
vulns. Since Cygwin isn't the sort of product that needs to make up
sham reasons to upgrade as Mic
> On Sep 21, 2015, at 7:04 PM, Michael Enright wrote:
>
> On Mon, Sep 21, 2015 at 1:31 PM, Marco Atzeri wrote:
>>
>> the change in nc had nothing to do with cygwin
>> change between 1.5 and 1.7
>>
>> https://sourceware.org/ml/cygwin-announce/2012-05/msg00015.html
>>
>
> Implying a tie betwee
On Mon, Sep 21, 2015 at 1:31 PM, Marco Atzeri wrote:
>
> the change in nc had nothing to do with cygwin
> change between 1.5 and 1.7
>
> https://sourceware.org/ml/cygwin-announce/2012-05/msg00015.html
>
Implying a tie between the nc version to the release of 1.7.0-0 was
wrong on my part. I am not
On 21/09/2015 22:02, jacob.a.lamber...@l-3com.com wrote:
Hello anrdae...@yandex.ru!
1. https://cygwin.com/acronyms/#TOFU pretty please.
Upgrading would be a pain,
Who said that?...
1. Here we go.
2. While I doubt it would be technically difficult, it would be easier to keep
the same ver
On 21/09/2015 21:55, Michael Enright wrote:
On Mon, Sep 21, 2015 at 12:25 PM, Andrey Repin wrote:
Upgrading would be a pain,
Who said that?...
PMFJI,
Between Cyg 1.5 and 1.7 the command-line interface changed on the "nc"
utility and, from the point of view of someone who at the time
Hello anrdae...@yandex.ru!
> 1. https://cygwin.com/acronyms/#TOFU pretty please.
>
> > Upgrading would be a pain,
>
> Who said that?...
1. Here we go.
2. While I doubt it would be technically difficult, it would be easier to keep
the same version as far as good ol' corporate policy goes.
Sin
On Mon, Sep 21, 2015 at 12:25 PM, Andrey Repin wrote:
> Greetings, jacob.a.lamber...@l-3com.com!
>
> 1. https://cygwin.com/acronyms/#TOFU pretty please.
>
>> Upgrading would be a pain,
>
> Who said that?...
>
>
PMFJI,
Between Cyg 1.5 and 1.7 the command-line interface changed on the "nc"
utility
Greetings, jacob.a.lamber...@l-3com.com!
1. https://cygwin.com/acronyms/#TOFU pretty please.
> Upgrading would be a pain,
Who said that?...
--
With best regards,
Andrey Repin
Monday, September 21, 2015 22:24:28
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/pr
bject: Re: Question about old win32 api
On Mon, 2015-09-21 at 16:10 +, jacob.a.lamber...@l-3com.com wrote:
> I'm attempting to compile cygwin 1.7.18. I've made some progress, but
> have run into what appears to be an incompatibility between minGW's
> Win32 api and th
On Mon, 2015-09-21 at 16:10 +, jacob.a.lamber...@l-3com.com wrote:
> I'm attempting to compile cygwin 1.7.18. I've made some progress, but have
> run into what appears to be an incompatibility between minGW's Win32 api
> and this version of cygwin.
Better yet, why are you trying to build su
17 matches
Mail list logo
