I mean, it's fine to put this back if we need it. It used to be in main, it's just fonts, etc.
But for the same reasons that we downgraded it (has a replacement), it would still be nice to drop it again in the future. Is there another way to solve bug 1625734 than going back to fonts-android? Is it possible to split fonts-noto-cjk into smaller chunks for example? But for yakkety sure, let's promote this again. ** Changed in: fonts-android (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1626245 Title: [MIR] fonts-android Status in fonts-android package in Ubuntu: Fix Committed Status in ghostscript package in Ubuntu: In Progress Bug description: Please include the fonts-android package in Ubuntu's component main. fonts-android includes the fonts-droid-fallback binary, and as a result of the discussion at bug 1625734, the server team wants that libgs9-common, which currently recommends fonts-noto-cjk, is changed to instead recommend fonts-droid-fallback. fonts-android is a Debian package and included in Debian's component main. It was included in Ubuntu's component main between trusty and wily. Bugs: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android https://bugs.launchpad.net/ubuntu/+source/fonts-android I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and haven't found any issues that would prevent the proposed main inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1626245/+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