I'm adding a glib2.0 task so that this shows more easily on the excuses page for people wondering why glib2.0 isn't able to migrate.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2129695 Title: Please remove awesome from resolute but not resolute-proposed Status in awesome package in Ubuntu: New Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2.0 2.86.0-3 sets Breaks: awesome (<< 4.3-8~) because awesome needs changes to work with glib 2.86. See https://bugs.debian.org/1115591 This means that britney won't migrate glib2.0 out of resolute-proposed as long as awesome << 4.3.8~ is in resolute. awesome currently fails to build with what looks like an obscure issue since our lua packages are basically in sync with Debian and I haven't seen any other lua package fail to build at this point. Debian would prefer to keep the Breaks since it is technically correct and I would prefer to not add a diff with Debian for this issue. Therefore, my recommendation is that we remove awesome from resolute, but leave it in resolute-proposed. Once awesome's build is fixed, it can migrate back to resolute. Build log excerpt ================= [ 98%] Generating API documentation cd /<<PKGBUILDDIR>>/build/docs && /usr/bin/ldoc . Error: no suitable Lua interpreter found Error: supported versions are: 5.2 5.1 Other Info ========== awesome is built with the default Lua, 5.3 https://launchpad.net/ubuntu/+source/awesome/4.3-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesome/+bug/2129695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
