On 2014-05-12 14:48, Peter Villeneuve wrote:
> Server is back up but indeed it seems the wheezy package wasn't built
>
> The requested URL
> /debian/pool/main/p/prosody-trunk/prosody-trunk_1nightly485-1~wheezy_amd64.deb
> was not found on this server.
The build environments needed some updates.
Server is back up but indeed it seems the wheezy package wasn't built
The requested URL
/debian/pool/main/p/prosody-trunk/prosody-trunk_1nightly485-1~wheezy_amd64.deb
was not found on this server.
On Mon, May 12, 2014 at 1:31 PM, Matthew Wild wrote:
> On 12 May 2014 13:28, Peter Villeneuve wr
On 12 May 2014 13:28, Peter Villeneuve wrote:
> No problem. By the way, I noticed the other days that recent builds weren't
> available for Wheezy but only Jessie and others.
> Is this latest one available for Wheezy amd64 too?
It should be available for all unless the builds fail for some reason
No problem. By the way, I noticed the other days that recent builds weren't
available for Wheezy but only Jessie and others.
Is this latest one available for Wheezy amd64 too?
On Mon, May 12, 2014 at 1:25 PM, Matthew Wild wrote:
> On 12 May 2014 13:19, Peter Villeneuve wrote:
> > No worries. T
On 12 May 2014 13:19, Peter Villeneuve wrote:
> No worries. Thanks for your effort.
> By the way, it seems that prosody.im is down.
Yes, sorry - system crash, it should be back shortly (within in an hour).
Regards,
Matthew
--
You received this message because you are subscribed to the Google G
No worries. Thanks for your effort.
By the way, it seems that prosody.im is down.
Best,
Peter
On Mon, May 12, 2014 at 3:22 AM, Matthew Wild wrote:
> On 11 May 2014 15:36, Peter Villeneuve wrote:
> > Hi Matthew,
> >
> > Is it available yet? I can't seem to find it.
>
> Really sorry Peter, for
On 11 May 2014 15:36, Peter Villeneuve wrote:
> Hi Matthew,
>
> Is it available yet? I can't seem to find it.
Really sorry Peter, for some unknown reason the commit hadn't
successfully pushed. I've done so now, and the builds should be done
in a few hours.
Regards,
Matthew
--
You received this
Hi Matthew,
Is it available yet? I can't seem to find it.
Cheers
On Sat, May 10, 2014 at 9:32 PM, Matthew Wild wrote:
> Hi Peter,
>
> On 10 May 2014 18:58, Peter Villeneuve wrote:
> > Any idea when the MUC issues will be resolved and pushed to trunk?
>
> I just pushed a fix, it should be in
Hi Matthew,
Thanks for the quick response.
I appreciate it.
Best,
Peter
On Saturday, May 10, 2014 9:32:34 PM UTC+1, Matthew Wild wrote:
>
> Hi Peter,
>
> On 10 May 2014 18:58, Peter Villeneuve >
> wrote:
> > Any idea when the MUC issues will be resolved and pushed to trunk?
>
> I just pushed
Hi Peter,
On 10 May 2014 18:58, Peter Villeneuve wrote:
> Any idea when the MUC issues will be resolved and pushed to trunk?
I just pushed a fix, it should be in the next nightly build (ready
about 6am UTC). Sorry for the delay and thanks for the report.
Regards,
Matthew
--
You received this
Hi Waqas,
Tried out yesterday's nightly build 484 (2014-05-09, 3942630b4e35) and I'm
still getting the MUC crash when using jitmeet.
May 10 17:31:44 mod_bosh error Traceback[bosh]:
/usr/lib/prosody/modules/muc/muc.lib.lua:172: attempt to call method
'get_child' (a nil value)
stack traceback:
/
Hi Waqas,
Thanks for the reply.
I tested out using ip4 and the problem remains. It's probably not a bosh
issue after all.
Perhaps it is the mod_muc after all. I'll wait until it's in the repo and
I'll try again.
Thanks,
Peter
On Thursday, May 8, 2014 11:30:23 PM UTC+1, Waqas wrote:
>
> On Thu
On Thu, May 8, 2014 at 3:57 PM, Peter Villeneuve wrote:
> Well I decided to remove Prosody and reinstall the 10 nightly debian
> package.
> Bosh doesn't crash now although I'm still having problems with a
> previously working setup.
>
> Have there been any major changes to mod_bosh or any other co
Well I decided to remove Prosody and reinstall the 10 nightly debian
package.
Bosh doesn't crash now although I'm still having problems with a previously
working setup.
Have there been any major changes to mod_bosh or any other core mods in
latest nightly?
Here's the error I'm now getting in n
14 matches
Mail list logo
