Re: [Development] Backporting the Keccak change

2017-09-04 Thread Lars Knoll
> On 4 Sep 2017, at 14:12, Thiago Macieira wrote: > > On Monday, 4 September 2017 03:30:31 -03 Lars Knoll wrote: >> I think we should in any case also introduce the keccak enum values. I'm ok, >> if one of them aliases Sha3_512 (which we should then deprecate) and you >> add a new enum value for

Re: [Development] HEADS-UP: Branching from '5.6' to '5.6.3' completed

2017-09-04 Thread Thiago Macieira
On Monday, 4 September 2017 12:55:30 -03 Jani Heikkinen wrote: > Hi all, > > We have branched '5.6.3' from '5.6' today. All changes targeted to Qt 5.6.3 > release must be done in '5.6.3' and '5.6' is for Qt 5.6.4 from now on. And > as usual only release team will have staging rights in '5.6.3' Pl

[Development] HEADS-UP: Branching from '5.6' to '5.6.3' completed

2017-09-04 Thread Jani Heikkinen
Hi all, We have branched '5.6.3' from '5.6' today. All changes targeted to Qt 5.6.3 release must be done in '5.6.3' and '5.6' is for Qt 5.6.4 from now on. And as usual only release team will have staging rights in '5.6.3' br, Jani ___ Development mai

Re: [Development] Adding Qt CoAP

2017-09-04 Thread Thiago Macieira
On Monday, 4 September 2017 11:04:24 -03 jedrzej.nowa...@qt.io wrote: > True, but we can re-evaluate if it is not working, modularization is harder > in general as it requires some code changes. Regarding the "two weeks" > delay, it is mostly a social problem, as we can not agree on how often qt5 >

Re: [Development] Adding Qt CoAP

2017-09-04 Thread jedrzej . nowacki
On Monday, September 4, 2017 9:14:37 AM CEST Thiago Macieira wrote: > On Saturday, 2 September 2017 16:54:03 -03 Jędrzej Nowacki wrote: > > On piątek, 1 września 2017 08:38:19 CEST Thiago Macieira wrote: > > > I'm also wondering if we shouldn't have a bigger repo for IoT-related > > > things, inst

Re: [Development] Adding Qt CoAP

2017-09-04 Thread Thiago Macieira
On Saturday, 2 September 2017 16:54:03 -03 Jędrzej Nowacki wrote: > On piątek, 1 września 2017 08:38:19 CEST Thiago Macieira wrote: > > I'm also wondering if we shouldn't have a bigger repo for IoT-related > > things, instead of creating a small one for each thing. > > Currently, from CI and rele

Re: [Development] Backporting the Keccak change

2017-09-04 Thread Thiago Macieira
On Monday, 4 September 2017 03:30:31 -03 Lars Knoll wrote: > I think we should in any case also introduce the keccak enum values. I'm ok, > if one of them aliases Sha3_512 (which we should then deprecate) and you > add a new enum value for the correct Sha3 algorithm. Confirm your thinking, please.

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread Thiago Macieira
On Monday, 4 September 2017 05:19:18 -03 René J. V. Bertin wrote: > That bug report suggests only Qt performance is affected. But if I'm not > mistaken, Linux accessibility goes through the d-bus, and if that daemon is > being flooded other applications can suffer as well (cf. KMail4 > synchronisin

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread René J . V . Bertin
And one more thing: I haven't been seeing the issue I reported originally since getting rid of the ibus stuff as described earlier in this thread. Uninstalling at-spi2-core must have been the real fix as I installed ibus in one of my attempts to get a grip on the issue.

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread René J . V . Bertin
René J. V. Bertin wrote: >> QT_LINUX_ACCESSIBILITY_ALWAYS_ON > > Interesting, I have no trace of that variable, and I cannot imagine that > uninstalling at-spi2-core would have unset it in all running shells. In addition, the code only checks if this variable is set. You cannot do QT_LINUX_ACCES