[16:52] [telegram] No problem at all, and thanks! (re @mitya57: I see, but don't expect it quickly, I am overloaded again.) [16:55] [telegram] @RikMills Wanna tag-team this one? :P [16:56] [telegram] I'd help but I certainly am not in a spot where I can do it alone [16:56] [telegram] Unless of course I have time in Prague ;) [16:56] [telegram] Maybe two or three overloaded people would be better than one :P [16:57] [telegram] Let me think on that. I can and have backported existing Qt before, but not done a new release in any way. [16:58] [telegram] I have some automation but it's not in a state that someone else can run it. [16:58] [telegram] 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 [16:59] [telegram] And most of the time is taken by manual work anyway (like figuring out why it doesn't build). [16:59] [telegram] I think we should work together on it though, I'm willing to help if I'm not the only one doing it :) [17:00] [telegram] /me more coffee [17:04] [telegram] @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 :) [17:05] [telegram] (I've tried to find it recently but am aware it was updated) [17:22] [telegram] https://qt-kde-team.pages.debian.net/images/qt5_build_deps.png [17:26] [telegram] I'll grab qtbase; we used GitLab wiki in the past as I recall? [17:30] [telegram] Feel free to grab qtbase, we can coordinate here. Also I can review before you upload it. [17:31] [telegram] Sounds good, I planned on using MPs for the first few anyway :) [17:36] [telegram] https://tracker.debian.org/news/1377490/accepted-qtbase-opensource-src-5156dfsg-3-source-into-experimental/ - was this meant to be uploaded to unstable? [17:36] [telegram] (After some testing time, of course... just looking for "what's going on" :) ) [17:37] [telegram] 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. [17:37] [telegram] If nobody replies, we can push it to unstable together with 5.15.7. [17:40] [telegram] 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. [17:40] [telegram] Worth adding to the list, thanks :) [17:42] [telegram] Here is upstream version with some my comments: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/416534. [17:42] [telegram] The comments are relevant for upstream if they want to keep support for Python 2, but less relevant for us. [19:01] [telegram] $ c++filt _ZN13QFontDatabase8findFontERK8QFontDefi [19:01] [telegram] QFontDatabase::findFont(QFontDef const&, int) [19:01] [telegram] $ c++filt _ZN13QFontDatabase8findFontERK8QFontDefib [19:01] [telegram] QFontDatabase::findFont(QFontDef const&, int, bool) [19:02] [telegram] That's really the only symbols change I'm seeing [19:04] [telegram] It's a private method, so that's fine. [19:12] [telegram] 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... [19:12] [telegram] (Last build took 47 minutes, I'll submit an MP within 2 hours from now...) [19:13] [telegram] I will probably be sleeping, will review tomorrow. [22:14] [telegram] https://salsa.debian.org/qt-kde-team/qt/qtbase/-/merge_requests/32 [22:14] [telegram] I intentionally left out the final changelog commit, saving that for uploading