KDE CI: Plasma » kde-gtk-config » kf5-qt5 SUSEQt5.12 - Build # 122 - Fixed!

BUILD SUCCESS Build URL https://build.kde.org/job/Plasma/job/kde-gtk-config/job/kf5-qt5%20SUSEQt5.12/122/ Project: kf5-qt5 SUSEQt5.12 Date of build: Tue, 17 Mar 2020 08:48:33 + Build duration: 1 min 13 sec and counting JUnit Tests Name: (root)

D28086: Improve CMake handling of GNOME libraries

gikari requested changes to this revision. gikari added a comment. This revision now requires changes to proceed. I reverted the commits ( R99:306e01d86ab9a891ec70219802ce01572b0d4025 and

D28095: Bump required version of KF5 to 5.69.0

ahmadsamir created this revision. ahmadsamir added reviewers: Frameworks, dfaure, apol, sitter. Herald added a project: Plasma. Herald added a subscriber: plasma-devel. ahmadsamir requested review of this revision. REVISION SUMMARY KCrash::setErrorMessage() was introduced in 5.69.0. REPOSITORY

D28095: Bump required version of KF5 to 5.69.0

This revision was automatically updated to reflect the committed changes. Closed by commit R871:ce461918868d: Bump required version of KF5 to 5.69.0 (authored by ahmadsamir). REPOSITORY R871 DrKonqi CHANGES SINCE LAST UPDATE https://phabricator.kde.org/D28095?vs=77812=77813 REVISION DETAIL

KDE CI: Plasma » drkonqi » kf5-qt5 FreeBSDQt5.13 - Build # 70 - Still Failing!

BUILD FAILURE Build URL https://build.kde.org/job/Plasma/job/drkonqi/job/kf5-qt5%20FreeBSDQt5.13/70/ Project: kf5-qt5 FreeBSDQt5.13 Date of build: Tue, 17 Mar 2020 10:14:29 + Build duration: 34 sec and counting CONSOLE OUTPUT [...truncated 292

KDE CI: Plasma » drkonqi » kf5-qt5 WindowsMSVCQt5.14 - Build # 15 - Still Failing!

BUILD FAILURE Build URL https://build.kde.org/job/Plasma/job/drkonqi/job/kf5-qt5%20WindowsMSVCQt5.14/15/ Project: kf5-qt5 WindowsMSVCQt5.14 Date of build: Tue, 17 Mar 2020 10:14:30 + Build duration: 54 sec and counting CONSOLE OUTPUT

Re: Problems in KWayland causes by API and ABI compatibility promises

There's definitely a problem, and I think it's a lot more than just discussing location and protocol versions. My typical workflow is reading the wayland protocol in detail, and kwayland is in that awkward position where I absolutely still need to read those underlying docs and the abstraction

<    1   2