Nope. The packages go in testing repo after some testing is done,
apparently, this failed I need to check why is that.
Our ci had some free space issues, which were affecting the pr-testing
and those are now fixed.
Thanks you very much. When the new package is available I will do a
test, but I have already tried with meet.jit.si and the fix seems to work.
I think I was not seeing the new versions of the packages because the
host was automatically running an "aptitude update" (I've already
disabled this). Then I found this available updates:
jicofo [1.0-386-1 -> 1.0-388-1]
jitsi-meet [1.0.2625-1 -> 1.0.2645-1]
jitsi-meet-prosody [1.0.2434-1 -> 1.0.2450-1]
jitsi-meet-web [1.0.2434-1 -> 1.0.2450-1]
jitsi-meet-web-config [1.0.2434-1 -> 1.0.2450-1]
jitsi-videobridge [1010-1 -> 1013-1]
The update of these versions of jitsi-meet solved the problem with
Chromium (although I don't know if the fix was introduced in this
version or maybe a previous one). Thank you very much.
By the way, is it possible that this version also includes a fix for
this ? It seems that now I'm not having that problem in Chromium but
I'm not sure if this is because I cleaned the cache, because you
introduced a fix, or just because it does not always happen (it seems to
be due to a race condition if I understood correctly what Leonard told me).
On 16/11/17 11:48, Daniel Bareiro wrote: