[MIR] fonts-orya, fonts-lohit-orya, fonts-orya-extra

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

This is a long overdue changeover, especially now that ttf-indic-fonts is removed from Debian. Two things though:
- It would be nice to see a team bug subscriber (~indian-team subscribes to ttf-indic-fonts, probably a good fit here too)
- What's the migration plan? I see that Debian has removed the transition packages (they made the transition so long ago)

BTW, those questions will be general questions for this whole crop of fonts-* MIRs you've filed.

The bug subscriber one is normally a blocker, but I'm willing to waive the paperwork for these tiny data packages that rarely change.

The transition question is more important though.

I've sent a message to ~indian-team asking them to subscribe to these packages.

What is the transition problem? As far as I could see the new packages appropriately conflict with the old ones so just changing the seed to bring in the new packages should uninstall the ttf-* versions.

True, there's no problem if people happen to have another package that depends on the new font packages. For example, this MIR's old package (ttf-oriya-fonts) is seeded in ubuntu-gnome. But that's the only seed it's included in.

So if an Indian user is using normal ubuntu-desktop and installed the Indian language during installation, or from the Language settings panel, and then upgraded to a release with this change made, they wouldn't get the new package.

Normally when we do such a transition, we keep the empty transitional packages around until the next LTS.

So in order to take care of our Indian users that aren't using Ubuntu GNOME, I'd argue that as part of promoting these fonts to main, in addition to changing which packages get installed when Indian languages are selected, we also update ttf-indic-fonts to be full of empty transitional packages pointing at the new fonts.

Then in 16.10, we can remove ttf-indic-fonts from the archive like Debian is able to do.

But that doesn't affect these fonts themselves. So I'll approve the lot of them.

Override component to main
fonts-orya 2:1.2 in vivid: universe/fonts -> main
fonts-orya 2:1.2 in vivid amd64: universe/fonts/optional/100% -> main
fonts-orya 2:1.2 in vivid arm64: universe/fonts/optional/100% -> main
fonts-orya 2:1.2 in vivid armhf: universe/fonts/optional/100% -> main
fonts-orya 2:1.2 in vivid i386: universe/fonts/optional/100% -> main
fonts-orya 2:1.2 in vivid powerpc: universe/fonts/optional/100% -> main
fonts-orya 2:1.2 in vivid ppc64el: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid: universe/fonts -> main
fonts-lohit-orya 2.5.4.1-1 in vivid amd64: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid arm64: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid armhf: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid i386: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid powerpc: universe/fonts/optional/100% -> main
fonts-lohit-orya 2.5.4.1-1 in vivid ppc64el: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid: universe/fonts -> main
fonts-orya-extra 2.0-3 in vivid amd64: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid arm64: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid armhf: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid i386: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid powerpc: universe/fonts/optional/100% -> main
fonts-orya-extra 2.0-3 in vivid ppc64el: universe/fonts/optional/100% -> main
21 publications overridden.

~indian-team is totally inactive for past 4-5 years . what is the transition plan for ttf-indic-fonts-core ?
What will be the installer dependancy ? ttf-indic-fonts-core created long back by considering community preference for fonts for installer in debian and same repeated in ubuntu . How you are addressing this ?