| Summary: | fcitx5 backports package not complete. | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | strayingfar |
| Component: | Packages User Edition | Assignee: | Neon Bugs <neon-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | carlosd.kde, jr, neon-bugs, sitter |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
strayingfar
2023-12-03 14:43:55 UTC
new versions just landed. does this fix the issue for you. (In reply to Carlos De Maine from comment #1) > new versions just landed. does this fix the issue for you. I don't see any new version. Does it reach the stable channel? aahh i see. fcitx5 is the latest - 5.1.5 https://archive.neon.kde.org/testing/pool/main/f/fcitx5/ but neon needs to backport kde-config-fcitx5 whis is mysteriously named fcitx5-configtool upstream https://github.com/fcitx/fcitx5-configtool will do as soon as tooling is up and running is it correct to assume that all 27 fcitx5 repos upstream at github should be packaged to provide all the supported backends/plugins of fcitx5?? https://github.com/orgs/fcitx/repositories?q=fcitx5&type=all&language=&sort= (In reply to Carlos De Maine from comment #4) > is it correct to assume that all 27 fcitx5 repos upstream at github should > be packaged to provide all the supported backends/plugins of fcitx5?? > https://github.com/orgs/fcitx/repositories?q=fcitx5&type=all&language=&sort= I think it's true, but i"m not very sure about that.😂 all of fcitx5 is now in backports for neon |