Re: [Development] [Releasing] brown paper bag issue in Qt 5.6.1 packages
On sexta-feira, 24 de junho de 2016 08:50:01 PDT Thiago Macieira wrote: > I disagree. This problem is going to affect Support a lot more, as it will > be difficult to get the actual version number from people. When customers > come for support and say they have 5.6.1, Support will have to tell the > customer "please re-download and install the new version" because they > won't be sure that the customer didn't download the old version last week. > > As for support on the IRC channel and mailing list,s if we don't change the > .qmake.conf file, I will simply tell people to *downgrade* to 5.6.0 or wait > for 5.6.2. Think of packagers that don't pay that good an attention to this > mailing list. They may not realise that it's a different version and may > simply call it 5.6.1. On IRC just now: 20:59 < nurupo> what does "-1" in "5.6.1-1" mean? 21:00 < nurupo> it always was major.minor.patch, with the API/ABI compatibility relation between them well defined 21:00 < nurupo> but suddenly there is this "-1" -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] brown paper bag issue in Qt 5.6.1 packages
On sexta-feira, 24 de junho de 2016 08:51:51 PDT Thiago Macieira wrote: > On sexta-feira, 24 de junho de 2016 10:26:37 PDT Tuukka Turunen wrote: > > Hi, > > > > I do not know why 5.6.1 has been deleted, but it is of course a mistake. > > However, we need to make sure no-one accidentally takes it, so maybe > > moving > > to archive is good approach? > > No, keep it in http://download.qt.io/official_releases/qt/5.6/, since it's > an official release. Source code is enough though, we don't need the > binaries. > > The solution for "make sure no one accidentally takes it" is to name the > other release 5.6.2... Files are still not back yet. I've created a P0 task for the release team. Please solve this Monday. https://bugreports.qt.io/browse/QTBUG-54351 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Qt-creator] [OS X] Dock icon progress widget
Thiago Macieira wrote: > On sexta-feira, 24 de junho de 2016 18:12:25 PDT René J. V. Bertin wrote: >> The remark above did make me wonder if QtDBus couldn't use a >> platform-native backend transparently. It seems unlikely (just as you >> probably cannot replace dbus itself by something that isn't ... dbus) but >> it cannot hurt to ask :) > What do you mean by that? What is a "platform-native backend"? Something that uses the platform's native desktop bus, as far as something like that exists. > How would it be used transparently? If 2 applications communicate via QtDBus calls it doesn't really matter what QtDBus does, it hides the implementation details. Instead of a daemon there could be an angel that handles the communication ;) > And more importantly, what is any of that different than > what QtDBus does right now? Well, that's the main point, isn't it. Replacing dbus by something that does the same thing almost the same way only in order to avoid using dbus doesn't make a lot of sense. I wasn't wondering aloud how we could do something completely different, but rather what could be improved to make dbus a true cross-platform daemon-based desktop bus service that cannot be accused of being a fish out of the water. R ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Push to Gerrit
Hi Harald, often on Windows it's easiest to install PuTTy and it's helper program, pageant. Run pageant and import/convert your ssh key and set this up in your gerrit webui. Cheers, Sean On 25/06/2016 16:06, Harald Vistnes wrote: Hi, I'm trying to make my first ever contribution to Qt, but I am struggling with the last part of actually pushing to Gerrit. I've followed the guidelines in the Wiki, but I have probably done something wrong. I've added and committed the patch locally, but when I try to run git push gerrit HEAD:refs/for/5.7 I get a popup messagebox: TortoiseGitPlink Fatal Error Disconnected: No supported authentication methods available (server sent: publickey) I'm on Windows. I assume the problem is related to the ssh keys. Any hints on how to continue would be welcome. Thanks, Harald Vistnes ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK KDAB (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090 Mobile: +44 (0)7545 140604 KDAB - Qt Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Push to Gerrit
Hi, I'm trying to make my first ever contribution to Qt, but I am struggling with the last part of actually pushing to Gerrit. I've followed the guidelines in the Wiki, but I have probably done something wrong. I've added and committed the patch locally, but when I try to run git push gerrit HEAD:refs/for/5.7 I get a popup messagebox: TortoiseGitPlink Fatal Error Disconnected: No supported authentication methods available (server sent: publickey) I'm on Windows. I assume the problem is related to the ssh keys. Any hints on how to continue would be welcome. Thanks, Harald Vistnes ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
