Bug 482080 - breeze and plasma-integration Qt5 builds not installed by default
Summary: breeze and plasma-integration Qt5 builds not installed by default
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-29 19:23 UTC by Jens Küspert
Modified: 2024-03-01 16:48 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed 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 Jens Küspert 2024-02-29 19:23:14 UTC 
SUMMARY
***
The binary package of ktimetracker has not been built since 2022-09-08.
When installing on a freshly upgraded Neon with Plasma 6 and KF6 it looks ugly, since it uses kf5-libs.
This does *not* happen in testing, since it is built with new liberaries.
***


STEPS TO REPRODUCE
1. Take Neon user
2. Install ktimetracker (version 4:5.0.1-3+22.04+jammy+release+build3)
3. Start ktimetracker

OBSERVED RESULT
Dependencies to kf5.

EXPECTED RESULT
Usage of kf6 (as in Neon testing).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon 22.04
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0 (ktimetracker says 5.115.0)
Qt Version: 6.6.2 (ktimetracker says 5.15.12)
Comment 1 David Redondo 2024-03-01 12:49:51 UTC 
The problem seems to be breeze and plasma-integration for Qt5 are not installed by default
Comment 2 Jens Küspert 2024-03-01 15:46:02 UTC 
(In reply to David Redondo from comment #1)
> The problem seems to be breeze and plasma-integration for Qt5 are not
> installed by default

That could be an explanation for the look.
In my opionion it would be more straight-forward to build the timetracke against kf6 and qt6, just as in testing.

Anyway: What packages need to be installed in order to get breeze ans plasma-integration für Qt5?
Comment 3 Harald Sitter 2024-03-01 16:48:07 UTC 
Should be fixed in latest snapshot.