- Package:
- src:libpinyin
- Source:
- libpinyin
- Submitter:
- Boyuan Yang
- Date:
- 2026-08-04 22:21:02 UTC
- Severity:
- normal
- Tags:
Dear Debian Input Method team members, Currently libpinyin in Debian is using Berkeley DB (libdb-dev). After the release of Debian 11, Debian has a release goal proposal to remove Berkeley DB due to its problematic AGPLv3 license issue (for details, see https://bugs.debian.org/987013 ). It seems that libpinyin also supports Keyto Cabinet as DBM. I believe we should consider switching to it to avoid dependency on Berkeley DB. It may also solve some old problems such as https://tests.reproducible-builds.org/debian/issues/unstable/berkeley_db_variation_requiring_further_investigation_issue.html and https://tests.reproducible-builds.org/debian/issues/unstable/randomness_in_files_generated_by_pinyin_gen_binary_files_issue.html . However, I am not sure what would users experience when database format is switched (e.g., will all data previously stored in old db be lost? Is that a severe issue?). Even with such side effect, I believe the benefit would be more significant and we should perform the switch within current development cycle. P.S. I am also aware of https://github.com/libpinyin/libpinyin/issues/140 , and tkrzw is being reviewed by Debian FTP Masters at https://ftp-master.debian.org/new/tkrzw_1.0.0+dfsg1-1.html .
Please don't misread the bug, this is not a goal that is confirmed by the Release team.
Hi, 在 2021-09-03星期五的 23:51 +0800,Shengjing Zhu写道: Indeed; that's why I wrote "release goal proposal" instead of "release goal". Anyway, personally I expect it to occur sometime in future, sooner or later. We already have a transition slot tracking the removal of libdb at https://release.debian.org/transitions/html/db5.3-rm.html . Thanks, Boyuan Yang
I think we should make a serious attempt to avoid such an interruption before accomplishing a switch to some other db format. There seems to be plenty of time.
Boyuan, I saw you made test uploads to experimental due to this. I talked with Sebastien Bacher, and with our Ubuntu hats on we are not very enthusiastic. kyotocabinet is currently not in Ubuntu's "main", so we would need to file a main inclusion request, and the related review would result in a symbols file request (compare opencc and marisa). So if you decide to do this soon, we'll probably revert the switch in Ubuntu for now. Wouldn't it be better to wait a bit and see what projects such as perl and python do? Also, considering that tkrzw is mentioned as a successor to kyotocabinet, if we would switch to the latter now, we might need to make yet another switch soon.
Hi, 在 2021-09-23星期四的 17:19 +0200,Gunnar Hjalmarsson写道: with clean installation, the (ibus-)libpinyin instance does not seem to be properly generating local user dictionary. So I guess we will not make this migration without further investigation. I am also wondering about Ubuntu's plan on libdb removal, though I guess Ubuntu may keep it forever due to needs from commercial side. Thanks, Boyuan Yang
Ack., good to know I'm not able to tell. Sebastien, who works for Canonical and usually is well-informed about what's going on, hadn't heard any discussion about the topic. Maybe the discussion is only held on Debian so far.
We believe that the bug you reported is fixed in the latest version of
libpinyin, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 993415@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libpinyin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 04 Aug 2026 17:28:37 -0400
Source: libpinyin
Architecture: source
Version: 2.11.91-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 993415 1119204
Changes:
libpinyin (2.11.91-1~exp1) experimental; urgency=medium
.
* Team upload.
* New upstream release candidate.
* debian/NEWS: Add a NEWS entry for the engine switch from
BerkeleyDB to Tkrzw. All previous user data will be lost
after the upgrade.
* debian/rules: Switch from BerkeleyDB to Tkrzw. (Closes: #1119204)
* debian/control: Switch from BerkeleyDB to Tkrzw. (Closes: #993415)
* debian/control: Bump debhelper compat to v14.
* debian/control: Bump Standards-Version to 4.7.4.
* debian/patches/*.patch: Drop all patches, merged upstream.
Checksums-Sha1:
04246dc55255cc48af04df7b4f7534d33fdcdf6b 2562 libpinyin_2.11.91-1~exp1.dsc
ca990cd40fa152844debd1bb321716ce928d45f5 20638374 libpinyin_2.11.91.orig.tar.gz
9860f4b46e42556914806acb443916782dff64ab 6416 libpinyin_2.11.91-1~exp1.debian.tar.xz
e77143ffe3af677430b9b3ee0039b4b7ed5b9217 9774 libpinyin_2.11.91-1~exp1_amd64.buildinfo
Checksums-Sha256:
d2b3b750b8c0fbc0af3249f4f0eca60953ef2f34b7032a705ce701d8e187b2ee 2562 libpinyin_2.11.91-1~exp1.dsc
ff3047b19d17b82e26891abbe1bb354a9da3f66393c07c71072de0615e21788c 20638374 libpinyin_2.11.91.orig.tar.gz
04b2497bf429d0f4b55facee4c6fb96838eb9820041cf21e3844c3d6e5602f06 6416 libpinyin_2.11.91-1~exp1.debian.tar.xz
4bc8e1e380811d1ae07aa5ee9e671ccb3e3ec1f9dae734253609d552e64c6c9b 9774 libpinyin_2.11.91-1~exp1_amd64.buildinfo
Files:
2fe6668e5f033cf2fa77784c8dc2b111 2562 libs optional libpinyin_2.11.91-1~exp1.dsc
27476fc7bb0c1932b4b850ec30f3217a 20638374 libs optional libpinyin_2.11.91.orig.tar.gz
f00b5d6e449fbee8656617a37747fd08 6416 libs optional libpinyin_2.11.91-1~exp1.debian.tar.xz
b3865a794b662b06728ec7a295a78fe9 9774 libs optional libpinyin_2.11.91-1~exp1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmpyYxUACgkQwpPntGGC
Ws6pCQ//XqlvCXDC3FqgRNm/97w9suewu9HaLvKQoHxROs0dLdrOf8p7aiVj6vcX
W8KW5U7GNsgzIFcFkPxJqd8VNtgpHTiFBGt6uucz/Nmq5arrF/lgrq2bIF37WRPn
qBe2lCtMIsBBIB5iLzFhhTdqlmVrsr6RINJYHqxerF880ZZSbqywqB+XKFQTWepg
6M48+12WJwcuEgVPiCKcBo/D6tKqS9tkMH/SOOoUARn7qNhMrjJ3JbRzg4gIx+zC
V1LnnOEnN9gNYfveJuD5EWrCVzVXJKu/GnOVsSqs9iYppOZiqYdt6sxyCc3lvLop
sVimzljXodWkKDPc4VQ1lrMH7bDk8hATMiRX70Z5WXFcs6CrDucd7JRdI8y2SzZe
aJI7wS3lsoErdpc1aydBCYfIjHf+GZZ9OSUbN866l0wPS6gv4eGyf8+XVs5h9EvP
Rij6pOEeRv0RN2oC/TYVKQCSGZV9RwEbr2yfNokNkcDp4TX2T2JlaAA6QZxoCIVN
9Bu6pySt4NGzx2x5pnO/xIVGEEEg7UvTUnUlriiGS7c2qdsK6AA+bkCjGhEJvgD8
WLbK4RJzPtn15plguTDaPNmSlQDNP7/80Gj5RVDRlYqPWiBibnXSX2KhbKS0Je4N
oXZJvxVuZ+5MYiEVsNt5m2lqo4xPuOl1XkGgdcJ2dQVTkSRYKiE=
=pehe
-----END PGP SIGNATURE-----