Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches
> Besides all the resource costs to create flatpaks on master builds by default every time, when those are usually not used by anyone anyway. It is important to mention that the pipelines on master usually publish to the nightly repos on cdn.kde.org/flatpak I guess you were not aware of that otherwise I wonder what makes you so confident to know nobody uses it? Cheers, Julius 04.02.2024 19:23:06 Ben Cooksley : > On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau > wrote: >> Hi, >> >> ((cc:kde-frameworks-devel for heads-up, replies please only to >> kde-core-deve)) >> >> I hit the problem that when working on a repo which would like to use latest >> KF development state to integrate some new KF API just added in cooperation >> with that very repo wanting to use it, I cannot do so when someone had added >> a >> flatpak job on CI to that repo. >> >> Because with such flatpak jobs it seems they are limiting the available KF >> version not to the current latest one, as expected for continuous >> integration, >> but some older (anywhere documented?) snapshot: >> >> "runtime-version": "6.6-kf6preview", > > Please see https://invent.kde.org/packaging/flatpak-kde-runtime/-/tree/kf6 > for what is in the KF6 preview. > >> >> What can be done here to reestablish the old immediate continuous integration >> workflow? Where new APIs (also from KF) are instantly available? > > With Flatpak new APIs were never instantly available - there has always been > a delay as the Flatpak Runtime uses the most recent released version of our > software. > >> >> Right now this is a new extra burden which makes working on new features with >> KF and apps more complicated. Thus less interesting, and one/I would rather >> duplicate code in apps to get things done. >> >> Blocking latest KF API from usage also means less testing of that before the >> initial release. >> >> Besides all the resource costs to create flatpaks on master builds by default >> every time, when those are usually not used by anyone anyway. > > Those applications that have a hard dependency on features being added to > Frameworks are not good candidates for making use of our Continuous Delivery > systems i'm afraid. > Both Flatpak and Craft based (Linux Appimages, Android APKs, Windows and > macOS) CD jobs are best optimised for those applications that rely on the > stable Frameworks releases. > > There are ways (in .craft.ini) to make newer Frameworks available, but that > requires that the system recompiles that Framework each time you trigger a > build and is therefore not recommended. > > Allowing those systems to use the "latest" artifacts of Frameworks would be a > non-trivial exercise. > >> >> So, how to solve those problems? Did I miss something? >> Could flatpak builds on master branches be made on-demand rather? >> >> Cheers >> Friedrich > > Cheers, > Ben
Re: Boost upgrade needed in craft
Hi, I just added boost 1.84.0 to Craft, but didn't set it as the default version yet. This should wait for a Craft cache rebuild (the next one will likely be in not too distant future ones Qt 6.6.2 is released). However this allows to try the new boost version for KDiff3 already via .craft.ini file. I will post more details about this in the MR. Cheers, Julius 28.01.2024 04:11:41 Michael Reeves : > Kdiff3 has run into a compilation bug in boost-hearders 1.80 on MacOS > > *std::unary_function* and *std::binary_function* are no longer available in > C++17 and C++20. They can be re-enabled by defining > *_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION*. They are also marked as > *[[deprecated]]* in C++11 and later. To disable deprecation warnings you have > to define *_LIBCPP_DISABLE_DEPRECATION_WARNINGS*. Note that this disables all > deprecation warnings. > > This issue is fixed upstream as of 1.84 and possibly earlier. Should I update > this library in cradt.
Re: Incubator + Review Process on https://develop.kde.org/docs/
This merge request is ready now, so last chance for a review. I suggest to merge this in 1 week if nobody raises major objections until then. Cheers, Julius Am 3. November 2023 um 12:57 schrieb "Plata" : > > Hi, > > I've opened a MR ( to include the Incubator and KDE Review processes on such > that new contributors can easily find them. > https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/308)https://develop.kde.org/docs/ > > It's basically moved from the wiki but has a few changes based on the review > comments so far. > > Please take a look to ensure that the described processes are correct. > > Rgds > > Plata >
Re: Craft Macos build failing on binary-factory.kde.org
Hi Michael, this is fixed this now. The issue was related to a cached version of QtMultimedia that linked to pulse audio while we disabled pulse audio for macOS recently. Sorry. Note that there is a matrix room for Craft related questions you may want to join https://go.kde.org/matrix/#/#kde-craft:kde.org Please do not just push random changes to Craft without a merge request or discussion if you are not 100% sure what you are doing. Thanks! Cheers, Julius 18.11.2023 20:56:41 Michael Reeves : > As of two days ago I am getting: > > Library dependency > '/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/extragear/kdiff3/archive/Applications/KDE/kdiff3.app/Contents/Frameworks/libpulse-mainloop-glib.0.dylib[http://kdiff3.app/Contents/Frameworks/libpulse-mainloop-glib.0.dylib]' > does not exist > > On the MacOS build for kdiff3.
Re: Fwd: KDE Craft Blueprints | Failed pipeline for master | 03023ae7
This broke due to the switch to python 3.12 which removed several deprecated functions Craft still used. It is fixed now. Cheers, Julius 06.10.2023 01:08:10 Michael Reeves : > Craft blueprints testing is failing for craft internal reasons. > > -- Forwarded message - > From: *KDE Invent* > Date: Thu, Oct 5, 2023 at 6:58 PM > Subject: KDE Craft Blueprints | Failed pipeline for master | 03023ae7 > To: > > > > [https://invent.kde.org/uploads/-/system/appearance/header_logo/1/kde-logo-white-blue-128x128.png] > > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-inverted-06e39ba2a7f9a32f6201e420175db85a4b6ac0348203fdc069001b440149.gif][✖][https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-inverted-06e39ba2a7f9a32f6201e420175db85a4b6ac0348203fdc069001b440149.gif]Pipeline > #493762 has failed! > > > Project Packaging [https://invent.kde.org/packaging]/ KDE Craft > Blueprints[https://invent.kde.org/packaging/craft-blueprints-kde] > > Branch > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-branch-gray-53618a7fc19d4d32ccbabac2f6d59bebe67202a9f2f1255e3f72c69756c0dd9c.gif]master[https://invent.kde.org/packaging/craft-blueprints-kde/-/commits/master] > > > Commit > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-commit-gray-c10243ac24cde64b549aec91de35e6b49c8739b506b86472b54614c10d8b4aac.gif]03023ae7[https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/03023ae74c1273ec06757d56732d39bf9a611c62] > [kdiff3] Fix blacklist syntax > > > Commit Author > [http:///assets/no_avatar-849f9c04a3a0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png]Michael > Reeves[https://invent.kde.org/mreeves] > > Pipeline > #493762[https://invent.kde.org/packaging/craft-blueprints-kde/-/pipelines/493762] > triggered by > [http:///assets/no_avatar-849f9c04a3a0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png]Michael > Reeves[https://invent.kde.org/mreeves] > had 1 failed job > > Failed job > > [https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-67056b7b99899e30453df79abfbe16162f6a26ed789d8236f81afcaea216ffe6.gif][✖][https://invent.kde.org/assets/mailers/ci_pipeline_notif_v1/icon-x-red-67056b7b99899e30453df79abfbe16162f6a26ed789d8236f81afcaea216ffe6.gif]test > > run-tests[https://invent.kde.org/packaging/craft-blueprints-kde/-/jobs/1234242] > > > > [https://invent.kde.org/assets/mailers/gitlab_logo_black_text-5430ca955baf2bbce6d3aa856a025da70ac5c9595597537254f665c10beab7a5.png][GitLab][https://invent.kde.org/assets/mailers/gitlab_logo_black_text-5430ca955baf2bbce6d3aa856a025da70ac5c9595597537254f665c10beab7a5.png] > You're receiving this email because of your account on > invent.kde.org[https://invent.kde.org]. Manage all > notifications[https://invent.kde.org/-/profile/notifications] · > Help[https://invent.kde.org/help] > > >
