[MIR] fonts-teluguvijayam

[Sebastien Bacher]

* Availability

Currently version builds fine and is in sync from Debian https://bugs.launchpad.net/ubuntu/+source/fonts-teluguvijayam/1.0-3 (it's a font and arch all so only amd64 build)

* Rationale

It's a new depends from fonts-telu

* Security

No CVE/known security issue

* Quality assurance

- the desktop-packages team is subscribed to the package
- the package is in sync with Debian
- the only report on Debian is a wishlist to include extra fonts which is blocked on license question

* Dependendies

The package has no depends

* Standards compliance

the package is using standard packaging (dh12) and a recent standards-version, it is in sync from Debian

* Maintainance

The package is maintained in Debian by the fonts team, the desktop team is going to look at issues on the Ubuntu side if requires

[Christian Ehrhardt  (paelzer)]

[16:43] <seb128> cpaelzer, note that the font got promoted already so I was unsure if the MIR was needed but I still filed it
[16:44] <cpaelzer> oh really, maybe it was MIRed in the past already then
[16:44] <cpaelzer> fonts-teluguvijayam | 1.0-3 | groovy | source, all
[16:47] <doko> cpaelzer: see the publishing history
[16:47] <seb128> vorlon did it
[16:47] <seb128> but no reason recorded there though
[16:48] <cpaelzer> well let me do the review then and either retrofit the Ack - or mention in case I don't agree
[16:48] <seb128> right
[16:48] <seb128> it made me wodner if there was an unstated policy that fonts don't need a MIR anymore
[16:48] <seb128> would be nice :)

[Christian Ehrhardt  (paelzer)]

[19:34] <vorlon> cpaelzer, seb128: was that a case of a font being promoted because it had been split out into a separate source package? Those wouldn't normally need to go through MIR. Or, yes, I could've assumed it didn't need an MIR because it was a font