Please note that FTBFSes on arm* have been resolved in mir 2.14.1-8 (Debian unstable). Maybe sync that version first?
@tsimonq2 I'd go with a well tested Mir 2.14 for 25.04 and wait with Mir 2.19 for 25.10. On the Lomiri part, Mir 2.19 and the not yet even public qtmir counterpart are so bleeding edge they are not fit for a distro release imho. This might be a problem for Lubuntu, though. So let's get everything (Mir 2.19, qtmir with Mir 2.19 API compliance) staged in Debian experimental and test how everything goes on the Lomiri side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/2099790 Title: [p-m] Mir FTBFS in plucky-proposed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Triaged Bug description: Mir FTBFS in plucky-proposed. The version there is 2.14.1, but I just uploaded 2.19.3 to Debian Experimental. I'd like to get this in for Plucky and turn this into an FFE bug, but for now, please don't sync from Debian Experimental without asking me, someone from the Mir Team, or Mike Gabriel, and please either remove the upload from proposed to clear the report or fix the arm64 failure in 2.14.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/2099790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
