Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-input-method@lists.debian.org

Dear mentors and Debian Input Method Team,

I am looking for a sponsor for my package "vielotus":

 * Package name     : vielotus
   Version          : 2.0.0-1
   Upstream contact : Trần Phát Đạt (Steve Dat) <ttd1232004@gmail.com>
 * URL              : https://github.com/stevedat/VieLotus-IM
 * License          : GPL-3.0-or-later
 * Vcs              : https://github.com/stevedat/VieLotus-IM
   Section          : utils

The source builds the following binary packages:

  libvielotus0 - VieLotusIM (Sen Viet) Vietnamese Input Method shared C-ABI
core
  ibus-vielotus - VieLotusIM (Sen Viet) Vietnamese Input Method plugin for
IBus
  fcitx5-vielotus - VieLotusIM (Sen Viet) Vietnamese Input Method plugin
for Fcitx5
  vielotus - VieLotusIM (Sen Viet) - Next-Gen Vietnamese Input Method
metapackage

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/vielotus/

Alternatively, you can download the package with 'dget' using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/v/vielotus/vielotus_2.0.0-1.dsc

Changes for the initial release:

 vielotus (2.0.0-1) unstable; urgency=medium
 .
   * Initial release.
   * Pure C++20 native engine — zero Swift runtime dependency.
   * Native Fcitx5 addon and IBus engine integration.
   * Smart Bilingual English-Vietnamese collision resolution.

Regards,

Hi,

On Fri, 30 Oct 2026 16:23:06 +0700 Dat Tran <ttd1232004@gmail.com> wrote:
 > Package: sponsorship-requests
 > Severity: wishlist
 > X-Debbugs-Cc: debian-input-method@lists.debian.org
 >
 > Dear mentors and Debian Input Method Team,
 >
 > I am looking for a sponsor for my package "vielotus":
 >
 > * Package name : vielotus
 > Version : 2.0.0-1
 > Upstream contact : Trần Phát Đạt (Steve Dat) <ttd1232004@gmail.com>
 > * URL : https://github.com/stevedat/VieLotus-IM
 > * License : GPL-3.0-or-later
 > * Vcs : https://github.com/stevedat/VieLotus-IM
 > Section : utils
 >
 > The source builds the following binary packages:
 >
 > libvielotus0 - VieLotusIM (Sen Viet) Vietnamese Input Method shared C-ABI
 > core
 > ibus-vielotus - VieLotusIM (Sen Viet) Vietnamese Input Method plugin for
 > IBus
 > fcitx5-vielotus - VieLotusIM (Sen Viet) Vietnamese Input Method plugin
 > for Fcitx5
 > vielotus - VieLotusIM (Sen Viet) - Next-Gen Vietnamese Input Method
 > metapackage
 >
 > To access further information about this package, please visit the
 > following URL:
 >
 > https://mentors.debian.net/package/vielotus/
 >
 > Alternatively, you can download the package with 'dget' using this command:
 >
 > dget -x
 > https://mentors.debian.net/debian/pool/main/v/vielotus/vielotus_2.0.0-1.dsc
 >
 > Changes for the initial release:
 >
 > vielotus (2.0.0-1) unstable; urgency=medium
 > .
 > * Initial release.
 > * Pure C++20 native engine — zero Swift runtime dependency.
 > * Native Fcitx5 addon and IBus engine integration.
 > * Smart Bilingual English-Vietnamese collision resolution.

I looked into vielotus 2.0.0-1, mentors upload #5. This version is not ready for sponsorship. See the following issues:
1. This version fails to build from source (FTBFS). See the attached build log. 2. Copyright inconsistencies. The
LICENSE file under the root directory is MIT, yet in debian/copyright you says Files: * is under GPL-3.0-or-later. MIT
is not mentioned anywhere in debian/copyright. Since you are the original upstream author, can you sort out the
licensing condition and document them consistently?

3. Packaging layout error (Multi-Arch). Package |libvielotus0|declares |Multi-Arch: same|, but installs an architecture-dependent symlink at the shared path |/usr/lib/libVieLotusCAPI.so|. With modern Debian, we want to avoid installing files under /usr/lib/ whenever possible. Using
/usr/lib/<arch-triplet>/ should be the default choice and it is well supported by CMake. You may want to read articles
such as https://wiki.debian.org/Multiarch . 4. Packaging layout error (dependency). The Fcitx settings action also
depends on a program shipped only in the IBus package; a Fcitx-only installation needs a working settings entry point.
5. Mismatch source file between Debian-provided tarball and upstream. I cannot find WindowsNativeEngine.cpp/.h file
anywhere on https://github.com/stevedat/VieLotus-IM . Since you are using debian/watch to monitor this repo, a proper
explanation is needed. 6. Destructive setting behaviour. Simply opening vielotus-settings would invoke save_and_apply
before displaying the GUI. This overwrites existing user (or Snap) `fontconfig/fonts.conf` file. This is destructive and
unacceptable; changing user preference must acquire an explicit user consent. It's a generic thing, not specific to
Debian. 7. Input corruption. I tried to type 80 consecutive b characters but only 63 of them are retained. This looks
like a bug. Please look into (and fix) the seven issues above, and prepare another version. Let me know if you have any
questions. Best, Boyuan Yang

The previous email below was not formatted correctly. Resending (see bottom):

在 2026/10/30 19:49, Boyuan Yang 写道:

I looked into vielotus 2.0.0-1, mentors upload #5. This version is not ready for sponsorship. See the following issues:

1. This version fails to build from source (FTBFS). See the attached build log.

