Right now, this doesn't build anymore, it is failing with:
/home/pmos/build/src/itinerary-c47772e49de6662acd7769d5c8cef94379ea7bcf/src/app/reservationmanager.h:21:10: fatal error: KItinerary/ExtractorRepository: No such file or directory
#include <KItinerary/ExtractorRepository>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've tried to update it to the latest commit, but then it fails with
another error. Turns out, this package depends on kitinerary (with a
k!), and whenever we update that, we also need to update this package
to the latest commit. Unfortunatelly, itinerary does not have tagged
versions yet.
So I would like to remove it for now, it does not seem like anybody is
using it at this point, and so it's just additional maintenance effort
for nothing. We could package it again, when it has tagged versions and
is therefore easy to update together with kitinerary.
Remove kitinerary too, because it isn't used by anything else.
This MR updates the app to the latest commit (currently from 2 days
ago). It also updates plasma-angelfish, but I changed the $pkgrel to
follow the format of the other Git packages.
This also re-enables plasma-angelfish and vvave in the default Plasma
Mobile installation, as they were previously disabled due to
qt5-qtwebengine (which they depend on) requiring a soname bump
upstream.
Add main/qt5-qtspeech, required dependency for kde/kpimtextedit. Disable
check in kde/kimap, as it fails at least with QEMU aarch64.
Change the source url for Sink and Kube to the KDE Download mirror
rather than their GitHub organization (they required rebuilding anyway
due to the applications upgrade).
Since the Qt upgrade, Plasma Mobile boots into a black screen, even
on the current version in the master branch. Bhushan recommended we
update to the latest plasma framework anyway (which is possible now
due to the newer Qt version) and try to fix it from there. See #159.
[skip ci].
ecm_find_qmlmodule checks if QML modules are installed, and if not it
warns during build time. This is purely for packager knowledge. Not
finding those packages here doesn't affect the runtime of the
kwin_wayland at all.
We are disabling this due to bug in the qmlplugindump which causes it to
not return and get stuck, See issue #28.
Revert this when QTBUG-70460 is solved upstream.
This commit adds a test case, which makes sure that the KDE framework
and plasma framework version are always the same.
Additional changes:
* APKBUILD parser parses the URL now (that's the best way I found to
categorize the KDE aports in frameworks and other)
* Changed single quotes to double quotes in KDE APKBUILDs, so the
parser doesn't include the single quotes in the parsed result
* Added the test case to the gitlab CI config
Also includes a revert for the commit which broke the libinput devices
for consolekit session. I am still unsure of solution for both of the
problems to suggest upstream. But it is in my todo list.
Fixes#1585
Disable checks for good.
* half of them would not run anyway because they require X11
* falkon-cookietest hangs for more than 30 minutes with 100% CPU usage
while cross compiling for armhf
That didn't help either, although it did work on a test run on the
same PC that builds the real binary repository packages. Must be
a race condition, see #1458.
This was a circular dependency, because plasma-framework depends on
kirigami2-dev. Furthermore it broke building, because the old
plasma-framework-dev could not be used as it depended on a package that
has been renamed.