vcswatch reports that
this package seems to have a new changelog entry (version
0.0.git20261101-2, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit c5e7cd7b2e3a93e1ef3e68e537f4c9f8e108be4a
Author: kevin <k@funmula.com>
Date: Thu Nov 19 22:37:49 2026 +0800
Build-Depend on 0c-ime-tools 0.2.13+ds-1
0c-ime 0.2.12+ds-1 was never uploaded. 0.2.13+ds-1 has the memory fix
upstream and is the first 0c-ime that ships pairing.lock.json, so use
it in Build-Depends and Breaks.
commit 2de17349185ebb29c7cea59e4fcc5bbf15342ba7
Author: kevin <k@funmula.com>
Date: Thu Nov 19 20:07:24 2026 +0800
Release 0.0.git20261101-2
commit 02f78191be85fdd50e9b7d00595f2d521cc00766
Author: kevin <k@funmula.com>
Date: Thu Nov 19 20:03:12 2026 +0800
Build with less memory and with newer tools (#1154305)
0c-compile in 0c-ime-tools before 0.2.12+ds-1 needed about 7.4 GB of
memory, and the build hung on a machine with 4 GB. Build-depend on the
fixed version and set GOMEMLIMIT=2000MiB for 0c-compile. Run
0c-single-gate with the jobs from DEB_BUILD_OPTIONS.
0c-ime 0.2.13 adds -attested-mass, whose default changes this
dictionary. Pass -attested-mass=0 when 0c-compile has it, so that the
same upload builds with older and newer tools.
Stop installing pairing.lock.json, which 0c-ime makes from 0.2.12 on,
and add Breaks: 0c-ime (<< 0.2.12~).
commit 1db4c6ae93baaa879f8ee50092818faa3afc650c
Author: Kevin Watt <k@funmula.com>
Date: Mon Nov 2 10:22:29 2026 +0000
Add the libtabe notice and fix the Apache-2.0 path
words.tsv has phrases from libtabe through McBopomofo, so name the holders and
the terms of libtabe's tsi-src/COPYING. chars.tsv has its own stanza, because
it has other sources. The path to the OpenCC license is in 0c-ime, not in this
source package.
commit 3a6f65ce8f5effdd07db693bfed05acf6942dedb
Merge: 0d31c39 eb991ec
Author: Kevin Watt <k@funmula.com>
Date: Sun Nov 1 13:21:37 2026 +0000
Update upstream source from tag 'upstream/0.0.git20261101'
Update to upstream version '0.0.git20261101'
with Debian dir 9117b90e08baea420f24f4a57628325090724053
commit 0d31c3913bfe60dccc04b405c18dd47e114b0b41
Author: Kevin Watt <k@funmula.com>
Date: Sun Nov 1 21:19:38 2026 +0800
Use 0.0.git<date> as the version
This fixes the lintian warning new-package-uses-date-based-version-number.
commit 5d039eef2f043c31ddb24bdd09b002376e07d952
Author: kevin <k@funmula.com>
Date: Sun Nov 1 14:55:06 2026 +0800
Explain the build order in README.source
commit 7ba759c7514b584bfb0ca33939e6bfbf57937756
Author: kevin <k@funmula.com>
Date: Sun Nov 1 08:22:42 2026 +0800
Close the ITP in the changelog
commit 646b56f8c929cdd5b3c457298c1e984d068f5161
Merge: 02dd764 5710b61
Author: Kevin Watt <k@funmula.com>
Date: Sat Oct 31 22:19:12 2026 +0000
Update upstream source from tag 'upstream/20261101'
Update to upstream version '20261101'
with Debian dir b5e35df29ee0ca3ffd70c22e5a5c4f4ad29d5eff
commit 02dd764735dd275c4e5e1acaa30ae977dc20e080
Author: kevin <k@funmula.com>
Date: Sun Nov 1 04:17:56 2026 +0800
Add the packaging
Compile the dictionary with the tools from 0c-ime-tools, and stop if the result
does not match data/dictionary.lock.json.
Tested with a local tarball made like the planned upstream release. The result
is byte-identical to the dictionary in the 0c-ime 0.2.7 release. The watch file
is not tested yet: upstream has not published that release.
commit 29634203646163d2264d263c147a3143bf09915a
Author: kevin <k@funmula.com>
Date: Sun Nov 1 03:33:06 2026 +0800
Start the 0c-ime-data packaging
The dictionary moves out of the 0c-ime source package. Not buildable yet:
the upstream release only has the bigram files.