On Sep 3 21:12, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> How feasible would it be to generate an alternate setup.ini
> >> (setup-snapshots.ini or something) and include the snapshots in the
> >> actual mirror with a switch to setup to select the alternate file?
> >> When we finally get t
Corinna Vinschen writes:
>> How feasible would it be to generate an alternate setup.ini
>> (setup-snapshots.ini or something) and include the snapshots in the
>> actual mirror with a switch to setup to select the alternate file?
>> When we finally get to it with OCaml's CI, that is probably how I
>
On Sep 2 08:37, David Allsopp wrote:
> Corinna Vinschen wrote:
> > On Sep 1 16:41, David Allsopp wrote:
> > > Corinna Vinschen wrote:
> > > > Some of the path handling is seriously crippled as soon as you start
> > > > using backslashes, and that's a delipberate decision and won't
> > > > change,
Corinna Vinschen wrote:
> On Sep 1 16:41, David Allsopp wrote:
> > Corinna Vinschen wrote:
> > > Some of the path handling is seriously crippled as soon as you start
> > > using backslashes, and that's a delipberate decision and won't
> > > change, even after fixing the aforementioned bug.
> >
> >
cyg Simple wrote:
> On 9/1/2018 5:52 PM, Andrey Repin wrote:
> > Greetings, David Allsopp!
> >
> >>> In terms of this OCAML build system problem:
> >>>
> >>> Please fix your build system. Do not mix POSIX and Win32 paths, use
> >>> POSIX paths only. Backslashes are *no* drop-in replacement for sl
On 9/1/2018 5:52 PM, Andrey Repin wrote:
> Greetings, David Allsopp!
>
>>> In terms of this OCAML build system problem:
>>>
>>> Please fix your build system. Do not mix POSIX and Win32 paths, use POSIX
>>> paths only. Backslashes are *no* drop-in replacement for slashes.
>
>> The "problem" for
Greetings, David Allsopp!
>> In terms of this OCAML build system problem:
>>
>> Please fix your build system. Do not mix POSIX and Win32 paths, use POSIX
>> paths only. Backslashes are *no* drop-in replacement for slashes.
> The "problem" for us is more subtle than this. The program which is
>
On Sat, 1 Sep 2018 21:23:56, Corinna Vinschen wrote:
> > Yes, you would run the chance that you would have to mend an official
> > release several times ... but is that bad?
>
> The idea of test releases is to avoid problem like the one we're discussing
> here in official releases. I'd like to ge
> As for the bug in question: I pushed a patch which should fix this
> issue. I created new developer snapshots and uploaded them to
> https://cygwin.com/snapshots/. Please give them a try.
Thank you Corinna for the quick fix and investigation!
I set up an environment to test it out:
https
On Sep 1 20:08, Houder wrote:
> On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote:
> > I'll fix this and release a 2.11.1 soon, but I still have a question:
> >
> > Why do I push out test releases if nobody cares?
>
> Yes, I know, it is a _hypothetical_question_. You do not really expect
> an
On Sep 1 16:41, David Allsopp wrote:
> Corinna Vinschen wrote:
> > Some of the path handling is seriously crippled as soon as you start using
> > backslashes, and that's a delipberate decision and won't change, even after
> > fixing the aforementioned bug.
>
> I don't quite follow this - does tha
On Sat, 1 Sep 2018 17:54:35, Corinna Vinschen wrote:
> I'll fix this and release a 2.11.1 soon, but I still have a question:
>
> Why do I push out test releases if nobody cares?
Yes, I know, it is a _hypothetical_question_. You do not really expect
an answer.
However it was my thought exactly. N
Corinna Vinschen wrote:
> On Sep 1 09:56, Andreas Hauptmann wrote:
> > On Sat, 1 Sep 2018 01:24:49 +
> > Bryan Phelps wrote:
> >
> > > I'll continue to look around for a more minimal repro,
> >
> > The normalization of paths with backslashes has changed.
> >
> > The following doesn't work any
On Sep 1 09:56, Andreas Hauptmann wrote:
> On Sat, 1 Sep 2018 01:24:49 +
> Bryan Phelps wrote:
>
> > I'll continue to look around for a more minimal repro,
>
> The normalization of paths with backslashes has changed.
>
> The following doesn't work any longer:
>
> cd /tmp
> stat "..
Am 01.09.2018 um 10:10 schrieb Marco Atzeri:
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
Thank you for all the work on Cygwin! I've been using it to spin up
an environment to build the OCaml compiler / toolchain, and it was
working great.
However, today, all our CI builds mysterio
Marco Atzeri wrote:
> Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
> > Hello,
> >
> >
> > Thank you for all the work on Cygwin! I've been using it to spin up an
> environment to build the OCaml compiler / toolchain, and it was working great.
> >
> >
> > However, today, all our CI builds mysteriousl
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
Thank you for all the work on Cygwin! I've been using it to spin up an
environment to build the OCaml compiler / toolchain, and it was working great.
However, today, all our CI builds mysteriously started failing - at first, I
suspected it
Am 01.09.2018 um 03:24 schrieb Bryan Phelps:
Hello,
In the meantime - is there a way we can pin the cygwin package to the 2.10.0-1
version, to unblock our builds?
Thank you!
Bryan
What is the problem in installing the previous version of the package ?
---
Diese E-Mail wurde von Avast A
On Sat, 1 Sep 2018 01:24:49 +
Bryan Phelps wrote:
> I'll continue to look around for a more minimal repro,
The normalization of paths with backslashes has changed.
The following doesn't work any longer:
cd /tmp
stat "..\bin\file.exe" # or
stat "..\\bin\\file.exe"
This however s
Hello,
Thank you for all the work on Cygwin! I've been using it to spin up an
environment to build the OCaml compiler / toolchain, and it was working great.
However, today, all our CI builds mysteriously started failing - at first, I
suspected it was a problem with AppVeyor, but I also failur
20 matches
Mail list logo
