https://bugs.kde.org/show_bug.cgi?id=510072
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/-/commit/79df60 |ma/discover/-/commit/638c22 |ca93f554ed2078ffb855e4f1633 |4f9916573ffe3dc6ca0ed3c49e8 |cbd2dab |622b1d4 --- Comment #5 from Nate Graham <[email protected]> --- Git commit 638c224f9916573ffe3dc6ca0ed3c49e8622b1d4 by Nate Graham. Committed on 02/10/2025 at 13:38. Pushed by ngraham into branch 'Plasma/6.5'. kcm: Restore runtime check for OSTree backend It's possible to build discover with the OSTree backend while running on a system that doesn't actually use OSTree. This would mean there's no option for selecting how system updates work even though the system supports choosing that, as the current logic is purely tied to a compile time check. This restores the runtime check if the OSTree backend was built. The systemd case is still based on a compile-time check as I don't know how to check that at runtime. (cherry picked from commit 79df60ca93f554ed2078ffb855e4f1633cbd2dab) Co-authored-by: Arjen Hiemstra <[email protected]> M +6 -4 kcm/CMakeLists.txt M +7 -1 kcm/updates.cpp https://invent.kde.org/plasma/discover/-/commit/638c224f9916573ffe3dc6ca0ed3c49e8622b1d4 -- You are receiving this mail because: You are watching all bug changes.
