Build v3.14.0 using QT 6

[p-fruck]

Nextcloud client is transitioning to QT6 as QT5 is end of life. My build instructions are based on the changes from nextcloud/desktop#4584 which does not have a stable nextcloud client release yet, so I am currently building from main branch.

The nextcloud client can be built and runs properly. Migrating to QT6 fixes the issues many people (including me) experienced with the deprecated/EOL QT5 runtime.

To the maintainers: The issues around missing elements have not been fixed for quite some time. I cannot afford dedicating large parts of my freetime to this project, but if you are interested in me supporting you maintaining the client, consider reaching out to me, as I also provided a PR for the last visual flatpak runtime issues: #130

[flathubbot]

Started test build 131037

[flathubbot]

Build 131037 failed

[p-fruck]

errors: [flathub-json-automerge-enabled]

Any maintainer has an idea why this happens? Building works fine locally using flatpak run org.flatpak.Builder --user --install ./build-dir/ com.nextcloud.desktopclient.nextcloud.yml

[flathubbot]

Started test build 136184

[flathubbot]

Build 136184 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/119223/com.nextcloud.desktopclient.nextcloud.flatpakref

[hpfr]

errors: [flathub-json-automerge-enabled]

Any maintainer has an idea why this happens? Building works fine locally using flatpak run org.flatpak.Builder --user --install ./build-dir/ com.nextcloud.desktopclient.nextcloud.yml

This appears to be why: Linter breaking change: restricting automatic merge | Flathub Documentation.

The automerge-flathubbot-prs feature has been introduced back in 2019 to reduce maintenance overhead of applications dependent on non-redistributable data. If an extra-data source used by the app disappears because of an update, the automation would ensure that it is still possible to install the app, without requiring manual intervention from the maintainers.

Over time, the feature has started to be misused as a general purpose automation for publishing updates without proper testing. This has led to a number of issues where apps became broken overnight, which could have been easily prevented if the update was tested before merging.

The Nextcloud manifest does not seem to use any extra-data sources, so you can probably update the commit message with this link.

[flathubbot]

Started test build 140000

[p-fruck]

@hpfr thanks for the hint, I updated the commit message

[flathubbot]

Build 140000 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/123037/com.nextcloud.desktopclient.nextcloud.flatpakref

[flathubbot]

Started test build 147368

[flathubbot]

Build 147368 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/130462/com.nextcloud.desktopclient.nextcloud.flatpakref

[p-fruck]

@tilosp From my point of view this PR is ready merge with the recent release of Nextcloud 3.14.0. What do you think?

[tilosp]

Thanks a lot!