Thanks Marc!
Very valuable info. It seems not to be changed soon so a transfer to git would
be appreciated asap.
Stefan
--
Cloud Computing - Latest Buzzword or a Glimpse of the
Bug #4740 [1] deals with this, by the way.
http://bugzilla.qooxdoo.org/show_bug.cgi?id=4740
On 12/14/2011 12:42 PM, Marc Puts wrote:
> It's a known problem and it's caused by sourceforge which at times is
> very unstable. I don't think there's much the qooxdoo team can do about
> it, except f
It's a known problem and it's caused by sourceforge which at times is
very unstable. I don't think there's much the qooxdoo team can do about
it, except for moving away from sourceforge.
The best available workaround is the one mentioned by Omri --
downloading the contribs manually and use the
Thanks for your response Omri!
>It happened to me a few times as well. I simply re-ran the generator until it
>worked.
we did and do
>You can also, as a temporary fix, redefine your config.json to point to the
>locally acquired copy of the contribution...
We already have done, but we need to
It happened to me a few times as well. I simply re-ran the generator until it
worked.
You can also, as a temporary fix, redefine your config.json to point to the
locally acquired copy of the contribution...
Cheers,
Omri
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Connectio
This is a message we have received for 6 days now:
>>> Scanning libraries- Checking network-based contrib:
>>> contrib://qxe/trunk/Manifest.json
[Errno 104] Connection reset by peer
Problem must be solved as, if it occurs for others too, it stops all
development involving contributing sour
