Bug 460680 - Installing kwrite also installs kate
Summary: Installing kwrite also installs kate
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages Unstable Edition (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-18 19:17 UTC by popov895
Modified: 2025-09-20 09:35 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description popov895 2022-10-18 19:17:22 UTC 
SUMMARY

Starting with KDE Gear 22.08, kwrite requires kate, so installing kwrite also installs kate, as well as removing kate also removes kwrite. The part of kate that kwrite depends on (I guess it's the kateprivate library) should be moved to a separate package, and kwrite should no longer depend on kate.

> $ apt depends kwrite
> kwrite
>   Depends: ktexteditor-katepart
>   Depends: kate
>   Depends: libc6 (>= 2.4)
>   Depends: libkf5coreaddons5
>   Depends: libkf5dbusaddons5
>   Depends: libkf5i18n5
>   Depends: libqt5core5a (>= 5.15.5+p20.04+tunstable+git20220912.0057)
>   Depends: libqt5gui5 (>= 5.15.5+p20.04+tunstable+git20220912.0057)
>   Depends: libqt5widgets5 (>= 5.15.5+p20.04+tunstable+git20220912.0057)
>   Depends: libstdc++6 (>= 4.2.1)

Same on KDE neon User Edition.

SOFTWARE/OS VERSIONS

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.6
Graphics Platform: X11
Comment 1 Carlos De Maine 2025-09-20 09:35:52 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!