Perfect, that worked! Thanks, Konstantin!
And thanks Thiago for explanation, too.
On Wed, 10 Oct 2018 at 21:43, Thiago Macieira wrote:
>
> On Wednesday, 10 October 2018 10:43:32 PDT Tomasz Siekierda wrote:
> > I'm on Kubuntu 18.10. I've made sure the ssh pub key on gerrit is
> > correct. And I'v
Hi all,
First beta release from Qt 5.12 is already out so it is time to start keeping
translatable strings as it is. And let's have official string freeze Fri 19th
October 2018.
br,
Jani
___
Development mailing list
Development@qt-project.org
http://l
On Wednesday, 10 October 2018 10:43:32 PDT Tomasz Siekierda wrote:
> I'm on Kubuntu 18.10. I've made sure the ssh pub key on gerrit is
> correct. And I've used init-repository script to get going.
>
> Does anybody know how to fix this? Most probably it's something stupid/
> trivial.
Most Linux di
Hi
Let's do a small maintenance break for the CI right away. It's quite unstable
currently, and a reset of all the hosts usually helps. While I do that, I'll
also enable nested virtual machines. This will enable a few things we are
working on.
-Tony
On Wed, Oct 10, 2018 at 8:43 PM Tomasz Siekierda wrote:
> Hi,
> I'm on Kubuntu 18.10. I've made sure the ssh pub key on gerrit is
> correct. And I've used init-repository script to get going.
>
Hi,
Ran into this a few months ago. Force the cipher through the ssh config and
you should get it goin
Hi,
it's been a while since I've last pushed to gerrit. I'm getting this:
$ git push gerrit HEAD:refs/for/dev
Unable to negotiate with 54.229.21.112 port 29418: no matching cipher
found. Their offer: aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc
fatal: Could not read from remote repository.
Plea