[16:49] looks like Simon or someone else dutifully started the next step of the cycle for us [16:51] Yup that was me 🙂 [16:51] Give it, meh, 6 hours and this will be up to date: https://ubuntu-archive-team.ubuntu.com/transitions/html/qt-6.6.2.html#!good,bad,partial,unknown,!notintesting [16:51] Also fun fact, once qt6-declarative is built and published, qt6-tools can also be synced [16:52] I know it's slightly confusing when just looking at a bullet-pointed list... the diagram is better [16:52] * tsimonq2[m] uploaded an image: (219KiB) < http://localhost:8008/_matrix/media/v3/download/ubuntu.com/OPhwQLTcjRbKomdyyqFfRnrE/image.png > [16:52] https://qt-kde-team.pages.debian.net/images/qt6_build_deps.png [16:52] spaghetti [16:52] but yes that is helpful :) [16:53] lmfao it's debatable on whether it's more or less helpful than the bullet pointed list 😜 [16:57] Aaron Rainbolt: Have you ever done no-change rebuilds for a transition before? [16:59] I don't know for sure, but I think I probably have and I believe I know how it's done. [16:59] DOwnload package, bump version (carefully!), add a changelog about why you NCR'd, upload, right? [17:00] I'd suggest pinging LocutusOfBorg and asking for his NCR script hah, there's a way to get a package ready with one command if you do dch-foo right [17:00] ok :) [17:01] Otherwise once all the Qt packages in the stack are synced/built, probably before the two NEW packages, this will have a good list of what needs NCRs and in what order: https://ubuntu-archive-team.ubuntu.com/transitions/html/qt-6.6.2.html [17:01] kk [17:01] If we make Madison mad and the stack still won't migrate, we should see what it complains about: https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_output.txt [17:02] anyway that's about all there is to it - dch -R is what I'll typically do [17:02] and I've already seen calibre and that one German ID package both FTBFS, so those won't need NCRs, they'll need retries [17:19] -Ubottu[m]:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Jammy 22.04.4] has been updated (20240507) [17:21] -Ubottu[m]:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Jammy 22.04.4] has been updated (20240507) [17:34] "I'd suggest pinging LocutusOfBor..." <- I want to know this [18:29] We'll share :) [18:29] It's late in Italy, so probably a tomorrow thing... plus qt6-declarative isn't built and published on riscv64 yet [18:55] This? [18:55] * RikMills[m] sent a code block: http://localhost:8008/_matrix/media/v3/download/chat.staging.ubuntu.com/vDEjskicggymguOdoaxwaaSQ [18:55] called rebuild-for [18:56] so you do rebuild-for "what you are rebuiilding against" source [18:57] That is what I use anyway [18:57] Came from doko I think [18:58] * RikMills[m] posted a file: rebuild-for (0KiB) < http://localhost:8008/_matrix/media/v3/download/kde.org/822c458ff6de6609036e73dcd60ef97b02550c211787919844398596096 > [18:58] That's one of those things that should be in ubuntu-dev-tools. [18:59] Simon Quigley: wxl ? [19:00] Thanks! [19:00] nifty [19:01] ErichEickmeyer[m: send in the PR! [19:01] wxl[m]: I'm just saying I'm surprised doko hasn't. [19:08] "#!/bin/sh..." <- > <@rikmills:kde.org> ```... (full message at ) [19:08] I don't doubt it ;) [19:09] But it works..... [19:11] Just a few safeguards, but nothing too terrible. [19:12] I actually like LocutusOfBorg's iteration better ;) https://pastebin.ubuntu.com/p/rBmTtsst5n/ [19:13] ¯\_(ツ)_/¯ they're all just scripts wrapping around dch and dput, I'm sure a Pythonic approach can be taken too [19:14] In the end you get a commends you can script into a long batch list of packages, so prepare hundreds of source packages in one dir in one go [19:15] s/commends/command/ [19:15] then do dput ubuntu *.changes [19:15] :) [19:20] oh, LOBs does the dput. same difference though [19:21] RikMills[m]: Not only does it do the dput, it has the prompt/safeguard commented out ;) [19:22] Perfect, who needs that anyway? :P [19:23] 🤐 [21:26] Hardware RISC-V64 builders when [21:26] :P [21:59] "Hardware RISC-V64 builders when" <- Too RISCy.