Your message dated Fri, 11 Sep 2026 17:13:50 +0000
with message-id <[email protected]>
and subject line Bug#1147324: Removed package(s) from unstable
has caused the Debian Bug report #1144750,
regarding fcitx: 4.x unmaintained upstream, superseded by src:fcitx5
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 [email protected]
immediately.)
--
1144750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144750
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fcitx
Severity: important
Tags: upstream wontfix
Forwarded: https://lists.debian.org/debian-input-method/2024/10/msg00042.html
X-Debbugs-Cc: [email protected]
On 12 Oct 2024, Boyuan Yang wrote:
>According to https://github.com/fcitx/ , it is obvious that the fcitx upstream
>has archived all fcitx 4.x-related development repositories since 2024-05.
>We can now assume that the upstream support for fcitx-* packages is no longer
>available.
>
>With the shift of upstream development and fcitx 4.x being unable to support
>Wayland environment from the very beginning, I believe the support for fcitx4
>input method framework in Debian should be deprecated. Now it should be the
>time to review all the reverse dependencies to fcitx4 and consider migrating
>out of it.
>
>Since we are late in the Debian 13 ("Trixie") development cycle, the package
>deprecation or removal will not happen before Debian 13 release. I believe
>that package removal will not happen earlier than Ubuntu 26.04 LTS release so
>that users and developers will have enough time to make the migration.
>
>A major source of fcitx4 package dependency is the tasksel metapackages.
>Replacing occurrences of fcitx4 in tasksel with fcitx5 should be the first
>thing to do next, and of course, with enough testing from users of different
>locales.
Opening a bug to represent that "dead upstream" status.
We're more than halfway through the Debian 14 cycle. Is it time to
revisit this, and perhaps look more closely at whether fcitx 4.x
can/should be removed before forky?
Dependencies that would be broken by this are:
- libsdl2, libsdl3: the Build-Depends on fcitx-libs-dev is not actually
necessary (SDL only uses fcitx via a D-Bus API), I'm going to remove
it in the next upload
- mozc: builds a fcitx-mozc package, could presumably stop building that
(but continue to build fcitx5-mozc)
- fcitx-autoeng-ng,
fcitx-chewing,
fcitx-configtool,
fcitx-dbus-status,
fcitx-fullwidthchar-enhance,
fcitx-m17n,
fcitx-punc-ng,
fcitx-qimpanel,
fcitx-ui-light:
all seem to be specific to fcitx 4.x, do they have fcitx5-based
replacements?
(This was prompted by me trying to remove the deprecated
libgirepository1.0-dev, which is still needed by fcitx 4.x,
<https://bugs.debian.org/1118813>.)
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1:4.2.9.9-2.1+rm
Dear submitter,
as the package fcitx has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1147324
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
