aurupdater

qt5-mlite

Build times (auto-updated)

2026-09-21: conflicts/provides against extra/mlite (pkgrel 1 -> 2)

AUR comment (Skaxen, 2026-09-13): file conflict installing qt5-mlite over mlite (/usr/bin/mlitenotificationtool, /usr/lib/mliteremoteaction both owned). Root cause: extra/mlite (Felix Yan’s package, same upstream sailfishos/mlite, same version 0.5.5) was rebuilt against Qt6 (depends=qt6-base) and kept the bare mlite name – unlike the other ~18 qt5-* packages in this tree, mlite isn’t a namespaced Qt module (no /usr/lib/qt5/... subpath), it’s an app-like lib installing plain top-level binaries, so the Qt5 and Qt6 builds inevitably collide on the same paths. This is inherent to the two builds coexisting, not a packaging bug – checked with the user, decided to keep this package where it is in maintained/ (no broader qt5-*-family directory reorg) and just fix the conflict declaration.

Fix: added provides=("mlite=$pkgver") and conflicts=('mlite') so pacman treats them as mutually-exclusive alternatives instead of erroring on a raw file conflict. Pure packaging fix, no source change -> pkgrel 1 -> 2. Built and published cleanly (x86_64 only, per arch=()). No AUR reply posted (see [[python2]]’s 2026-09-21 entry for why – this project’s tooling never posts to AUR).

Re-checked 2026-09-24 (FEEDBACK.txt sweep): no new comments since, Skaxen’s report stays resolved by the pkgrel 2 fix above.