[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#888563: transition: fcitx



Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Dear Release Team,

I'm working to push fcitx 4.2.9.5 into unstable.
Fcitx upstream bumped the SONAME of one of its libraries,
libfcitx-gclient. This is a really tiny transition that only
affects one package outside fcitx world (mlterm):

% LC_ALL=C.UTF-8 apt rdepends libfcitx-gclient0
libfcitx-gclient0
Reverse Depends:
  Depends: fcitx-frontend-gtk2 (>= 4.2.9)
  Depends: libfcitx-gclient0-dbgsym (= 1:4.2.9.4-3)
  Depends: mlterm-im-fcitx (>= 4.2.7)
  Depends: fcitx-imlist (>= 4.2.7)
  Depends: fcitx-frontend-fbterm (>= 4.2.7)
  Depends: fcitx-config-gtk (>= 4.2.7)
  Depends: gir1.2-fcitx-1.0 (>= 4.2.9)
  Depends: fcitx-libs-dev (= 1:4.2.9.4-3)
  Depends: fcitx-libs (>= 1:4.2.9.4-3)
  Depends: fcitx-frontend-gtk3 (>= 4.2.9)

I will handle every reverse-dependency named after fcitx
(requesting binNMU or uploading the updated package).

As for package mlterm, I rebuilt it against the new fcitx. The build
is okay but the program won't start. I've filed bug #887711 for it.
If the bug cannot be fixed soon, I'm planning to disable mlterm's fcitx
support in an NMU later.

    https://bugs.debian.org/887711

Automatic transition tracker:

    https://release.debian.org/transitions/html/auto-fcitx.html

NB. the missing fcitx-module-quickphrase-editor there has no reverse-dependency
thus
does not affect the transition.

Thanks,
Boyuan Yang



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


Reply to: