qt5-quickcontrols-nemo

Build times (auto-updated)

x86_64: 1m2s (2026-09-06 07:30 UTC, serial)

Category: maintained/qt5-quickcontrols-nemo (adopted from official Arch repos – flagged by buildmaster’s “Missing state file” checker as a candidate to move to the AUR; see https://buildmaster.archlinux32.org/checker/summary.html).

2026-09-05: adopted from official repos

Dropped from: extra-x86_64
Method used: B (no AUR repo existed, cloned straight from gitlab packaging repo)
Reason dropped upstream: unknown, needs manual look
Conflict notes: n/a (Method B, no merge performed)

2026-09-05: build failure – transitive Qt5/Qt6 mlite conflict, fixed via a Qt5 fork chain

Interesting discovery: the PKGBUILD’s own header already credits # Maintainer: Andreas Baumann / # Contributor: Felix Yan – this was originally our own AUR package before Felix Yan (an Arch TU) adopted it into the official repos. It’s now come full circle back to us via the buildmaster adoption flow.
First archbuild attempt failed with all 6 depends reported “missing”: nemo-qml-plugin-configuration, nemo-theme-glacier, qt5-graphicaleffects, qt5-quickcontrols, qt5-virtualkeyboard, qt5-mlite. Root cause was only the last two – neither existed in any configured repo (AUR-only) – but a failed batch pacman -S reports the whole requested set as missing, not just the actual blockers. Fixed by building+publishing both to archlinuxaba (see [[qt5-mlite]], [[qt5-virtualkeyboard]] if that memory file exists).
Second attempt got further (dependency resolution succeeded) but hit a real file conflict: /usr/bin/mlitenotificationtool and /usr/lib/mliteremoteaction exist in both official mlite (Qt6, pulled in transitively by nemo-qml-plugin-configuration, which switched to Qt6 at 0.2.10-2) and our qt5-mlite (Qt5 fork), with no conflicts/replaces declared either way.
Real fix (not a conflicts/replaces band-aid): nemo-qml-plugin-configuration itself needed the same Qt5-fork treatment as qt5-mlite – see [[qt5-nemo-qml-plugin-configuration]]. Forked at its last Qt5 commit (0.2.10-1, right before upgpkg: 0.2.10-2: switch to qt6), renamed, depends updated to qt5-mlite. Then this package’s own depends=('nemo-qml-plugin-configuration' ...) was changed to qt5-nemo-qml-plugin-configuration to match. Built and published cleanly after that (5.7.7-2, no version bump – pure dependency-name fix).
Refines “Reason dropped upstream” above: not a single explicit removal commit, but a casualty of the Nemo Mobile stack’s Qt5->Qt6 migration – a Qt5-only leaf package left behind once its sibling packages (at least nemo-qml-plugin-configuration) moved to Qt6. nemo-theme-glacier, qt5-graphicaleffects, qt5-quickcontrols, qt5-virtualkeyboard did NOT need the same treatment – only the mlite dependency chain collided.
Still staged at /data/INSTALL/qt5-quickcontrols-nemo (Method B, not yet pushed to AUR/vendored into maintained/ – that’s a deliberate manual step per adopt_package.sh’s design, done by hand after review).

2026-09-08: false UPD flag fixed – upstream’s own Qt5->Qt6 migration, same story as above

STATES.txt flagged 5.7.7 -> 6.4.3 as UPD. Confirmed real (upstream genuinely tagged 6.4.3), but checked that tag’s CMakeLists.txt: find_package(Qt6 COMPONENTS Core Gui Qml Quick Test REQUIRED) – upstream itself migrated to Qt6 starting at tag 6.0, same underlying story as the nemo-qml-plugin-configuration fork above. This package depends entirely on qt5-* packages and is deliberately pinned to the last Qt5-era tag, so bumping to 6.4.3 would both require a Qt6 rebuild and break every qt5-* dependency. Not a routine bump.

Fixed at the nvchecker level rather than leaving it perpetually flagged: added include_regex = "5\\..*" to .nvchecker.toml so only 5.x tags are ever considered. Hit a real nvchecker gotcha getting there – include_regex/exclude_regex match via re.fullmatch(pattern, str(x)), so an anchored-prefix-only pattern like "^5\\." matches nothing (fullmatch requires the whole string, e.g. "5.7.7", to match; "^5\\." alone only ever matches the 2-char string "5."). Needed .* at the end ("^5\\..*" or bare "5\\..*", fullmatch anchors both ends already) to actually match real version strings. Verified directly with nvchecker -c .nvchecker.toml --logger json before and after.