 (Photo, 806x335) https://i.imgur.com/HluyrWt.jpg
 @mitya57 you aware of anything such? ^
 I have a feeling some autotests failed with similar?
 In 5.14.2 I removed a patch that may be related.
 http://autopkgtest.ubuntu.com/packages/n/notepadqq/groovy/amd64
 tests failing with similar error
 https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/commit/e0bb0919ad7c7920dfdf59be36a2de6833cd72bf
 Also we are building with bundled ICU because Debian has an old version, in Ubuntu there is no such problem so maybe building with system ICU again will help.
 I have a groovy VM on another machine I can test any trial PPA build you might do
 @mitya57 [Interesting, vorlon reinstantiated the previous qtwebengine upload, I thought su …], copy-package takes any version as an argument
 And he's an AA so he has the powers
 @RikMills [I have a groovy VM on another machine I can test any trial PPA build you might d …], Will it be OK if I upload to the same PPA (4057)?
 Do you want to copy it to the archive from the PPA if it tests OK? if so, I think you will need a fresh ticket. If not, then should do no harm
 If it is one package then I can copy it manually.
 right. I have never tried that
 anyway, using that ppa should not steop us finalizing the ticket
 Uploaded.
 I wonder if I should have created a separate qml-module-qtqml package. Neon guys did not add it. And it breaks a few packages, e.g. kitemmodels.
 @RikMills what do you think?
 Looks like a separate .so file for that module was added as part of https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=43573c8df170c566
 I guess it makes sense as you did it
 I think...
 The documentation lists it as a separate module (https://doc.qt.io/qt-5/qtqml-qmlmodule.html) and I think it is possible to use QtQml without importing it, so maybe that was correct, yes.
 In that case kitemmodels tests need to depend on it (outside of autotests directory, it is not used).
 shall I upload that then?
 Yes, please
 done
 Thanks
 missing symbols for qtwebengine :(
 Oops
 Will fix in 15 minutes
 Done.
 @mitya57 https://bugreports.qt.io/browse/QTBUG-82589
 https://bugs.mageia.org/show_bug.cgi?id=26200
 Interesting that qtdiag prints the right path.
 But this is without usrmerge. Do you have it enabled?
 I guess so. This is a default install
 Let me try to build qtbase with `-no-feature-relocatable` in that PPA.
 Ok. Thanks!
 Uploaded.
 aha https://packaging.neon.kde.org/qt/qtbase.git/commit/debian/rules?h=Neon/release&id=2cbf7f4d5d1ea1496d76f0a159187af96b3401c3
 So this was the right change :)
 FWIW, I uploaded qcustomplot which should fix the autopkgtest failure.
[20:21] <fvogt> FYI, that's what upstream Qt recommends for system-wide installations anyway
 this change should fix notepadqq tests I hope
[20:22] <mitya57> fvogt: Thanks for confirming!
 @RikMills [this change should fix notepadqq tests I hope], Maybe you can already test how kontact behaves? Qtbase built on amd64
 @mitya57 [Maybe you can already test how kontact behaves? Qtbase built on amd64], I tried a few mins ago. Had not published the amd64 in the PPA yet
 "Finished 50 minutes ago" — hopefully should be published soon
 Looks like it just has!
 @mitya57 fixed!
 Great! I am copying it to archive then.
 Or better to wait until it builds on all architectures and copy with binaries? What do you think?
 I think either way, some arches will not be done until after midnight my time. and riscv64 took 8 hrs last time, so waiting to binary copy that means tomorrow
 so I think I would source copy or upload
 that way autotests will get queued overnight
 as they do not wait for riscv64 to be done
 Copied with existing binaries. Apparently it was possible :)
 really? nice
 I assumed that would fail. handy to know
 For arm and riscv64 new builds are started.
 ah. I think it errors when there are binaries, but they are not published in the source archive. that must be what failed for me once before
 Maybe.
 I have triggered kitemmodels retests
 and I will probably do some more looking in the morning
 Thanks!
 sadly we are are queued behind about 1.5 billion perl tests 🙄
 😱