Actually not. Some dependency definition is missing, so packagekit-qt5 never gets pulled… Maybe plasma-workspace should depend on packagekit-qt5?
PS: Sorry for answering an slightly old thread, but a moment ago other user asked in a Telegram group about it and I noticed that I had the same issue. Although I solved it I was a bit curious if others had noticed this before.
packagekit-qt5 is optional for plasma-desktop and frameworkintegration.
Based on the latest KDE description brand that can be read here Repositioning the KDE Brand | KDE.news
The order of importance and subsequent dependencies is Workspace < Desktop < Packagekit
I see your point, but in practice a user without technical knowledge just see an error and have no clue how to solve it. That it’s just what I’m saying.
@bogdancovaciu already mentioned which packages contain those files, so you can deduce from that what you need.
But in general if some file (usually a library) is missing you can always update file database (so you have latest info) and (regex) search to which package it belongs: