https://bugzilla.redhat.com/show_bug.cgi?id=1635455

--- Comment #2 from Akira TAGOH tagoh@redhat.com --- It was. Canna requring to build this sub-package has been orphaned (I was a maintainer and I'm not interested in maintaining anymore) and will be dropped soon because no one seems interested to it and keeps orphaned so long.

Was it intended that the package no longer build by default? If so, should something obsolete it? If not, can you put it back? Thanks!

What sort of functionality do we need to consider for replacement? from Japanese-input perspective, there might be a few options to replace it though, strictly speaking from UX, there are no candidates at all. Or should it be added to fedora-obsolete-packages? dunno if they allow us to add sub-package though.

https://bugzilla.redhat.com/show_bug.cgi?id=1635455

Adam Williamson awilliam@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(awilliam@redhat.c | |om) |

--- Comment #3 from Adam Williamson awilliam@redhat.com --- 'Obsoletes' is not strictly about replacement, at least as I see it. 'Provides' is about replacement. The point of 'Obsoletes' is just to get the package off people's systems. The key question to ask yourself about Obsoletes is: "OK, I want to ensure people with package X installed get it removed on update. What *other*, somehow vaguely-related, package is highly likely to be installed in almost every case where X is installed?" Then put the obsolete in that package. That package doesn't have to be, strictly speaking, a *replacement*.

I don't think there's any problem with putting subpackages in fedora-obsolete-packages either.