so how should we glib2.0 stop migrating to the release pocket, when synced from experimental, and breaking builds?
No, this is not a gcc thing. But the kernel 5.2 now finally getting built in eoan, and not binary copied from disco as done for 5.0. Blocking packages for having some build failures is not the thing we are currently doing. ** Changed in: gcc-9 (Ubuntu) Status: New => Incomplete ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1836100 Title: Was able to migrate out of proposed despite breaking dmks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1836100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs