Bug 376120 - Repackage fcitx-frontend-qt5
Summary: Repackage fcitx-frontend-qt5
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-07 03:37 UTC by trmdi
Modified: 2025-09-20 09:36 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description trmdi 2017-02-07 03:37:28 UTC
Please remove the depend: qtbase-abi-5-5-1
from the package: fcitx-frontend-qt5

Because libqt5core5a includes qtbase-abi.
It will prevent user installs the package fcitx-frontend-qt5.

"The following packages have unmet dependencies:
 fcitx-frontend-qt5 : Depends: qtbase-abi-5-5-1"

I'm using KDE Neon User Edition.
The package has error in packaging: fcitx-frontend-qt5/now 1.0.5-1 amd64
Comment 1 Jonathan Riddell 2017-02-07 22:05:47 UTC
added and updated
Comment 2 Jacob Zhong 2021-08-19 00:10:16 UTC
Hi, I found this issue happens again on the latest KDE Neon. The error message is

```
Investigating (0) fcitx5-frontend-qt5:amd64 < none -> 0.0~git20200118.2e38c95-1build3 @un puN Ib >
Broken fcitx5-frontend-qt5:amd64 Depends on qtbase-abi-5-12-8:amd64 < none @un H >
  Considering libqt5core5a:amd64 3773 as a solution to fcitx5-frontend-qt5:amd64 9999
Done
```

I guess it's the same issue and could you help to repackage it?
Comment 3 Jumpei Ogawa 2023-05-11 00:58:20 UTC
I think this thread can be closed because this issue is resolved in https://bugs.kde.org/show_bug.cgi?id=461620
Comment 4 Carlos De Maine 2025-09-20 09:36:22 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!