Re: [Development] New git mirror - http://code.qt.io
On Tue, Feb 24, 2015 at 12:54:48PM +, Hirvonen Olli wrote: Hi, We have installed a new read-only git mirror under qt.io domain (http://code.qt.io). The purpose of this git mirror is to act as a authoritative git mirror for Qt sources, and we plan to change links on our own web pages to it where applicable. The new service does not have impact to existing mirrors such as GitHub (https://github.com/qtproject) and Gitorious (http://qt.gitorious.org/), but we want to have our own mirror under qt.io domain as well. This is nice, but there is something else that could be even more beneficial. If you guys could sign tags that would be even more authoritative than a dedicated git. For example, in QtCreator's repository, $ git tag -v v3.3.1 object 567c6eb8759436a94835d06cf209956229265220 type commit tag v3.3.1 tagger Eike Ziller eike.zil...@theqtcompany.com 1424783381 +0100 Qt Creator v3.3.1 error: no signature found error: could not verify the tag 'v3.3.1' A signed tag automatically verifies the entire history as being authentic (up to the tag). - Adam PS. GPG signed releases would also be nice in addition to simple hash checksums. For example, one file with ALL hashes that is then signed would verify these hashes (and all releases) as authentic. -- Adam Majer ad...@zombino.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] CI failing due to tst_licenses.pl test
Hi, Since nobody else has replied to this yet, my understanding of what happened with license checks is roughly as follows. I was not involved, so YMMV - this is all just gained from observation of what's happened - someone else please correct me if I'm wrong. a) someone, somewhere, made a decision to change license headers (I don't know where this discussion happened, at least I don't recall this happening on-list) b) tst_licenses (or was it all qtqa tests?) were disabled, presumably to allow a) to happen c) license headers were changed, without checking that they actually passed the test d) license checks were reenabled, making everything fail e) 5.5 got branched without this having been fixed f) licenses were changed (again) in dev, fixing the tests g) finally, dev was merged back down to 5.5 to fix the failures there By my count, there's a few failures here: * it would have been nice to have a heads up about the headers change. * disabling license checks to update headers seems to have been a pretty terrible idea * branching 5.5 before fixing that seemed to create a lot of additional confusion, especially without any real communication about what was going on with all of these issues The situation is - I think - almost back to normal, bar some modules that aren't part of releases. Robin On Mon, Feb 23, 2015 at 3:17 AM, Aaron McCarthy mccarthy.aa...@gmail.com wrote: Hi, Changing are failing to integrated because the license header used by the tst_licenses.pl test does not match the existing headers in the source. Errors like the following are seen: # Failed test 'Mismatch in license text in examples/qml/dynamicscene/content/Button.qml # Actual: * Neither the name of The Qt Company Ltd and its Subsidiary(-ies) nor the # Expected: * Neither the name of The Qt Company Ltd nor the names of its' # at /work/build/_qtqa_latest/tests/prebuild/license/tst_licenses.pl line 389. Cheers, -- Aaron McCarthy ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New git mirror - http://code.qt.io
On Tuesday 24 February 2015 14:01:39 Adam Majer wrote: A signed tag automatically verifies the entire history as being authentic (up to the tag). - Adam PS. GPG signed releases would also be nice in addition to simple hash checksums. For example, one file with ALL hashes that is then signed would verify these hashes (and all releases) as authentic. We can consider that for new releases. The next upcoming release is 5.5 alpha. -- 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] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.
How did you configure it? Did you run configure.bat? Regards, Konstantin 2015-02-24 10:42 GMT+04:00 Gunnar Roth gunnar.r...@gmx.de: Hello, i am trying to build qt5.5 from git on windows . i do not want to make a deveolper build but want to build the code as i normally do. After creating the configure.exe, configureing and starting the build, qtcore build fails because it cannot find headers, which normally reside in qtbase\include but this is completely missing in the git src code. what do i need to do to create the source code in a form like it is in released tar.gz files? Thank you in advance, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.
Yes, as i wrote After creating the configure.exe, configuring [..] from the log: Starting Qt configuring for win32-vs11-32 + cd qtbase + C:RTILSharedQt5.5.0qt-srcqtbaseconfigure.bat -top-level -prefix C:RTILSharedBinQt5.5.0WIN32-VS11-32 -platform win32-msvc2012 -debug-and-release -rtti -force-debug-info -mp -ltcg -qtlibinfix RTIL -opensource -confirm-license -nomake examples -nomake tests -system-libjpeg -opengl dynamic -directwrite -direct2d Regards, Gunnar Gesendet:Dienstag, 24. Februar 2015 um 09:56 Uhr Von:Konstantin Ritt ritt...@gmail.com An:Gunnar Roth gunnar.r...@gmx.de Cc:development@qt-project.org development@qt-project.org Betreff:Re: [Development] trying to build qt 5.5 git branch. Missing qtbaseinclude dir and content. How did you configure it? Did you run configure.bat? Regards, Konstantin 2015-02-24 10:42 GMT+04:00 Gunnar Roth gunnar.r...@gmx.de: Hello, i am trying to build qt5.5 from git on windows . i do not want to make a deveolper build but want to build the code as i normally do. After creating the configure.exe, configureing and starting the build, qtcore build fails because it cannot find headers, which normally reside in qtbaseinclude but this is completely missing in the git src code. what do i need to do to create the source code in a form like it is in released tar.gz files? Thank you in advance, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] HEADS UP: Qt5.5. branching complete
Hi all! Qt 5.5 branching is now complete. It means 'dev' branch is for Qt 5.6 release and all changes targeted to Qt5.5 must be done in '5.5' branch. Ossi is still taking re-targeting requests from 'dev' to '5.5' if some change currently in 'dev' should be in Qt 5.5. Next milestone now is Qt5.5 Alpha. We are trying to create Qt5.5 Alpha packages release Alpha as soon as possible. So please inform me immediately if there is some changes which must be in Alpha but which aren't merged in '5.5'branch yet br, Jani Lähettäjä: Heikkinen Jani Lähetetty: 16. helmikuuta 2015 15:04 Vastaanottaja: development@qt-project.org Kopio: releas...@qt-project.org Aihe: HEADS UP: Qt5.5. branching started Hi all, Qt5.5 feature freeze branching period is now ongoing. '5.5' branch is created you should start using it for the changes targeted to Qt5.5 release. Again we will use 'soft branching' scheme like we did with 5.4.0. Downmerge from 'dev' to '5.5' will happen next Monday (23rd Feb) so there should be enough time to finalize ongoing changes in 'dev' start using '5.5'. After downmerge next Monday 'dev' branch will be for '5.6' release. As usual Ossi is taking re-targeting requests from 'dev' to '5.5' as well. br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qtbase 5.5 branch is blocked
On Tuesday 24 February 2015 07:43:47 Heikkinen Jani wrote: Hi all, If I have understood correctly merge from 'dev' to '5.5' should solve this issue. Or does someone disagree? It could be that a commit which somehow integrated to 5.5 is causing the failure. There is only a few commit in 5.5 that are not in dev. A candidate, looking at the failure, could be 2f5c2ec12f3c45a0806b5872c206a680e9fce014, but i have no idea. The way to solve this would be to investigate: try to reproduce the failure and see why it fails. This could very well be a real regression. But yes, you can also try to merge dev into 5.5 and see if it passes. -- Olivier Woboq - Qt services and support - http://woboq.com - http://code.woboq.org ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.
I now started all over, i can find qt-srcqtbaseincludeQtCore now. But build fails with cl -c -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -D_HAS_EXCEPTIONS=0 -MP -GR -GL -W3 -w34100 -w34189 -w44996 /Fd..libQt5BootstrapRTIL.pdb -DUNICODE -DWIN32 -DQT_BOOTSTRAPPED -DQT_LITE_UNICODE -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS -DQT_NO_DATASTREAM -DQT_NO_LIBRARY -DQT_NO_QOBJECT -DQT_NO_SYSTEMLOCALE -DQT_NO _THREAD -DQT_NO_UNICODETABLES -DQT_NO_USING_NAMESPACE -DQT_NO_DEPRECATED -DQT_NO_TRANSLATION -DQT_QMAKE_LOCATION=C:/RTIL/Shared/Qt/5.5.0/bld/WIN32-VS11-32/qtb ase/bin/qmake -DQT_CRYPTOGRAPHICHASH_ONLY_SHA1 -DQT_NO_CAST_FROM_ASCII -DQT_BUILD_BOOTSTRAP_LIB -DQT_BUILDING_QT -D_CRT_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -DQT_NO_EXCEPTIONS -DQT_NO_DE BUG -DNDEBUG -IC:RTILSharedQt5.5.0qt-srcqtbasesrctoolsbootstrap -I. -IC:RTILSharedQt5.5.0qt-srcqtbasesrc3rdpartyzlib -IC:RTILSharedQ t5.5.0qt-srcqtbaseinclude -IC:RTILSharedQt5.5.0qt-srcqtbaseincludeQtCore -IC:RTILSharedQt5.5.0qt-srcqtbaseincludeQtXml -IC:RTILShare dQt5.5.0qt-srcqtbaseincludeQtCore5.5.0 -IC:RTILSharedQt5.5.0qt-srcqtbaseincludeQtCore5.5.0QtCore -IC:RTILSharedQt5.5.0qt-srcqtbasein cludeQtXml5.5.0 -IC:RTILSharedQt5.5.0qt-srcqtbaseincludeQtXml5.5.0QtXml -I..include -I..includeQtCore -IC:RTILSharedQt5.5 .0bldWIN32-VS11-32qtbaseincludeQtXml -Itmp -IC:RTILSharedQt5.5.0qt-srcqtbasemkspecswin32-msvc2012 -Fo.objrelease @C:Usersadrogu1AppDataL ocalTempqdom.obj.6168.17472.jom qdom.cpp C:RTILSharedQt5.5.0qt-srcqtbasesrcxmldomqdom.cpp(35) : fatal error C1083: Cannot open include file: qdom.h: No such file or directory thats would be inqt-srcqtbaseincludeQtXml but does not exist. i also see now that this isQt5BootstrapRTIL which is being build. but still got no clue whats wrong actually. Regards, Gunnar Gesendet:Dienstag, 24. Februar 2015 um 10:34 Uhr Von:Gunnar Roth gunnar.r...@gmx.de An:Konstantin Ritt ritt...@gmail.com Cc:development@qt-project.org development@qt-project.org Betreff:Re: [Development] trying to build qt 5.5 git branch. Missing qtbaseinclude dir and content. Yes, as i wrote After creating the configure.exe, configuring [..] from the log: Starting Qt configuring for win32-vs11-32 + cd qtbase + C:RTILSharedQt5.5.0qt-srcqtbaseconfigure.bat -top-level -prefix C:RTILSharedBinQt5.5.0WIN32-VS11-32 -platform win32-msvc2012 -debug-and-release -rtti -force-debug-info -mp -ltcg -qtlibinfix RTIL -opensource -confirm-license -nomake examples -nomake tests -system-libjpeg -opengl dynamic -directwrite -direct2d Regards, Gunnar Gesendet:Dienstag, 24. Februar 2015 um 09:56 Uhr Von:Konstantin Ritt ritt...@gmail.com An:Gunnar Roth gunnar.r...@gmx.de Cc:development@qt-project.org development@qt-project.org Betreff:Re: [Development] trying to build qt 5.5 git branch. Missing qtbaseinclude dir and content. How did you configure it? Did you run configure.bat? Regards, Konstantin 2015-02-24 10:42 GMT+04:00 Gunnar Roth gunnar.r...@gmx.de: Hello, i am trying to build qt5.5 from git on windows . i do not want to make a deveolper build but want to build the code as i normally do. After creating the configure.exe, configureing and starting the build, qtcore build fails because it cannot find headers, which normally reside in qtbaseinclude but this is completely missing in the git src code. what do i need to do to create the source code in a form like it is in released tar.gz files? Thank you in advance, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qtbase 5.5 branch is blocked
Hi, there is https://bugreports.qt.io/browse/QTBUG-44434 describing the issue, but there does not seem to be a conclusion yet. It is unlikely that the issue is fixed by the merge or goes away magically; it would be appreciated if the accessibilty experts could take a look. Regards, Friedemann -- Friedemann Kleint | The Qt Company ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Questions about code reviews and static analysis tools for TU Delft research
Hi everyone, I'm doing research on code reviews and static analysis tools at the SERG group (http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of Technology. Currently, we want to give an overview of the usage of code review and static analysis tools in open source projects. Therefore, I would be very happy to know a little bit more about how code reviews are used in Qt and if (and maybe how) static analysis tools are used. I have a couple of questions for anyone willing to answer: 1. Do all developers (contributors and core developers) have to submit a code review for every change? I’m asking because many projects only review changes made by contributors. 2. Which code review tools are used? 3. Are static analyzers used? If they are used: a. Is passing the checks of the static analyzers necessary for a change to be accepted? b. Which static analyzers are used? Thanks, Radjino ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Proposal: Deprecating platforms in Qt 5.6 that don't support lambda
On Feb 20, 2015, at 10:04 AM, André Somers an...@familiesomers.nl wrote: Bo Thorsen schreef op 20-2-2015 om 09:03: Andrés question about how this would change the API is a lot more interesting. I so far haven't seen a single case where someone has described how access to lambdas might improve the API. Well, the new connect style is also already improved API. If they are there, I'd love to see them, because maybe this would teach me something I haven't figured out yet. One example I could come up with as a potential new API is QSortFilterProxyModel. Currently, it requires subclassing to change the sort or the filter functions: it supplies protected filterAcceptsRow, filterAcceptsColumn and lessThan functions. I think that it would be much more convenient if these filters and the comparator could be supplied as a function object (a lambda, or a functor, or a std::mem_fn, anything callable as a function). While this wasn't all that practical in the past, I think C++/11 makes this much more convenient than subclassing. We start using these kind of patterns more and more in Qt Creator. Another example in Qt might be virtual QWebView * QWebView::createWindow(QWebPage::WebWindowType type) [protected] which could instead be a setWindowFactory function (same in QWebEngine). This could of course just be added, instead of replacing. But that would mean API bloat. Downside of replacing is of course: you break old code. I think that if we go over the Qt classes, we'll find more examples of where a subclass or a separate function that you need to write could be replaced with a more modern API. André ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller, Senior Software Engineer - The Qt Company GmbH The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5.4.1 Qt Creator 3.3.1 released
Hi all, We are happy to announce that Qt 5.4.1 Qt Creator 3.3.1 is released today, see http://blog.qt.io/blog/2015/02/24/qt-5-4-1-released/ http://blog.qt.io/blog/2015/02/24/qt-creator-3-3-1-released/ Big thanks to everyone who have helped to make the releases happen! Br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] ot: qt development information
Hi, the short and simple answer is no. The current version of the Qt Visual Studio Add-In only supports Qt 5.x. On 2/24/2015 15:42, Alessio Mochi wrote: I would like know if exist an integration plugin for vs2013 that work with qt 4.8. Thanks. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QStandardPaths could be helpful for cross platform portability, Qt Everywhere
On 24 Feb 2015, at 07:24, Jeremy Whiting jpwhit...@kde.org wrote: Hello list, I discussed a bit with Thiago and some others on irc this evening and have realized that the QStandardPaths patch from [1] and discussion on [2] is trying to solve too many problems at once. I'll list the problems here and some possible solutions to these problems afterwards so we can discuss what are appropriate/purposeful fixes to the problems and get these issues fixed. Thoughts, opinions, counterarguments, suggestions? (Disclaimer: I know little about KDE frameworks internals) On OS X (and iOS): place the resources in he framework bundle for the component that owns them. Add public API to the component for accessing the resources. Installers and deployment utilities can then move the framework bundles as needed, for example to a shared location for a “system” installation, or to the applicaiton bundle to create a stand-alone, sandboxable app. Thanks for the writeup! I find sharing the big picture like this very useful. Morten ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] ot: qt development information
I would like know if exist an integration plugin for vs2013 that work with qt 4.8.Thanks. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QStandardPaths could be helpful for cross platform portability, Qt Everywhere
On Tuesday 24 February 2015 13:47:53 Sorvig Morten wrote: On OS X (and iOS): place the resources in he framework bundle for the component that owns them. Add public API to the component for accessing the resources. Agreed. That means libraries that get installed as frameworks should simply carry their private data inside their bundle. That makes it a lot easier to move, remove, and update the framework. Installers and deployment utilities can then move the framework bundles as needed, for example to a shared location for a “system” installation, or to the applicaiton bundle to create a stand-alone, sandboxable app. Yep. However, I don't think that's sufficient. It misses two important use-cases: 1) non-framework libraries 2) libraries (framework or not) accessing global resources installed by global package management Both cases still require finding unbundled data. Thanks for the writeup! I find sharing the big picture like this very useful. -- 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] trying to build qt 5.5 git branch. Missing qtbase\include dir and content.
On Tuesday 24 February 2015 07:42:16 Gunnar Roth wrote: Hello, i am trying to build qt5.5 from git on windows . i do not want to make a deveolper build but want to build the code as i normally do. After creating the configure.exe, configureing and starting the build, qtcore build fails because it cannot find headers, which normally reside in qtbase\include but this is completely missing in the git src code. what do i need to do to create the source code in a form like it is in released tar.gz files? How did you obtain the source code? If you used git clone, this should not be happening. If you used git archive or downloaded an archive from the web interfaces, then this is the root cause. Create a directory called .git inside qtbase to fool the Qt buildsystem into thinking you have a clone. -- 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] QStandardPaths could be helpful for cross platform portability, Qt Everywhere
On Monday 23 February 2015 23:24:07 Jeremy Whiting wrote: A second solution is to add some API to QStandardPaths to modify the paths at run time. This would allow libraries to add paths to QStandardPaths' standard paths that it needs in its initialization methods. For example a library that requires data files that it knows are installed to /some/path can add /some/path to the GenericDataLocation via something like QStandardPaths::addCustomPath(GenericDataLocation, /some/path) and it's subsequent calls to QStandardPaths::locate(GenericDataLocation, somedatafile) would get the file required. Hi Jeremy Thanks for the write up, it's appreciated. I'm wondering if the above should be a global config or if we should make QStandardPaths support creating an object that a library could use internally. If we choose the latter, a library could set up its own, private search paths and not bother anyone else. Another similar option would be to always add relative paths based on the application binary or library (or both) so libraries installed inside a .app bundle on OS X could find the data files that are also inside the .app bundle. This way binaries on Windows could also find data files and libraries relative to the installation path of the executable itself, so if end users install MyProgram into D:\Some\Path\Myprogram, and the installer puts the data files beneath that, QStandardPaths api could find the data files wanted. Indeed, we need that. For Qt itself, we have QLibraryInfo, but the installation prefix is usually hardcoded. For Mac, Linux and Windows, I think we have good solutions for determining the installation path of a library given a pointer located inside it, so we should really investigate relocatable builds and adapt both QLibraryInfo and QStandardPaths. -- 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] QStandardPaths could be helpful for cross platform portability, Qt Everywhere
Jeremy Whiting wrote: One solution is to use/support XDG_*_DIRS environment variables on all platforms. This has one advantage in that the same tools can be used on all platforms to customize the paths given by the standard. This is ok for developers working on software, but not the best idea for shipping actual software to end users since setting environment variables is not often easy or advisable and has other effects. Note this is the approach of the patch in gerrit, but it's a non-solution because of the above mentioned issues. Still, I don't understand the strong resistance to implementing this. Supporting XDG_* everywhere helps portability and does not hurt the non-freedesktop.org platforms in any way. If the user doesn't use those environment variables, then nothing changes at all. Kevin Kofler ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QStandardPaths could be helpful for cross platform portability, Qt Everywhere
On Wednesday 25 February 2015 00:44:49 Kevin Kofler wrote: Jeremy Whiting wrote: One solution is to use/support XDG_*_DIRS environment variables on all platforms. This has one advantage in that the same tools can be used on all platforms to customize the paths given by the standard. This is ok for developers working on software, but not the best idea for shipping actual software to end users since setting environment variables is not often easy or advisable and has other effects. Note this is the approach of the patch in gerrit, but it's a non-solution because of the above mentioned issues. Still, I don't understand the strong resistance to implementing this. Supporting XDG_* everywhere helps portability and does not hurt the non-freedesktop.org platforms in any way. If the user doesn't use those environment variables, then nothing changes at all. The resistance is understanding why it's needed. Other platforms haven't needed this, so we have to answer the question of why we need to add it. People are asking: shouldn't apps and libs instead adapt to the OS in question? First and foremost, as Jeremy said, QSP is lacking functionality even for the standard way of doing things on those OS. Second, there's also the question of unmodified Unix libraries and shared, global resources. Given this latter argument, I think we will have to implement the XDG variables. -- 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] CI failing due to tst_licenses.pl test
On 25 Feb 2015, at 7:20 am, Robin Burchell robin...@viroteck.net wrote: Hi, Since nobody else has replied to this yet, my understanding of what happened with license checks is roughly as follows. I was not involved, so YMMV - this is all just gained from observation of what's happened - someone else please correct me if I'm wrong. a) someone, somewhere, made a decision to change license headers (I don't know where this discussion happened, at least I don't recall this happening on-list) b) tst_licenses (or was it all qtqa tests?) were disabled, presumably to allow a) to happen c) license headers were changed, without checking that they actually passed the test d) license checks were reenabled, making everything fail e) 5.5 got branched without this having been fixed f) licenses were changed (again) in dev, fixing the tests g) finally, dev was merged back down to 5.5 to fix the failures there By my count, there's a few failures here: * it would have been nice to have a heads up about the headers change. * disabling license checks to update headers seems to have been a pretty terrible idea * branching 5.5 before fixing that seemed to create a lot of additional confusion, especially without any real communication about what was going on with all of these issues The situation is - I think - almost back to normal, bar some modules that aren't part of releases. Surely those unreleased modules would need to have/get updated licenses as well, seeing as someone most likely has a patch or script available to do so on numerous files recursively. I know that the license headers in QtSystem are 3 years out of date... I imagine other unreleased modules are as well. Robin On Mon, Feb 23, 2015 at 3:17 AM, Aaron McCarthy mccarthy.aa...@gmail.com wrote: Hi, Changing are failing to integrated because the license header used by the tst_licenses.pl test does not match the existing headers in the source. Errors like the following are seen: # Failed test 'Mismatch in license text in examples/qml/dynamicscene/content/Button.qml # Actual: * Neither the name of The Qt Company Ltd and its Subsidiary(-ies) nor the # Expected: * Neither the name of The Qt Company Ltd nor the names of its' # at /work/build/_qtqa_latest/tests/prebuild/license/tst_licenses.pl line 389. Cheers, -- Aaron McCarthy ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
