Package Details: sonic-frameworks-quick-ui 6.27.0-1

Git Clone URL: https://aur.archlinux.org/sonic-frameworks-quick-ui.git (read-only, click to copy)
Package Base: sonic-frameworks-quick-ui
Description: A QtQuick based components set
Upstream URL: https://github.com/Sonic-DE/sonic-frameworks-quick-ui
Licenses: LGPL-3.0-only, LGPL-2.0-only
Groups: sonicde-frameworks
Conflicts: kirigami
Provides: kirigami
Submitter: sonicde-buildbot
Maintainer: sonicdesktop (callmetango, jcrowell, sonicde-buildbot)
Last Packager: sonicde-buildbot
Votes: 0
Popularity: 0.000000
First Submitted: 2026-06-18 17:23 (UTC)
Last Updated: 2026-06-18 17:23 (UTC)

Required by (172)

Sources (1)

Latest Comments

callmetango commented on 2026-07-14 21:10 (UTC)

@jghodd

sonic-frameworks-quick-ui is a drop-in replacement for kirigami and conflicts with it at the moment 179f19eb1f9c. That's a consequence of forking the KDE packages. Upstream is looking into a solution to have KDE and SonicDE installed at the same time.

jghodd commented on 2026-07-01 20:34 (UTC) (edited on 2026-07-03 14:12 (UTC) by jghodd)

There is a conflict with kirigami2:


error: failed to commit transaction (conflicting files)
/bslx/bslxlive/bslx-base/x86_64/work/x86_64/airootfs/usr/share/locale/ja/LC_MESSAGES/libkirigami2plugin_qt.qm exists in both 'sonic-frameworks-quick-ui' and 'kirigami2'
Errors occurred, no packages were upgraded.

I'm going to be testing this via a live system image, built with archiso. It is impossible to do anything "special" to install both of these while there is a conflict - archiso has no allowance for special cases. Please fix this.

Edit: I was able to find all packages that pulled in kirigami, but it took me about 16 hours to do it, cross-referencing dependencies and requirements. The final culprit... kup. Too many packages are still pulling in plasma5 pieces, many of which have a need to pull in kirigami. This makes building a live image with 1500 packages a bit of chore when you need to find the handful of packages that require kirigami. It may not be absolutely necessary to get rid of the conflict since the software can be arranged so that there is no conflict, the scope of trying to resolve that conflict when trying to deal with a massive multi-package installation is daunting. Maybe there's a better solution.