[00:03] -queuebot:#ubuntu-qt- New binary: qtwayland-opensource-src [ppc64el] (hirsute-proposed/universe) [5.15.1-3] (kubuntu, qt5)
[00:06] -queuebot:#ubuntu-qt- New binary: qtwayland-opensource-src [amd64] (hirsute-proposed/universe) [5.15.1-3] (kubuntu, qt5)
[00:06] -queuebot:#ubuntu-qt- New binary: qtwayland-opensource-src [s390x] (hirsute-proposed/universe) [5.15.1-3] (kubuntu, qt5)
 @RikMills [@tsimonq2 I think the ticket publishing from bileto worked, but please double ch …], Looking
[01:07] -queuebot:#ubuntu-qt- New binary: qtwayland-opensource-src [arm64] (hirsute-proposed/universe) [5.15.1-3] (kubuntu, qt5)
[01:38] -queuebot:#ubuntu-qt- New binary: qtwayland-opensource-src [armhf] (hirsute-proposed/universe) [5.15.1-3] (kubuntu, qt5)
 Thank you @tsimonq2! All looks fine from the first sight.
 Thank you all! I see that WebKit copied fine :)
 Oh, qtwebengine also needs ruby :(
 good morning
 what's the deal with ruby?
 @Santa [what's the deal with ruby?], Morning! There is a dependency loop between ruby and ruby-rubygems, so neither is installable.
 https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.15.1+dfsg-5/+build/20219754
 Oh, qt3d needs link with -latomic on riscv64, I forgot to fix it :(
 @mitya57 am I missing something or this package needs to be synced from debian: https://packages.qa.debian.org/r/rubygems.html
 (to fix the ruby problem)
 https://salsa.debian.org/ruby-team/ruby-defaults/-/commit/909f416d20b7939585548d9f3afdf9970b0b2116
 "ruby is uninstallable before ruby-rubygems is actually in the … archive."
 That package is synced. But it's also broken in Debian.
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972702
 aha
 soy maybe we could ask the archive admins to remove ruby-defaults temprorarily from -proposed ?
 s/soy/so/
 along with the other one (src:rubygems)
 @Santa [soy maybe we could ask the archive admins to remove ruby-defaults temprorarily f …], I asked doko exactly about the same yesterday ;)
 ok, what a mess
 @mitya57 [Thank you all! I see that WebKit copied fine :)], :)
 @mitya57 [Oh, qtwebengine also needs ruby :(], :(
 @mitya57 [I asked doko exactly about the same yesterday ;)], should we progress to asking in #ubuntu-release ?
 @RikMills [should we progress to asking in #ubuntu-release ?], Done
[08:59] <RikMills> great
 I will wait 15 minutes and then retry qtwebengine
 \o/
 thanks
 @mitya57 [I will wait 15 minutes and then retry qtwebengine], then wait 20+ hrs for arm64 😢😂
 It started building!
 :)
 also: https://launchpad.net/ubuntu/+source/qtwebkit-opensource-src
 needs to be retried at some point
 @Santa [needs to be retried at some point], done
 @RikMills Can you tell me how to move the Qt transitions from planned to ongoing on https://people.canonical.com/~ubuntu-archive/transitions/ ? Or I should ask on #ubuntu-release?
 @mitya57 [@RikMills Can you tell me how to move the Qt transitions from planned to ongoing …], https://code.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs
 Thanks!
 move the qt files from monitor/planned folder to monitor/ongoing folder
 Pushed https://bazaar.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs/revision/850, thanks again
 np
 hedgewars failed to install build-dependencies because of some ghc stuff
 fcitx-qt5 failed with symbols error, that is much easier to fix
 qtpim failed with tests failures :(
 :/
 vorlon has been doing rebuilds for new ghc, so he may know the state of play
 qtpim looks like a timeout
 I mean, just retrying might built it I guess. it was build succesfully for riscv64
 * built
 @Santa [qtpim looks like a timeout], qtpim has timeout on amd64, but it was already broken there. On other architectures it has a new test failure. On riscv64 the tests are not run at all.
 In addition to all that, there is an endianness error on s390x, but it is also not new.
 I will look at it a bit later.
 https://launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/5.19.5-0ubuntu3/+build/20224640
 Just retried.
 ↑ this one needs a rebuild I guess
 thanks
 Day summary: … - all rebuilds are uploaded. … - qtwebengine built on amd64, but has NEW binaries. … - qt3d fixed in Debian, will be autosynced. … - Mike Gabriel seems to be working on the qtpim fix, I will leave it to him. … - hedgewars build-dependencies are still not installable.
 thanks
 ghc transition apparently has multiple levels of rebuilds to do before all works, so might not be quick
 @mitya57 who is Mike Gabriel?
 @Santa [@mitya57 who is Mike Gabriel?], qtpim maintainer, see https://tracker.debian.org/pkg/qtpim-opensource-src
 of the debian package
 Yes
 alright can you please forward to him my guess about the failure?
 mu guess is:
 * my guess is:
 This commit is causing the autotest regression: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=edec095cf80b62057116ce75c581b5ca5866bdcc
 I'm also guessing "2.0" and "-1.0" are being read as ints since that commit
 therefore the autotests fails because it's expecting a double
 JUST A GUESS XD
 @Santa [This commit is causing the autotest regression: https://code.qt.io/cgit/qt/qtbas …], That commit is included only in dev branch, it's not in 5.15
 @Santa [I'm also guessing "2.0" and "-1.0" are being read as ints since that commit], But you are right, these numbers are now treated as integers for some reason.
 Maybe it's an effect of the major parser rewrite in 5.15 (it now uses CBOR internally).
 I would bet for the JSON parser
 If I'm reading this code correctly, all numbers with a dot should be treated as doubles, not integers: … https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/serialization/qjsonparser.cpp?h=5.15.1#n711
 So I have no idea why they are actually becoming qlonglong :/
 so you are guessing this is the commit which broke the thing: https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.15.1&id=35adb74ddd915831789f0175423660f8e898942e
 Yes, probably that one. But it's just a guess.
 Maybe the best way to fix it is replacing 2.0 with 2.1 and -1.0 with -1.1
 Anyway, end of day for me, good night
 @mitya57 thank you. I think progress has been good :)
 I guess it won't be a tragedy if the qtpim reads "2.0" as integer into a QVariant
 good night