 No problem at all, and thanks! (re @mitya57: I see, but don't expect it quickly, I am overloaded again.)
 @RikMills Wanna tag-team this one? :P
 I'd help but I certainly am not in a spot where I can do it alone
 Unless of course I have time in Prague ;)
 Maybe two or three overloaded people would be better than one :P
 Let me think on that. I can and have backported existing Qt  before, but not done a new release in any way.
 I have some automation but it's not in a state that someone else can run it.
 It's been a while since I've done it, but I am able to parse automation if you're willing to hand it to me in a pm
 And most of the time is taken by manual work anyway (like figuring out why it doesn't build).
 I think we should work together on it though, I'm willing to help if I'm not the only one doing it :)
 /me more coffee
 @mitya57 Where does the build order live? I can get us started at least, and get a document going, if you don't have those already :)
 (I've tried to find it recently but am aware it was updated)
 https://qt-kde-team.pages.debian.net/images/qt5_build_deps.png
 I'll grab qtbase; we used GitLab wiki in the past as I recall?
 Feel free to grab qtbase, we can coordinate here. Also I can review before you upload it.
 Sounds good, I planned on using MPs for the first few anyway :)
 https://tracker.debian.org/news/1377490/accepted-qtbase-opensource-src-5156dfsg-3-source-into-experimental/ - was this meant to be uploaded to unstable?
 (After some testing time, of course... just looking for "what's going on" :) )
 No, I'm not sure how Qt Wayland works on GNOME, so I asked for testing in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954781#39.
 If nobody replies, we can push it to unstable together with 5.15.7.
 By the way, Debian's release team wants me to port Qt WebEngine to Python 3. If you somehow have a lot of free time, help with that will be welcome. ArchLinux has a patch for that, we can steal it from them.
 Worth adding to the list, thanks :)
 Here is upstream version with some my comments: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/416534.
 The comments are relevant for upstream if they want to keep support for Python 2, but less relevant for us.
 $ c++filt _ZN13QFontDatabase8findFontERK8QFontDefi 
 QFontDatabase::findFont(QFontDef const&, int)
 $ c++filt _ZN13QFontDatabase8findFontERK8QFontDefib
 QFontDatabase::findFont(QFontDef const&, int, bool)
 That's really the only symbols change I'm seeing
 It's a private method, so that's fine.
 I think my local qtbase is ready for review - I'm going to put it through one more build cycle for CYA - copyright updates made are already reflected in our copyright file (the tri-licensing for libjpeg), and symbols seem kosher. I worry about non-standard arches, but that will come with time once this hits experimental...
 (Last build took 47 minutes, I'll submit an MP within 2 hours from now...)
 I will probably be sleeping, will review tomorrow.
 https://salsa.debian.org/qt-kde-team/qt/qtbase/-/merge_requests/32
 I intentionally left out the final changelog commit, saving that for uploading