[07:00] Huh. What has caused https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#mir to leave old riscv and s390x binaries behind? [07:01] RAOF, NBS binaries are not autocleaned, so my guess would be whoever did a NBS round did it before the new version had built on those archs yet [07:01] Those binaries are indeed not built by the new package, but why only complain about riscv & s390x? [07:02] RAOF, on fact, https://launchpad.net/ubuntu/+source/mir/2.7.0-0ubuntu4 explain it [07:02] that version only built on those architectures [07:03] !!! I didn't notice that, because how would it only build there 🤪 [07:03] RAOF: I am only a bot, please don't think I'm intelligent :) [07:03] RAOF, because we ignore test results on those archs? [07:04] RAOF, anyway, just clean the NBS binaries from proposed now :) [07:04] Yeah, will do. [07:05] Huh. I thought we ran wlcs on all (little-endian) archs. 🤷‍♀️ [07:07] Oh! Does *launchpad* build with `DEB_BUILD_OPTIONS=nocheck` on riscv? [07:08] The More You Know! [07:09] RAOF, yes, since the arch was added, it would have make really difficult to start the port otherwise [07:09] Fair! [07:09] And it is already slow, might as well have been partially a capacity/speed reason [07:10] also I don't think we have the builders to keep up otherwise [07:10] what cpaelzer said [07:47] rbasak: I've added the arguments/details I mentioned to 1890263 - let me know if that is enough to reconsider (we will re-upload to SRU queue then) or not (fine as well - keep it on Won't Fix but untag server-todo then) [10:52] actually focal was built with tests enabled for riscv, they were only disabled in gutsy (which makes for a surprise or two when SRUing things) === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie