On 10.08.2016 23:18, Lorn Potter wrote:
Hello,
Is there someone who has a script for updating license headers that can
release this, or make it known? Or, alternatively, update the license
headers or make the license test not run on non supported modules for
integrations?

to exclude it, add your module here:

http://code.qt.io/cgit/qt/qtqa.git/tree/tests/prebuild/license/tst_licenses.pl#n70

Trying to upstream some stuff:

Module "qt/qtsystems" (a1509631b047285239fcadbcf44d425d94e329d0) Failed
test(s): license:
 agent:2016/08/10 13:16:31 build.go:298: Executing instruction 13 of 13
 agent:2016/08/10 13:16:31 build.go:321: [perl
qt/qtqa-latest/tests/prebuild/license/tst_licenses.pl]  1200
 1..252
 ok 1 - config.tests/bluez/main.cpp
 ok 2 - config.tests/gconf/main.cpp
 ok 3 - config.tests/mir/main.cpp
 ok 4 - config.tests/udev/main.cpp
 ok 5 - config.tests/x11/main.cpp
 Old license being used for
doc/src/publishsubscribe/examples/battery-charge.qdoc.
 ok 6 - doc/src/publishsubscribe/examples/battery-charge.qdoc
 Old license being used for
doc/src/publishsubscribe/examples/examples-publishsubscribe.qdoc.

probably using http://code.qt.io/cgit/qt/qtbase.git/tree/header.BSD-OLD?h=dev instead of http://code.qt.io/cgit/qt/qtbase.git/tree/header.BSD?h=dev

Also, What exactly does this mean? These are new files. Where is the
reference text to use?

eg:
http://code.qt.io/cgit/qt/qtbase.git/tree/header.LGPL?h=dev

 not ok 69 - License text and reference text have different number of
lines in src/imports/systeminfo/qdeclarativeinputdevicemodel.cpp
 #   Failed test 'License text and reference text have different number
of lines in src/imports/systeminfo/qdeclarativeinputdevicemodel.cpp'
 #   at qt/qtqa-latest/tests/prebuild/license/tst_licenses.pl line 395.

yours has 41 lines and the reference only 38
http://code.qt.io/cgit/qt/qtbase.git/tree/header.LGPL?h=dev


thanks-
Lorn




--
Sergio Ahumada
[email protected]

_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to