[pkg] package should be renamed according to new Debian Fonts Policy

[Rogério Theodoro de Brito]

Hi.

I just downloaded the font package and I noticed that its name is passé: we are now adopting the conventions from here (written by yours truly):

    https://github.com/rbrito/fonts-policy

In symmary: it should begin with `fonts`, followed by a hyphen, followed by the name of the font (lowercased, spaces substituted with hyphens etc.), without the need of "family" in its name. For instance, `fonts-ubuntu` would be fine. `fonts-ubuntu-maag` is also fine.

If you plan on releasing fonts in multiple formats, then putting the format as part of the name is OK.

Regards,

Rogério Brito.

[Matthew Paul Thomas (mpt)]

Neither this bug report, nor the linked policy, give any hint of what bad things happen if the policy is not followed. Some examples would help in determining how important this bug is to fix.

[Matthew Paul Thomas (mpt)]

The current policy is on the Debian wiki. <https://wiki.debian.org/Fonts/PackagingPolicy> It claims that "There is currently discussion on the pkg-fonts-devel mailing list that hopes to lead to a more comprehensive policy". Sadly, that isn't the case: the mailing list is almost entirely spam and debbugs/ftpmaster notifications.

Rogério, I really would appreciate the information I asked for previously: What happens if the policy is not followed? Or to put it another way, what benefits would this change have?

[Paul Sladen (sladen)]

Doing this as a one-off would be extranous (which is why it has been waiting for a new upstream release to go out, which hasn't happened yet), but it would be relatively quick (5–10 minutes to actually change ./debian/{control,*.install} and then an hour or two testing upgrade testing combinations) to split these at the point of doing the next packaged font release.

It makes sense to do this at the same time as bug #863358, as the rename to the New Debian Font Standard packaging names requires the same operations, and this would turn two rounds into a single round.

[Jeremy Bícha (jbicha)]

This is being fixed now by renaming the source package from
ubuntu-font-family-sources package to fonts-ubuntu.

The binaries are being renamed from
ttf-ubuntu-font-family to fonts-ubuntu and from
fonts-ubuntu-font-family-console to fonts-ubuntu-console.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rogério Theodoro de Brito (rbrito)]

Thanks a lot!

--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Em 28 de fev de 2018 09:02, "Jeremy Bicha" <email address hidden> escreveu:

> ** Project changed: ubuntu-font-family => ubuntu-font-family-sources
> (Ubuntu)
>
> ** Changed in: ubuntu-font-family-sources (Ubuntu)
> Status: New => Fix Committed
>
> ** Changed in: ubuntu-font-family-sources (Ubuntu)
> Milestone: 1.00 => None
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/851457
>
> Title:
> [pkg] package should be renamed according to new Debian Fonts Policy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-
> family-sources/+bug/851457/+subscriptions
>
>