On Thu, Dec 13, 2012 at 05:10:09PM +0100, Adam GROSZER wrote:
> On 12/13/2012 04:15 PM, Tres Seaver wrote:
> >On 12/13/2012 04:45 AM, Adam GROSZER wrote:
> >>Let's put the blame on windows. A process got stuck on winbot, so it
> >>could not release the binaries. Now I kicked it and all should be
>
On 12/13/2012 04:15 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2012 04:45 AM, Adam GROSZER wrote:
Let's put the blame on windows. A process got stuck on winbot, so it
could not release the binaries. Now I kicked it and all should be
fine.
Was the wedged proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2012 04:45 AM, Adam GROSZER wrote:
> Let's put the blame on windows. A process got stuck on winbot, so it
> could not release the binaries. Now I kicked it and all should be
> fine.
Was the wedged process also blocking test runners? I haven
On 12/13/2012 12:30 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/2012 04:12 PM, Roger wrote:
I guess the peristent release is broken. At least with my windows
minsys setup. (I don't use cygwin)
Should this work or does persistent require a special build setup?
On Dec 13, 2012, at 0:30 , Tres Seaver wrote:
>> Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. cc1.exe:
>> error: unrecognized command line option '-mno-cygwin' error: Setup
>> script exited with error: command 'gcc' failed with exit status 1 An
>> error occurred when trying to instal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/2012 04:12 PM, Roger wrote:
> I guess the peristent release is broken. At least with my windows
> minsys setup. (I don't use cygwin)
>
> Should this work or does persistent require a special build setup?
>
>
> bin\buildout.exe Develop:
>
