#3288 Request for exception: libquotient 0.9.0 (No longer builds for qt5)
Closed: Accepted by sgallagh. Opened by farchord.

Libquotient has released a new update, 0.9.0. The following apps use that library

[KDE Stack]
itinerary
neochat

[External]
quaternion

The breaking change in this version is that it no longer builds for qt5. So this would be qt6 only from now on. I checked, and all depending apps already build on top of qt6 only, and the kde-sig group has access to those dist-gits so they can all be rebuilt. But the qt5 subpackage will need to be dropped.

Updating to 0.9.0 is important because functionality in neochat as things stand is partially broken as, if your homeserver is matrix.org, you currently get no avatar, no gifs, no videos, images, and so on (according to a user, I can't verify as I no longer have a matrix.org account) and neochat is a core app of the kde experience.

Thank you!


Metadata Update from @ngompa:
- Issue tagged with: updates policy exception

Well, we could make the old version available as a compatibility package to continue providing the Qt5 version for stable releases and update the main libquotient library still.

That might avoid needing an exception?

Well, we could make the old version available as a compatibility package to continue providing the Qt5 version for stable releases and update the main libquotient library still.

That might avoid needing an exception?

Here's my thought about this though, the current version of libquotient, as I said, has broken functionality... Yeah we could make a compat package, but I don't see how future apps would be built against libquotient-qt5 as it's kindof broken as things stand right now, so it'd be basically unused, no?

+1 to update. I don't think it makes sense to cling to old versions if they are not functional. Better to move things along and fix bugs.

+1, for the same reason.

We're at (+6, 0, 0) after ~5 days.

After a week (and some change):
APPROVED (+7, 0, 0)

@fesco members: if you see a ticket that was approved according to rules, please consider doing to "APPROVED" message and setting pending announcement, so that people don't need to wait longer for the result.

Metadata Update from @zbyszek:
- Issue tagged with: pending announcement

Announced

Metadata Update from @sgallagh:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Metadata