← Back to team overview

documentation-packages team mailing list archive

[Bug 1626245] Re: [MIR] fonts-android


On 2016-09-22 15:18, Michael Terry wrote:
> 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?

Yes it is. We did consider doing so last spring, but decided not to;
please see <https://bugs.debian.org/823374>.

For the Z series it would be possible to pick up that idea again. In
that case we would get:

* fonts-noto-cjk
  Providing the weights regular and bold; approx. 22 MiB archive space

* fonts-noto-cjk-extras
  Providing the other font weights; approx. 50 MiB archive space

fonts-noto-cjk would then require approx. 22 - 2 = 20 MiB more archive
space comapred to fonts-droid-fallback. If that's something which the
server team can 'live with', it's one way to handle this.

> But for yakkety sure, let's promote this again.


You received this bug notification because you are a member of
Documentation Packages, which is subscribed to fonts-android in Ubuntu.

  [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




  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main

To manage notifications about this bug go to: