First, we'll need an upstream org.kde.{Platform,Sdk} with KF6 included. Any timeline for that? We will use that to add KF6 to org.fedoraproject.KDE6{Platform,Sdk} (aka flatpak-kde6-{runtime,sdk}).

Also, is there a list of KDE Gear apps which are staying on KF5 for now?

At this point I'm assuming that I'll be heavily involved in migrating our flatpaks to F40, so I'll take this.

Thanks! The work on the KF6 runtime is in progress for Flathub.
Ideally we get at least one other person working with you to learn about the process and offload part of the work. This should be a good opportunity for contributors to get involved.

org.kde.{Platform,Sdk}//6.6 now include KF6, so I was able to make a first draft of a runtime update:

https://src.fedoraproject.org/flatpaks/flatpak-kde6-runtime/pull-request/1

Right now, the biggest issue is kf6-kio-core's dependency on switcheroo-control. That needs to either be softened at least, or perhaps moved to comps etc. See https://src.fedoraproject.org/rpms/kf6-kio/pull-request/3

Next issue: the kf5-kwallet-libs->kf5-kwallet->kf6-kwallet dependencies would pull KF6 components into the KDE5 runtime (which will still be needed at least for F40): https://src.fedoraproject.org/rpms/kf5-kwallet/pull-request/4

UPDATE: merged and built

Question: org.kde.Platform//6.6 includes libphonon4qt6 but no phonon backend. Is that an oversight? The only supported backend is now vlc. Even vlc-plugins-base will pull in a lot more libraries than previously, so we may want to reconsider the division of plugins in vlc. /cc @ngompa

One more KF6-in-KDE5 runtime issue: https://src.fedoraproject.org/rpms/kf5-kguiaddons/pull-request/3

Hopefully the last KF6-in-KDE5 issue, only in the SDK: https://src.fedoraproject.org/rpms/extra-cmake-modules/pull-request/4

There is an initial build of the KDE runtimes for F40, and I'm starting to work on the apps. Unfortunately, the recent addition of qch generation has broken /app builds of all frameworks not in the runtime, because QTQCHDIR does not match %_qt6_docdir. As a result, the qch doc files are installed in /usr but %files is looking for them in /app, and the build fails as a result.

/cc @loise

Would it make sense to turn the docs off for Flatpak builds?

Would it make sense to turn the docs off for Flatpak builds?

If they were already conditional, I would say yes, but since they are not, it would mean another round of spec updates. It may be simpler to simply define KDE_INSTALL_QTQCHDIR in %cmake_kf6. Trying this now.

Filed https://src.fedoraproject.org/rpms/kf6/pull-request/6

Filed https://src.fedoraproject.org/rpms/kf6/pull-request/6

This has solved the problem with qch docs installation.

Build fixes needed:
https://src.fedoraproject.org/rpms/discount/pull-request/2
https://src.fedoraproject.org/rpms/kalarm/pull-request/1
https://src.fedoraproject.org/rpms/kf6-baloo/pull-request/4
https://src.fedoraproject.org/rpms/libmusicbrainz5/pull-request/3
https://src.fedoraproject.org/rpms/protobuf/pull-request/27

Also, kolorfill builds but does not run on Qt6, works fine with Qt5:
https://src.fedoraproject.org/rpms/kolorfill/pull-request/1

The runtimes and most Gear apps are now in testing; the default Kinoite apps are on their way to stable for inclusion in the RC.

Most of gear is now stable at 24.02.2 on F40, a few stragglers are now in testing. Remaining issues:

• digikam is currently blocked by an hdf5 PR;
• pandoc-cli (for ghostwriter) does not build correctly;
• kleopatra now depends on akonadi. it previously did not and therefore was flatpak'ed separately, but until now all akonadi-dependent components have been shipped with kontact to have a single akonadi instance. kleopatra is technically not PIM though and can be used without it. Either we could simply drop the standalone app, or allow a standalone version to talk to another instance. (Perhaps this depends more on how much PIM uses kleopatra rather than the other way around.)

This is done.

Thanks!