touch-packages team mailing list archive

[Gunnar Hjalmarsson <1527938@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: fonts-android (Ubuntu)
     Importance: High
         Status: New

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