2. Copyright inconsistencies. The LICENSE file under the root directory is MIT, yet in debian/copyright you says Files:
* is under GPL-3.0-or-later. MIT is not mentioned anywhere in debian/copyright. Since you are the original upstream
author, can you sort out the licensing condition and document them consistently?

3. Packaging layout error (Multi-Arch). Package libvielotus0 declares  Multi-Arch: same, but installs an
architecture-dependent symlink at the shared path /usr/lib/libVieLotusCAPI.so. With modern Debian, we want to avoid
installing files under /usr/lib/ whenever possible. Using /usr/lib/<arch-triplet>/ should be the default choice and it
is well supported by CMake. You may want to read articles such as https://wiki.debian.org/Multiarch .

4. Packaging layout error (dependency). The Fcitx settings action also depends on a program shipped only in the IBus
package; a Fcitx-only installation needs a working settings entry point.

5. Mismatch source file between Debian-provided tarball and upstream. I cannot find WindowsNativeEngine.cpp/.h file
anywhere on https://github.com/stevedat/VieLotus-IM . Since you are using debian/watch to monitor this repo, a proper
explanation is needed.

6. Destructive setting behaviour. Simply opening vielotus-settings would invoke save_and_apply before displaying the
GUI. This overwrites existing user (or Snap) `fontconfig/fonts.conf` file. This is destructive and unacceptable;
changing user preference must acquire an explicit user consent. It's a generic thing, not specific to Debian.

7. Input corruption. I tried to type 80 consecutive b characters but only 63 of them are retained. This looks like a bug.

8. Input corruption (continued). When I type "turn on", the IM emits "tủn turn on". Is it expected?

Please look into (and fix) the eight issues above, and prepare another version. Let me know if you have any questions.

Best,
Boyuan Yang

Dear Boyuan,

Thank you very much for your thorough review and testing on Debian sid.
I have resolved all 8 issues you reported and uploaded an updated source
package (2.0.0-1) to Debian Mentors:

  dget -x
https://mentors.debian.net/debian/pool/main/v/vielotus/vielotus_2.0.0-1.dsc

  (.dsc SHA256:
0c1b32da294b5d07b1761c07d905a7c8a91587db300dc4299d246bbb4a212f3c)

Summary of fixes matching your 8 review points:

1. Fixed FTBFS on sid (C++20 for Fcitx5 >= 5.1.23):
   - Updated CrossPlatform/fcitx5-vielotus/CMakeLists.txt from C++17 to
     CMAKE_CXX_STANDARD 20 to match current Fcitx5 headers on Debian sid.
   - Verified clean builds on clean debian:sid chroots/containers (g++
     16.2.0, fcitx5 5.1.23-1, lintian 2.143.0) on both amd64 and arm64.

2. Resolved copyright consistency:
   - Updated debian/copyright (Files: * -> Expat, and
     org.vielotus.VieLotus.metainfo.xml -> FSFAP) and the ITP/package
     metadata to consistently reflect the upstream MIT (Expat) license
     in LICENSE.

3. Fixed Multi-Arch shared library layout in libvielotus0:
   - Updated CrossPlatform/capi-native/CMakeLists.txt (GNUInstallDirs
     CMAKE_INSTALL_LIBDIR, VERSION 0.2.0, SOVERSION 0) and
     debian/libvielotus0.install so libVieLotusCAPI.so.0* installs
     exclusively under /usr/lib/<multiarch-triplet>/ with zero files in
     /usr/lib/.

4. Fixed binary package dependency separation (Fcitx5 vs IBus):
   - Guarded the optional settings action in fcitx5-vielotus to check for
     /usr/bin/vielotus-settings at runtime and fall back cleanly to
     fcitx5-configtool when ibus-vielotus is not installed.
   - Added Suggests: ibus-vielotus to fcitx5-vielotus and verified
     standalone installation of libvielotus0 + fcitx5-vielotus without
     ibus-vielotus.

5. Synchronized upstream repository and v2.0.0 tag with orig.tar.xz:
   - Published the full C++20 core engine sources
     (Sources/VieLotusCoreWindows/WindowsNativeEngine.{h,cpp}) and Linux
     adapters to https://github.com/stevedat/VieLotus-IM (including tag
     v2.0.0) so debian/watch / uscan matches vielotus_2.0.0.orig.tar.xz.

6. Removed destructive startup behavior in vielotus-settings:
   - Removed automatic save_and_apply() execution on startup before the
     GTK settings window opens, and removed all writes to
     ~/.config/fontconfig/fonts.conf. Configuration is now written to
     ~/.config/vielotus/config.env only upon explicit user action.

7. Fixed >63 consecutive character truncation:
   - Added automatic preedit chunk flushing at 48 characters in both
     ibus-vielotus and fcitx5-vielotus before the 64-token syllable
     buffer limit is reached. Verified in live IBus and Fcitx5 sessions
     that typing 80+ consecutive 'b' characters retains every character.

8. Fixed "turn on" duplication ("tủn turn on") and session context reset:
   - Fixed the space-commit path so a single commit is emitted per word
     without re-committing composing text, and ensured sentence context
     resets cleanly on input context reset, focus transitions, and line
     breaks / navigation keys while remaining active within a sentence
     (verified in live IBus and Fcitx5 sessions: standalone "turn on " ->
     "tủn on ", subsequent "turn murn " -> "tủn mủn ", and English-primed
     "please turn on " -> "please turn on ").

Please let me know if there are any further improvements needed. Thank
you again for your time and guidance!

Best regards,
Trần Phát Đạt (Steve Dat)