Your message dated Fri, 28 Feb 2025 17:02:49 +0000 with message-id <E1to3lB-0003fV-A9@fasolo.debian.org> and subject line Bug#1099094: fixed in fcitx5-keyman 1.1.2-2 has caused the Debian Bug report #1099094, regarding fcitx5-keyman: FTBFS against keyman 18.0.199 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1099094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099094 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: fcitx5-keyman: FTBFS against keyman 18.0.199
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Fri, 28 Feb 2025 10:37:59 +0100
- Message-id: <[🔎] Z8GD99aSkR-dh8MJ@ramacher.at>
Source: fcitx5-keyman Version: 1.1.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramacher@debian.org https://buildd.debian.org/status/fetch.php?pkg=fcitx5-keyman&arch=amd64&ver=1.1.2-1%2Bb1&stamp=1740728874&raw=0 [ 92%] Built target fcitx5-keyman-translation In file included from /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:8: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.h:57:26: error: ‘km_core_cp’ does not name a type; did you mean ‘km_core_cu’? 57 | void setOption(const km_core_cp *key, const km_core_cp *value); | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.h:57:49: error: ‘km_core_cp’ does not name a type; did you mean ‘km_core_cu’? 57 | void setOption(const km_core_cp *key, const km_core_cp *value); | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp: In function ‘std::string fcitx::{anonymous}::get_current_context_text_debug(km_core_state*)’: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:111:5: error: ‘km_core_cp’ was not declared in this scope; did you mean ‘km_core_cu’? 111 | km_core_cp *buf = | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:111:17: error: ‘buf’ was not declared in this scope 111 | km_core_cp *buf = | ^~~ /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:120:9: error: ‘km_core_cp_dispose’ was not declared in this scope; did you mean ‘km_core_cu_dispose’? 120 | km_core_cp_dispose(buf); | ^~~~~~~~~~~~~~~~~~ | km_core_cu_dispose /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp: In member function ‘void fcitx::KeymanState::updateContext()’: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:199:41: error: ‘km_core_cp’ does not name a type; did you mean ‘km_core_cu’? 199 | state, reinterpret_cast<km_core_cp *>(utf16Context.data())); | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:199:52: error: expected ‘>’ before ‘*’ token 199 | state, reinterpret_cast<km_core_cp *>(utf16Context.data())); | ^ /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:199:52: error: expected ‘(’ before ‘*’ token /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:199:53: error: expected primary-expression before ‘>’ token 199 | state, reinterpret_cast<km_core_cp *>(utf16Context.data())); | ^ /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp: In member function ‘void fcitx::KeymanKeyboardData::load()’: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:323:9: error: ‘km_core_keyboard_load’ was not declared in this scope; did you mean ‘km_core_keyboard_key’? 323 | km_core_keyboard_load(kmxPath.data(), &keyboard_); | ^~~~~~~~~~~~~~~~~~~~~ | km_core_keyboard_key /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp: At global scope: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:340:49: error: ‘km_core_cp’ does not name a type; did you mean ‘km_core_cu’? 340 | void fcitx::KeymanKeyboardData::setOption(const km_core_cp *key, | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:341:49: error: ‘km_core_cp’ does not name a type; did you mean ‘km_core_cu’? 341 | const km_core_cp *value) { | ^~~~~~~~~~ | km_core_cu /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp: In member function ‘virtual void fcitx::KeymanEngine::keyEvent(const fcitx::InputMethodEntry&, fcitx::KeyEvent&)’: /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:515:71: error: cannot convert ‘const km_core_cu*’ {aka ‘const char16_t*’} to ‘const int*’ 515 | keyman->keyboard()->setOption(actions->persist_options[i].key, | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ | | | const km_core_cu* {aka const char16_t*} /build/reproducible-path/fcitx5-keyman-1.1.2/src/engine.cpp:340:61: note: initializing argument 1 of ‘void fcitx::KeymanKeyboardData::setOption(const int*, const int*)’ 340 | void fcitx::KeymanKeyboardData::setOption(const km_core_cp *key, | ~~~~~~~~~~~~~~~~~~^~~ make[3]: *** [src/CMakeFiles/keyman.dir/build.make:82: src/CMakeFiles/keyman.dir/engine.cpp.o] Error 1 Cheers -- Sebastian Ramacher
--- End Message ---
--- Begin Message ---
- To: 1099094-close@bugs.debian.org
- Subject: Bug#1099094: fixed in fcitx5-keyman 1.1.2-2
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Fri, 28 Feb 2025 17:02:49 +0000
- Message-id: <E1to3lB-0003fV-A9@fasolo.debian.org>
- Reply-to: Boyuan Yang <byang@debian.org>
Source: fcitx5-keyman Source-Version: 1.1.2-2 Done: Boyuan Yang <byang@debian.org> We believe that the bug you reported is fixed in the latest version of fcitx5-keyman, 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 1099094@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 fcitx5-keyman 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) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 28 Feb 2025 10:56:00 -0500 Source: fcitx5-keyman Architecture: source Version: 1.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org> Changed-By: Boyuan Yang <byang@debian.org> Closes: 1099094 Changes: fcitx5-keyman (1.1.2-2) unstable; urgency=medium . * debian/patches/066e3ef80f73e236592c8d743bf3be88a06c3c16.patch: Apply patches from upstream to fix compatibility with keyman 18.x. (Closes: #1099094) Checksums-Sha1: acf9621f503100cbc44be6dbf2f6fd50ffae557f 2106 fcitx5-keyman_1.1.2-2.dsc e392fbf92c5f6348c5e3731bfbca588f96da8fb9 17348 fcitx5-keyman_1.1.2.orig.tar.xz 6b3a0f63fc64beeb16c2f1eb4180eae2be330521 5768 fcitx5-keyman_1.1.2-2.debian.tar.xz 64e200ee54588471590083f53aaa73d84b984654 7481 fcitx5-keyman_1.1.2-2_amd64.buildinfo Checksums-Sha256: 6273baebab009949499cc746e1c8518ed7dce8e7f2cc92ad977501f5fc508aaf 2106 fcitx5-keyman_1.1.2-2.dsc 87ea8954e2d4d9f6c87bf409b52eb97e66e61f9188ad0371cf737076dfd799c7 17348 fcitx5-keyman_1.1.2.orig.tar.xz 994f483c8c77fe7b1967d7774af358126c0b3e15b8b1fd600b0475bcd9f00ad5 5768 fcitx5-keyman_1.1.2-2.debian.tar.xz d5fc38a0833bf8df84b84e67ccbf27dbccf1af3b7bfe2a014c4791a573c36c57 7481 fcitx5-keyman_1.1.2-2_amd64.buildinfo Files: 0c78088497e6ca9695830e1c5cbc8cfd 2106 utils optional fcitx5-keyman_1.1.2-2.dsc ab46563eeebe530b5cb24fcab0a6b4a2 17348 utils optional fcitx5-keyman_1.1.2.orig.tar.xz e84efac37505d01802bf39ebe3c96b0b 5768 utils optional fcitx5-keyman_1.1.2-2.debian.tar.xz c4885890c9a8e4341ba4801039a44a5a 7481 utils optional fcitx5-keyman_1.1.2-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmfB3eEACgkQwpPntGGC Ws7duw/+Nb0NUm+K7aOPDewWefIvFzqIxAVet9gCL77Ul+lrNsxuMam8ocRyc9Qp jnyuAiq3JrSMzP5OOJFTR8b1xjscpZxlmYeuJtAD+GmNznfC+mdcpjUNb9o+HQd+ kp012O0iVGbky6L1Bh7s9JXQqgQDfVRssz8YE371evuf3Q7Q07NhwccfwmJICZ7H YnnGc5K9xPndixkf3WEnGC0N1+31RLv2TtvW0rH0hRWxPGPiMMN01PdxAuLaA3GE LyCQ11j3kaDjLRuThJYEuf0CZIX/JQL7NP6tYWMBPrL73FMcBARljlj60HSAdUgI 5G4wslg32Je4BwDQUeiE4XZXq0PIMKhvX9MqG7QlaFS1EfBMOkBzbZHjiOv+xdwf 2u8jfAVGJvLHFFXzZGhh/WADtqkLTw4KgIPdGFjEEyhVB1LnjRDKG8L+3IeiAaRl qD4PSVNUxECFv4qZvL4XrSHWipmJ5McwJ1qb3E8UV3Y9mVXbHzGX1hJ9mn9hP+X2 3fkLWw3mwXRC9nd4mPRcno+7LbB0Kw3ipM2JWNg64iclnoLTmpFFDxr0y/Y5WvG9 dJiBwrPSg4AJnpRTCU6RJFeLEvXK/E5iox6pc0qLXwo1lL+yCVGL/1l4yy9VBqsV c5yWrFxQtp5rpE+7JjfyFceLtbyoLD6zikFoooQMOskp2Ezk6AU= =SSnn -----END PGP SIGNATURE-----Attachment: pgp2vMKF5HRoW.pgp
Description: PGP signature
--- End Message ---