Debian Patches
Status for opencc/1.4.1+ds1-7
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0003-no-remote-images-when-reading-docs-on-disk.patch | Don't fetch remote images when reading docs on disk This fixes a privacy breach previously reported as Lintian warnings |
Gunnar Hjalmarsson <gunnarhj@ubuntu.com> | not-needed | 2026-04-25 | ||
| 0004-Use-system-googletest.patch | Use system googletest | Shengjing Zhu <zhsj@debian.org> | not-needed | 2024-07-28 | ||
| 0005-Disable-build-in-setup.py.patch | Disable build in setup.py | Shengjing Zhu <zhsj@debian.org> | no | 2024-08-02 | ||
| 0009-setup.py-Handle-python-binding-instead-of-cmake.patch | setup.py: Handle python binding instead of cmake Link the extension against the libopencc.so built by the cmake pass in $OPENCC_BUILD_DIR/src. Only -L (library_dirs) is set on purpose: adding runtime_library_dirs would bake the (build-time-only) build directory into DT_RUNPATH, and even deleting that entry afterwards leaves the build path behind in .dynstr (lintian: file-references-package-build-path). The installed extension resolves libopencc.so.1.4 through the regular linker search path instead; debian/rules sets LD_LIBRARY_PATH for the test run. |
Boyuan Yang <byang@debian.org> | not-needed | 2026-01-13 | ||
| 0010-fix-git-version-fallback.patch | Fix stale fallback version when building from a tarball without .git Upstream derives OPENCC_VERSION from `git describe` in cmake/GitVersion.cmake, falling back to hardcoded _OPENCC_FALLBACK_MAJOR/MINOR/REVISION when no .git directory is present (as is always the case for Debian source tarballs). The fallback was left at 1.4.0 in the 1.4.1 release, so builds from the released tarball report version 1.4.0 instead of 1.4.1. =================================================================== |
xiao sheng wen <atzlinux@sina.com> | not-needed | 2026-07-15 | ||
| 0011-drop-python-cli-entry-point.patch | Drop the python console_scripts opencc entry point Since 1.4.x, setup.py registers a "opencc" console_scripts entry point (opencc.cli:main). debian/rules runs the pybuild install step after the cmake install step, so this Python wrapper script overwrites the compiled C++ /usr/bin/opencc CLI tool installed by the opencc binary package, and it lacks a corresponding python3 dependency. Drop the entry point; the compiled CLI tool remains the one and only /usr/bin/opencc, and the python3-opencc bindings (import opencc) are unaffected. =================================================================== |
Frank Lin <debian@linshuang.info> | no | 2026-07-15 | ||
| 0012-fix-legacy-dict-detection-on-big-endian.patch | Fix legacy 64-bit OCD layout detection on big-endian platforms The BinaryDict and DartsDict deserializers detected the legacy 64-bit layout by checking whether probe bytes [4..7] are zero, which only holds on little-endian hosts; on big-endian platforms (s390x, ppc64, sparc64, hppa) legacy files were misread as fixed-width and loaded as empty dictionaries. Replace the byte-offset idiom at all three sites with a shared LooksLikeLegacy64Field() helper that loads the probe as a native uint64_t and checks its high 32 bits, which is correct on both byte orders and compiles to the same behavior on little-endian. Verified with BinaryDictTest and DartsDictTest on arm64 and on emulated s390x. This fixes the following test failures on all big-endian Debian architectures (s390x, powerpc, ppc64, sparc64, hppa): BinaryDictTest.AcceptsLegacy64BitLayout BinaryDictTest.RejectsHugeValueTotalLength DartsDictTest.LoadsLegacy64bitFormat DartsDictTest.Legacy64PrefixSearchBeyond64Matches DartsDictTest.Legacy64SerializeToFileThrows |
Frank Lin <github@linshuang.info> | no | 2026-08-04 |
All known versions for source package 'opencc'
- 1.4.1+ds1-7 (sid)
- 1.4.1+ds1-3 (forky)
- 1.1.9+ds1-1+deb13u1 (trixie)
- 1.1.6+ds1-1 (bookworm)
