touch-packages team mailing list archive

[Vasudev Kamath <kamathvasudev@xxxxxxxxx>]

On Sun, Dec 20, 2015 at 4:13 AM, Gunnar Hjalmarsson
<1527938@xxxxxxxxxxxxxxxxxx> wrote:
> @Vasudev: It struck me that the package name change isn't quite
> uncomplicated, since fonts-droid is shipped by default on all Ubuntu
> installs. However, I suggest that we await Aron Xu's comments before
> doing anything.

Sure. But the move was unavoidable since Android upstream dropped
Droid Fonts all together. Providing fonts-droid with only Fallback
font might confuse people so we asked every one to switch to Noto as
per upstream suggestion, we also dropped a fontconfig file which maps
all Droid fonts to Noto (DroidSans and DroidSerif).

And finally I moved Fallback fonts to new package fonts-droid-fallback.



--

Vasudev Kamath
http://copyninja.info

-- 
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/1527938

Title:
  Upstream fonts-droid -> fonts-droid-fallback

Status in fonts-android package in Ubuntu:
  New

Bug description:
  Upstream has moved the Droid Sans Fallback font from the fonts-droid
  package to a new fonts-droid-fallback package.

  http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/

  It means that we'll need to change the package name in a bunch of
  seeds, and in pkg_depends.

  This will not be a problem as regards new installs, as far as I can
  tell, but I fear a problem when people upgrade from 14.04 or 15.10 to
  16.04, since there is no dummy package with the old name which depends
  on the new one.

  @Aron: How should we deal with this issue? One way, if Droid Sans
  Fallback will keep being the default Chinese font in 16.04, is to ask
  upstream to create a transitional dummy package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1527938/+subscriptions