aurupdater

qt5-nemo-qml-plugin-configuration

Build times (auto-updated)

2026-10-12: pkgrel 1 -> 2, drop /opt/tests to fix file conflict (AUR comment, Skaxen)

Skaxen reported a file conflict installing against the official (now Qt6) nemo-qml-plugin-configuration: both packages own identical paths under /opt/tests/nemo-qml-plugin-configuration-qt5/.... This is exactly the risk the 2026-09-05 entry below predicted (“no declared conflicts/replaces either way”), just hit for test files rather than the plugin binaries. Root cause: upstream’s tests/tests.pro hardcodes the -qt5-suffixed install path regardless of which Qt actually builds it, so the official package kept installing to that same path even after its own Qt6 switch.

Fix: dropped the whole /opt tree from package() (rm -rf "$pkgdir"/opt after make install) rather than adding conflicts=/replaces= – these are upstream CI test binaries, not needed by any real consumer, so removing them from both forks’ packaging eliminates the collision outright instead of just forcing pacman to make the user choose one package over the other. Packaging-only, pkgrel 1 -> 2 per [[feedback_pkgrel_vs_pkgver]]. Built and published clean (x86_64) via repo_release.sh. Did not reply on AUR – matches [[feedback_obvious_fixes_no_aur_reply]].

Note: despite the “Category: local-install” note just below, this package is now vendored under maintained/ with an AUR origin remote (confirmed via check_aur_feedback.sh surfacing Skaxen’s comment) – the local-install staging described below has since been promoted.

Category: local-install (rebuilt to unblock qt5-quickcontrols-nemo’s own adoption; not vendored under arch/ yet). Path: /data/INSTALL/qt5-nemo-qml-plugin-configuration, a plain (non-submodule) git checkout, same pattern as qt5-mlite/[[qt5-mlite]].

Build times (auto-updated)

2026-09-05: forked from official nemo-qml-plugin-configuration to stay on Qt5