Hola,
On 2026-07-18 08:44, Boyuan Yang wrote:
> 在 2026/7/17 17:27, Luke Yasuda 写道:
>> Hi all,
>>
>> As you know, both anthy and kasumi are not maintained upstream
>> anymore. Bug #1110438 suggested that anthy could be replaced by the
>> succeeding hard fork "anthy-unicode". In fact, the upstream maintainer
>> of anthy-unicode also hard forked kasumi as "kasumi-unicode" [1][2]. I
>> see two ways to move forward:
>>
>> a. file two ITPs, for anthy-unicode and kasumi-unicode. They should
>> "Provides:" anthy and kasumi respectively. After they're packaged,
>> anthy and kasumi should be requested removal from unstable.
>>
>> b. we don't introduce two new packages. We simply migrate these anthy
>> and kasumi to the new upstream by updating them to the new upstream
>> versions.
>>
>> I prefer b. anthy-unicode and kasumi-unicode are hard forks after the
>> original projects stopped development, things are compatible. The
>> migration process should be transparent to users. It'll look like a
>> simple upstream maintainer change.
>>
>> Either ways, I can help (but need sponsors). But before I start to do
>> anything, please let me know your thoughts so we're on the same page.
>>
>> [1] https://github.com/fujiwarat/anthy-unicode
>> [2] https://github.com/fujiwarat/kasumi-unicode
> This seems reasonable for the orphaned kasumi, but listed Anthy package
> maintainers
> may need to be notified since Debian's anthy source code forked a
> little
> bit off the original version. See https://tracker.debian.org/pkg/anthy
> and https://wiki.debian.org/Teams/DebianAnthy .
I assumed all the uploaders were on the debian-input-method list. But
I'm Cc'ing people listed in "uploaders" and the Debian-JP devel mailing
list just in case.
Cheers,
--
Luke Yasuda
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC