[neon/qt/qtdeclarative/Neon/testing] debian: try to undo explicit target ordering

Neon CI null at kde.org
Tue May 18 12:20:49 BST 2021


Git commit 1288580811c86fb06f65a86f4c67478d6cf9e5f3 by Neon CI.
Committed on 18/05/2021 at 11:19.
Pushed by sitter into branch 'Neon/testing'.

try to undo explicit target ordering

there is a change in the recent merge that seems to want to solve this as
well and since the build now fails I'm guessing the two approaches are
mutually exclusive. in any event since qmake is falling over randomly...
again... I do not know what to do other than randomly applying hacks... again

M  +1    -6    debian/rules

https://invent.kde.org/neon/qt/qtdeclarative/commit/1288580811c86fb06f65a86f4c67478d6cf9e5f3

diff --git a/debian/rules b/debian/rules
index 3f682ba..1ba8461 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,12 +21,7 @@ override_dh_auto_clean:
 override_dh_auto_configure:
 	dh_auto_configure -- QT_BUILD_PARTS+=tests QMAKE_PYTHON=python3
 
-# run the bin-only target first. there appears to be a bug with qmake incorrectly producing
-# target dependencies when first running make docs and then make all
-# specifically the *qmltyperegistrations.cpp do not get generated which is where registration
-# symbols would be defined so they are then missing from the library as a whole
-# https://forum.qt.io/topic/114188/qt-5-15-undefined-symbol
-override_dh_auto_build-indep: build-arch
+override_dh_auto_build-indep:
 	dh_auto_build -- docs
 
 override_dh_auto_build-arch:


More information about the Neon-commits mailing list