Re: KDE Gear projects with failing CI (release/23.08) (17 October 2023)
I'm a bit confused as to why this was only added to the release/23.08 branch and not master as well. Also the licensing issue was not solved correctly, see the following patch: https://invent.kde.org/accessibility/kontrast/-/commit/17ece874e0f2fda3f8a6553ac7386b911faad405 In the future, please open a merge request. This is the sort of issues that can be easily caught up in code reviews ;) Cheers, Carl On Tue, Oct 17, 2023, at 11:07 PM, Scarlett Moore wrote: > Fixed! > Scarlett > > On Tue, Oct 17, 2023 at 1:54 PM Albert Astals Cid wrote: > > > > Please work on fixing them, otherwise i will remove the failing CI > > jobs on their 4th failing week, it is very important that CI is passing for > > multiple reasons. > > > > Good news: We're down to only 1 non passing repository. > > > > = FAILING UNIT TESTS = > > > > kontrast: (1st week) > > * https://invent.kde.org/accessibility/kontrast/-/pipelines/501951 > > * reuse check is failing > > > > >
Re: KDE Gear projects with failing CI (release/23.08) (17 October 2023)
Hi, Thanks for the clarity on the license. Snaps are not ready for qt6 at all, hence the release branch only. I wasn't doing MRs as I am the sole maintainer of snaps and I only have another day to get this transition done before my internet gets cut off. I wanted to get 23.08.2 release done before this happens. I will do MR as requested and hope for the best. Scarlett On Wed, Oct 18, 2023 at 12:31 AM Carl Schwan wrote: > > I'm a bit confused as to why this was only added to the release/23.08 branch > and not master as well. > > Also the licensing issue was not solved correctly, see the following patch: > https://invent.kde.org/accessibility/kontrast/-/commit/17ece874e0f2fda3f8a6553ac7386b911faad405 > > In the future, please open a merge request. This is the sort of issues that > can > be easily caught up in code reviews ;) > > Cheers, > Carl > > On Tue, Oct 17, 2023, at 11:07 PM, Scarlett Moore wrote: > > Fixed! > Scarlett > > On Tue, Oct 17, 2023 at 1:54 PM Albert Astals Cid wrote: > > > > Please work on fixing them, otherwise i will remove the failing CI > > jobs on their 4th failing week, it is very important that CI is passing for > > multiple reasons. > > > > Good news: We're down to only 1 non passing repository. > > > > = FAILING UNIT TESTS = > > > > kontrast: (1st week) > > * https://invent.kde.org/accessibility/kontrast/-/pipelines/501951 > > * reuse check is failing > > > > > >
Policy on merge-requests for developers. ( Specifically snapcraft transition )
Hello! As you have probably seen the noise, I have been busy transitioning snapcraft files to their respective repo. After I had already made it 3/4 of the way through I was asked to do MRs for this transition, which is no problem at all, I have already done so. However, I have only received one approval. I only touch snap related files and I now know to add license headers to said files.. If the tests pass, am I allowed to merge these myself? Or do I need to wait? This will make my releases for snaps difficult and prolonged.I guess not something I considered when proposing this. Thanks for any insight, Scarlett
Re: Policy on merge-requests for developers. ( Specifically snapcraft transition )
El dimecres, 18 d’octubre de 2023, a les 19:17:05 (CEST), Scarlett Moore va escriure: > Hello! > As you have probably seen the noise, I have been busy transitioning > snapcraft files to their respective repo. After I had already made it > 3/4 of the way through I was asked to do MRs for this transition, > which is no problem at all, I have already done so. However, I have > only received one approval. I only touch snap related files and I now > know to add license headers to said files.. If the tests pass, am I > allowed to merge these myself? Or do I need to wait? This will make my > releases for snaps difficult and prolonged.I guess not something I > considered when proposing this. I find that auto approving one own's MRs after a few days is ok if you're an expert in the field and noone has disagreed. Doing a MR makes sure you don't inadvertently break the build, we all think we're infallible but still mess it up from time to time. Cheers, Albert > Thanks for any insight, > Scarlett
[ANNOUNCE] CMake 3.28.0-rc2 is ready for testing
I am proud to announce the second CMake 3.28 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.28
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.28/release/3.28.html
Some of the more significant changes in CMake 3.28 are:
* C++ 20 named modules are now supported by Ninja Generators and
Visual Studio Generators for VS 2022 and newer, in combination with
the MSVC 14.34 toolset (provided with VS 17.4) and newer, LLVM/Clang
16.0 and newer, and GCC 14 (after the 2023-09-20 daily bump) and
newer. See "cmake-cxxmodules(7)" for details.
* "HIP" language code may now be compiled for NVIDIA GPUs using the
NVIDIA CUDA Compiler (NVCC). See the "CMAKE_HIP_PLATFORM" variable.
* On Apple platforms, ".xcframework" folders are now supported.
* The "exec_program()" command, which has been deprecated since CMake
3.0, has been removed by policy "CMP0153". Use the
"execute_process()" command instead.
* Generated files, in targets using File Sets, are now considered
private by default. Generated public headers must be specified
using file sets. This allows Ninja Generators to produce more
efficient build graphs. See policy "CMP0154".
* The "find_library()", "find_path()", and "find_file()" commands no
longer search in installation prefixes derived from the "PATH"
environment variable. This behavior was added in CMake 3.3 to
support MSYS and MinGW ("MSYSTEM") development environments on
Windows, but it can search undesired prefixes that happen to be in
the "PATH" for unrelated reasons. Users who keep some
"/bin" directories in the "PATH" just for their tools do not
necessarily want any corresponding "/lib" or
"/include" directories searched. The behavior was reverted
for non-Windows platforms by CMake 3.6. Now it has been reverted on
Windows platforms too.
CMake 3.28 Release Notes
Changes made since CMake 3.27 include the following.
New Features
Languages
-
* C++ 20 named modules are now supported by Ninja Generators and
Visual Studio Generators for VS 2022 and newer, in combination with
the MSVC 14.34 toolset (provided with VS 17.4) and newer, LLVM/Clang
16.0 and newer, and GCC 14 (after the 2023-09-20 daily bump) and
newer. See "cmake-cxxmodules(7)" for details.
* "HIP" language code may now be compiled for NVIDIA GPUs using the
NVIDIA CUDA Compiler (NVCC). See the "CMAKE_HIP_PLATFORM" variable.
Platforms
-
* On Apple platforms, ".xcframework" folders are now supported:
* The "find_library()" command now finds ".xcframework" folders.
* The "target_link_libraries()" command now supports linking against
a ".xcframework" folder.
* The "IMPORTED_LOCATION" target property of an imported library
target may now be the path to a ".xcframework" folder.
* Apple visionOS and its "xros" and "xrsimulator" SDKs are now
supported. Compiling for Apple visionOS can be requested by setting
"CMAKE_SYSTEM_NAME" to "visionOS". See Cross Compiling for iOS,
tvOS, visionOS, or watchOS for more information.
Presets
---
* "cmake-presets(7)" files now support schema version "8". It adds
support for a "$schema" field.
Compilers
-
* Cray Clang-based compilers are now supported with "compiler id"
"CrayClang".
* The OrangeC compiler is now supported with "compiler id" "OrangeC".
Commands
* The "add_custom_command()" and "add_custom_target()" commands gained
a "JOB_SERVER_AWARE" option.
* The "cmake_host_system_information()" command gained a
"MSYSTEM_PREFIX" query for the installation prefix of a MSYS or
MinGW development environment on Windows hosts.
* The "set_property()" command "TEST" mode gained a "DIRECTORY" option
to set properties on tests in other directories.
* The "set_tests_properties()" command gained a "DIRECTORY" option to
set properties on tests in other directories.
* The "get_property()" command "TEST" mode gained a "DIRECTORY" option
to get properties on tests in other directories.
* The "get_test_property()" command gained a "DIRECTORY" option to get
properties on tests in other directories.
Variables
-
* The "CMAKE_CROSSCOMPILING_EMULATOR" environment variable was added
to initialize the "CMAKE_CROSSCOMPILING_EMULATOR" cache variable.
* The "CMAKE_HIP_PLATFORM" variable was added to specify the GPU
platform for which HIP language sources are to be compiled ("amd" or
"nvidia").
Properties
--
* On imported shared libraries, the "IMPORTED_IMPLIB" target property
may now be used without "IMPORTED_LOCATION". This can be used to
represent a stub library whose location should not be added as a
runtime search path to dependents that link it.
* The "IMPORTED_LOCATION" property of a macOS framework may now be a
path to the ".framework" folder itself.
* The "XCODE_EMBED_RESOURCES" target property was ad
KDE Frameworks 5.111.0 released
19th October 2023. KDE today announces the release of KDE Frameworks 5.111.0. KDE Frameworks are 83 addon libraries to Qt which provide a wide variety of commonly needed functionality in mature, peer reviewed and well tested libraries with friendly licensing terms. For an introduction see https://kde.org/products/frameworks/ Baloo Use the FSID as the device identifier where possible (bug 471289) Extra CMake Modules ecm_add_tests/ecm_add_test: add argument WORKING_DIRECTORY KCoreAddons Unset bug address for implicitly created KAboutData (bug 473517) KDE GUI Addons mark geo-scheme-handler as non-gui executable on macOS/Windows KImageFormats avif: support repetition count raw: fix multi image load hdr: fix oss-fuzz issue 62197 hdr: fix crash (oss-fuzz) xcf: fix crash (oss-fuzz issue 62075) xcf: fix oss-fuzz issue KIO dbusactivationrunner: only activate well-formed services (bug 475266) DBusActivationRunner: fix object path according to spec Undeprecate KCoreDirLister::setMimeExcludeFilter Fix incomplete error strings in MimeTypeFinderJob Don't crash if KMountPoint gives nothing back while checking for CIFS (bug 474451) trashimpl: optimize TrashSizeCache::calculateSize (bug 461847) trash: Optimize trashimpl::adaptTrashSize [kfilewidget] Fixing saving to files with quotes (bug 426728) KPropertiesDialog: Force PlainText on size label Kirigami AboutPage: Allow overriding donateUrl by aliasing it from AboutItem (bug 474864) KRunner runnerpython: Fix install script paths to desktop files (bug 474866) KService KService: allow .desktop files without an Exec line (bug 430157) KWidgetsAddons Remove "No date" option from date picker popup used by date combo box Set the modes on the date picker Fix file rating being unreadable in certain themes (bug 339863) KWindowSystem Explain in deprecation message that logical coordinates must be used in KF6 Syntax Highlighting Set mode for more config file endings (bug 475078) Highlight MapCSS numeric and string condition values textproto syntax: Support multipart strings textproto syntax: Add test case for octal escape sequences textproto syntax: Support some types of comments textproto syntax: Allow empty strings textproto syntax: Allow commas between fields Add TextProto syntax (protocol buffer Text Format Language) Security information The released code has been GPG-signed using the following key: pub rsa2048/58D0EE648A48B3BB 2016-09-05 David Faure Primary key fingerprint: 53E6 B47B 45CE A3E0 D5B7 4577 58D0 EE64 8A48 B3BB https://kde.org/announcements/frameworks/5/5.111.0 -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 signature.asc Description: This is a digitally signed message part.
KDE+Qt6 releases schedule
The calendar for the next KDE Frameworks, KDE Plasma and KDE Gear has been agreed in the release team. https://community.kde.org/Schedules/February_2024_MegaRelease Alpha is less than 3 weeks away 😲 8 November 2023: Alpha KDE Gear 24.01.75 / KDE Plasma 5.80.0 / KDE Frameworks 5.245.0 29 November 2023: Beta 1 KDE Gear 24.01.80 / KDE Plasma 5.90.0 / KDE Frameworks 5.246.0 20 December 2023: Beta 2 KDE Gear 24.01.85 / KDE Plasma 5.91.0 / KDE Frameworks 5.247.0 10 January 2024: Release Candidate 1 KDE Gear 24.01.90 / KDE Plasma 5.92.0 / KDE Frameworks 5.248.0 For KDE Gear that want to ship with Qt6 for this release they need to be switched to Qt6 (and obviously stable) *BEFORE* this date. 31 January 2024: Release Candidate 2 KDE Gear 24.01.95 / KDE Plasma 5.93.0 / KDE Frameworks 5.249.0 21 February 2024: Private Tarball Release KDE Gear 24.02.0 / KDE Plasma 6.0 / KDE Frameworks 6.0 28 February 2024: Public Release KDE Gear 24.02.0 / KDE Plasma 6.0 / KDE Frameworks 6.0
