Re: KDE Gear projects with failing CI (master) (21 May 2024)

Am Dienstag, 21. Mai 2024, 23:23:53 MESZ schrieb Albert Astals Cid: > massif-visualizer - NEW > * https://invent.kde.org/sdk/massif-visualizer/-/pipelines/693832 > * appstreamtest fails because https://apps.kde.org/massif-visualizer > doesn't exist Meh. apps.kde.org code fails over the

D26484: Add KIO::DropJobFlag to allow manually showing the menu

kossebau added a comment. And now reported the challenge of drop objects lifetime vs user input on decisions by https://bugreports.qt.io/browse/QTBUG-125229 REPOSITORY R241 KIO REVISION DETAIL https://phabricator.kde.org/D26484 To: trmdi, #frameworks, davidedmundson, elvisangelaccio,

D26484: Add KIO::DropJobFlag to allow manually showing the menu

kossebau added a comment. Hi. I just came across dropping random data (in my case an image) into file views not working, i.e. not creating any new files due to no more data in the QMimeData instance referred to in the DropJob. Looking into the details, it seems this is due to the flaw

Re: KDE Gear projects with failing CI (master) (9 April 2024)

Am Mittwoch, 10. April 2024, 14:29:37 CEST schrieb Ingo Klöcker: > On Mittwoch, 10. April 2024 13:33:46 CEST Friedrich W. H. Kossebau wrote: > > Am Mittwoch, 10. April 2024, 13:04:47 CEST schrieb Ingo Klöcker: > > > On Mittwoch, 10. April 2024 09:21:34 CEST Ben Cooksley wrote: &

Re: KDE Gear projects with failing CI (master) (9 April 2024)

Am Mittwoch, 10. April 2024, 13:04:47 CEST schrieb Ingo Klöcker: > On Mittwoch, 10. April 2024 09:21:34 CEST Ben Cooksley wrote: > > On Wed, Apr 10, 2024 at 9:51 AM Ingo Klöcker wrote: > > > On Dienstag, 9. April 2024 23:26:32 CEST Albert Astals Cid wrote: > > > > ktrip - NEW > > > > > > > > *

D19557: Update design to look more similar to kde.org

kossebau added inline comments. INLINE COMMENTS > kde-docs.css:252 > +color: white; > +font-height: 3em; > +background: #54a3d8; Seems there is no such CSS property font-height? Was this meant to be e.g. font-size or line-height? REPOSITORY R238 KDocTools REVISION DETAIL

Re: flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

Am Donnerstag, 22. Februar 2024, 15:58:53 CET schrieb Friedrich W. H. Kossebau: > Am Dienstag, 30. Januar 2024, 18:34:46 CET schrieb Timothée Ravier: > > Hi folks, > > > > Flathub is now requiring that applications define a "developer_name" tag > &g

flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

Am Dienstag, 30. Januar 2024, 18:34:46 CET schrieb Timothée Ravier: > Hi folks, > > Flathub is now requiring that applications define a "developer_name" tag in > their metadata (see [1], [2]). > > What do folks think would be a good value for our application there? > > Based on the suggestion

Re: KDE Frameworks with failing CI (master) (19 February 2024)

Am Montag, 19. Februar 2024, 19:36:19 CET schrieb Albert Astals Cid: > 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: 1 repository has been fixed > > Bad news: 1

Re: KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

Am Samstag, 27. Januar 2024, 18:22:35 CET schrieb Friedrich W. H. Kossebau: > moving slowly, but moving :) > > Would there be any objections to declare the kde(re)review phase to be > successfully completed now? See below for comments on the checklist. So 10 days passed and no actu

Re: Proposal for using gitlab for kdereview process

Long time ago, but perhaps there are still memories... Am Dienstag, 4. Juli 2023, 14:32:59 CET schrieb Jonathan Riddell: > I've gone ahead an updated the Sanity checklist Having come across the checklist items * Passing KDE neon build * App packages in Flatpak, Snap, AppImages and Windows etc

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Sonntag, 4. Februar 2024, 19:22:28 CET schrieb 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

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Montag, 5. Februar 2024, 00:15:00 CET schrieb Julius Künzel: > > 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 >

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Montag, 5. Februar 2024, 10:58:07 CET schrieb Ben Cooksley: > On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau > > wrote: > > So, how to solve those problems? Did I miss something? > > Could flatpak builds on master branches be made on-demand rather? > >

Re: KDE Gear projects with failing CI (release/24.02) (6 February 2024)

Am Mittwoch, 7. Februar 2024, 11:48:57 CET schrieb Ben Cooksley: > All of the Games Flatpak failures are caused by > https://invent.kde.org/games/libkdegames/-/commit/023d1a7b173f9d28453a0268e9 > 1ad1ccb47054b9 I intend to revert that commit in 24 hours unless a suitable > explaination can be

Re: KDE Frameworks with failing CI (kf5) (4 February 2024)

Am Sonntag, 4. Februar 2024, 13:34:09 CET schrieb Albert Astals Cid: > ki18n - NEW > * https://invent.kde.org/frameworks/ki18n/-/pipelines/598250 > * Linux tests are failing Was found yesterday to be due to iso-codes 4.16 -> https://invent.kde.org/frameworks/ki18n/-/merge_requests/108

Re: KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

Am Montag, 29. Januar 2024, 17:11:57 CET schrieb Volker Krause: > On Samstag, 27. Januar 2024 18:22:35 CET Friedrich W. H. Kossebau wrote: > > There are only 2 open checkboxes: > > > > [ ] Passing CI job for Reuse linting > > > > The challenge is that ther

Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

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

Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

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

Re: What can we expect from our developers

Am Montag, 29. Januar 2024, 10:38:11 CET schrieb Sune Vuorela: > On 2024-01-29, Jonathan Riddell wrote: > > This sort of comment makes me really sad. The All About the Apps goal, > > which in principle is still ongoing, was an attempt to get KDE developers > > to realise it was important not

Re: KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

Hi, moving slowly, but moving :) Would there be any objections to declare the kde(re)review phase to be successfully completed now? See below for comments on the checklist. Am Sonntag, 12. November 2023, 22:57:55 CET schrieb Friedrich W. H. Kossebau: > Hi, > > REVIEW PHASE START &g

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

Am Freitag, 29. Dezember 2023, 16:36:41 CET schrieb Tommaso Massimi: > On Fri, Dec 29, 2023 at 3:35 PM Friedrich W. H. Kossebau > wrote: [snip} > > After a more close look I would partially disagree and point to another > > > possible cause: > correct, my analisys was

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

Hi, Am Freitag, 29. Dezember 2023, 10:53:45 CET schrieb Tommaso Massimi: > running plasma-systemmonitor with valgring a lot of problems are declared, > I'm trying to check them out. > > I'm not sure if this is the best way to communicate with the development > team, > so I'm writing this mail

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

Am Freitag, 29. Dezember 2023, 10:53:45 CET schrieb Tommaso Massimi: > running plasma-systemmonitor with valgring a lot of problems are declared, > I'm trying to check them out. > > I'm not sure if this is the best way to communicate with the development > team, > so I'm writing this mail also to

KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

Hi, REVIEW PHASE START please note the start of a kdereview phase for Skladnik. The checklist issue has been created here: https://invent.kde.org/games/skladnik/-/issues/2 RELEASE PLANNED FOR NOV 20th While the phase is running, in parallel I plan to do a first (well, after 15 years of

Move krunner also to plasma bundle? (was: Re: plasma-framework, kactivities and kactivities-stats: please consider proper de-KF-ication now)

Am Sonntag, 5. November 2023, 15:32:21 CET schrieb christ...@cullmann.io: > On 2023-11-05 15:11, Nate Graham wrote: > > On 11/5/23 07:09, christ...@cullmann.io wrote: > >> if we are atm moving stuff, might it make sense to move Baloo, too, > >> given it only > >> is usable with the daemon inside

plasma-framework, kactivities and kactivities-stats: please consider proper de-KF-ication now

Hi, with plasma-framework, kactivities and kactivities entering the Plasma product bundle, I assume they also will adapt to Plasma versioning. Without any de-KF-ication though this will break things though for building consumers soonish. Example --- 8< --- find_package(KF6 ${KF_MIN_VERSION}

Re: Breeze and ECM are incompatible for installing icons

Am Donnerstag, 2. November 2023, 14:51:48 CET schrieb Harald Sitter: > https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-lates > t.html > > Each directory contains icons designed for a certain nominal icon size and > > scale, as described by the index.theme file > ... > > >

Re: libkexiv2, libkdcraw (Re: Collection of packaging notes)

Am Mittwoch, 1. November 2023, 13:25:42 CET schrieb Friedrich W. H. Kossebau: > Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > > - Non frameworks modules installing libKF*.so > > libkexiv2 (libKF6KExiv2.so) > > Any code ideas for naming it, given ther

Re: Collection of packaging notes

Am Mittwoch, 1. November 2023, 13:30:03 CET schrieb Jonathan Riddell: > One quick question, is naming non-frameworks libKF6foo really a problem we > need to fix? Given all the other issues... What is in a name... usually some semantics. We could also call random libraries libdsafwef or

libkexiv2, libkdcraw (Re: Collection of packaging notes)

Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin: > With various alpha coming out soon, here are the notes added to my packages > when I started packaging snapshots and still present. Thanks for the report. Everyone: Could we perhaps establish some wiki page where such

KDE Gear "6.0" status update: all 40 games & 2 libs now Qt6-only in master

Hi, just a quick heads-up to keep more people in the loop: all the 40 game apps & 2 game libs covered by KDE Gear starting today are now Qt6-only in their master branches. And thus can/will be released based on Qt6/ KF6 in the KDE Gear "6.0" 24.02 release. So the section "Games" can be checked

Re: RFC: switching games released with KDE Gear to Qt6/KF6-only in master branch next?

Am Mittwoch, 13. September 2023, 22:34:16 CEST schrieb Friedrich W. H. Kossebau: > (cc: kde-devel for heads-up, please reply only to kde-games-devel) > > QUESTION > > Would anyone have issues with switching all the games and game libraries > released with KDE Gear

RFC: switching games released with KDE Gear to Qt6/KF6-only in master branch next?

Hi, (cc: kde-devel for heads-up, please reply only to kde-games-devel) QUESTION Would anyone have issues with switching all the games and game libraries released with KDE Gear to be Qt6/KF6 only in the master branch (once some conditions are met, see below)? MOTIVATION Having brushed over

PSA: Qt6-based KDE software builds: drop EXCLUDE_DEPRECATED_BEFORE_AND_AT override now

Hi, a quick heads-up: if you already package or otherwise do any Qt6-based KDE software builds and have in the set of manual flags passed to cmake any "-DEXCLUDE_DEPRECATED_BEFORE_AND_AT=x.y.z" override, please remove that override completely now. All KDE sources should now set the proper

PSA: Qt6-based KDE software builds: drop EXCLUDE_DEPRECATED_BEFORE_AND_AT override now

Hi, a quick heads-up: if you already package or otherwise do any Qt6-based KDE software builds and have in the set of manual flags passed to cmake any "-DEXCLUDE_DEPRECATED_BEFORE_AND_AT=x.y.z" override, please remove that override completely now. All KDE sources should now set the proper

Re: Tellico failing CI with exiv2 error

Am Donnerstag, 6. Juli 2023, 18:43:50 CEST schrieb Kai Uwe Broulik: > > Probably libexiv2 on the CI host was updated to libexiv2 0.28, but > > KFileMetaData was not rebuilt. Automatic dependency tracking for > > artifacts > > > from the CI system is obviously incomplete (or likely

Re: KSvg in kdereview

Am Mittwoch, 21. Juni 2023, 12:23:55 CEST schrieb Ben Cooksley: > On Wed, Jun 21, 2023 at 10:12 PM Harald Sitter wrote: > > LGTM now +2 > > > > On Wed, Jun 21, 2023 at 10:04 AM Marco Martin wrote: > > > I fixed CI, passes now > > Thanks for correcting that. > > As Friedrich raised the initial

Re: KSvg in kdereview

Hi, Am Donnerstag, 20. April 2023, 10:25:34 CEST schrieb Marco Martin: > Hi all, > A part of plasma-framewrok, which is the one to do SVG-based themes, > has now been splitted in a standalone library which is intended to be > a new framework in KF6 (all usages of the plasma-framework version >

Re: Usage of KF5/KF6 in targets and CMake config files outside of Frameworks

Am Freitag, 10. März 2023, 05:24:40 CET schrieb Kevin Kofler: > Heiko Becker wrote: > > while looking at a MR for libkcddb (part of Gear) I wondered if the > > transition from Qt5/KF5 to Qt6/KF6 could be used to get rid of the KF5/6 > > prefix in target names and CMake config files for libraries

Re: Usage of KF5/KF6 in targets and CMake config files outside of Frameworks

Am Donnerstag, 9. März 2023, 18:03:17 CET schrieb Ingo Klöcker: > On Donnerstag, 9. März 2023 16:58:40 CET Heiko Becker wrote: > > while looking at a MR for libkcddb (part of Gear) I wondered if the > > transition > > from Qt5/KF5 to Qt6/KF6 could be used to get rid of the KF5/6 prefix in > >

Re: Usage of KF5/KF6 in targets and CMake config files outside of Frameworks

Am Donnerstag, 9. März 2023, 18:03:17 CET schrieb Ingo Klöcker: > On Donnerstag, 9. März 2023 16:58:40 CET Heiko Becker wrote: > > while looking at a MR for libkcddb (part of Gear) I wondered if the > > transition > > from Qt5/KF5 to Qt6/KF6 could be used to get rid of the KF5/6 prefix in > >

Re: RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

(cc:kde-core-devel only for heads-up, any reply please only to kde-devel) Am Dienstag, 28. Februar 2023, 15:20:11 CET schrieb Friedrich W. H. Kossebau: > TL;DR Would you fancy not having to always explicitly include a version > header of a KFoo module to have the KFOO_VERSION variable ava

Re: RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

(cc:kde-core-devel only for heads-up, any reply please only to kde-devel) Am Dienstag, 28. Februar 2023, 15:20:11 CET schrieb Friedrich W. H. Kossebau: > TL;DR Would you fancy not having to always explicitly include a version > header of a KFoo module to have the KFOO_VERSION variable ava

Re: RFC: an improved ki18n_install

Am Dienstag, 7. März 2023, 02:51:06 CET schrieb Aleix Pol: > Having ninja/make do this dependency generation can end up being more > work than worth it because then we need to have a static list Such static list could be generated by scripty when it updates the po/ folder and stored there, no?

RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

Hi, (cc:kde-core-devel only for heads-up, any reply please only to kde-devel) TL;DR Would you fancy not having to always explicitly include a version header of a KFoo module to have the KFOO_VERSION variable available in your code? So is it worth it to add support for that on the KF side?

RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

Hi, (cc:kde-core-devel only for heads-up, any reply please only to kde-devel) TL;DR Would you fancy not having to always explicitly include a version header of a KFoo module to have the KFOO_VERSION variable available in your code? So is it worth it to add support for that on the KF side?

Helper for porting from deprecated KMessageBox Yes/No API

Hi, while as "culprit" for those API changes (HIG-matching rename of *YesNo* methods) I have seen to do the needed porting in some repos, there are more which need someone else to do that sadly. Especially for those projects with many calls perhaps the approach we now developed for KDevelop

Re: "Configure Language" option

Am Dienstag, 25. Oktober 2022, 17:16:15 CEST schrieb Friedrich W. H. Kossebau: > Am Montag, 24. Oktober 2022, 23:38:15 CEST schrieb Stefan Gerlach: > > i noticed that several KDE apps lack the ability to switch the UI language > > when using the "Configure Language&qu

Re: "Configure Language" option

Am Montag, 24. Oktober 2022, 23:38:15 CEST schrieb Stefan Gerlach: > i noticed that several KDE apps lack the ability to switch the UI language > when using the "Configure Language" dialog. The .mo files are correctly > installed, all the languages are in the selection box and the configuration >

Re: Cleaning up cdash.org integration, what to do, or any hidden usage still?

Hi Alex, thanks for the quick reply. :) Am Sonntag, 4. September 2022, 23:42:36 CEST schrieb Alexander Neundorf: > On Freitag, 2. September 2022 12:20:50 CEST Friedrich W. H. Kossebau wrote: > > we stumbled over some CTestConfig.cmake files in some of the KDE git > > repositor

Cleaning up cdash.org integration, what to do, or any hidden usage still?

Hi, (cc: kde-devel for heads-up, please reply only to kde-core-devel). we stumbled over some CTestConfig.cmake files in some of the KDE git repositories. Which seem to originate from a time where people worked on integration with cdash.org, that is a decade ago :) It seems though this

Cleaning up cdash.org integration, what to do, or any hidden usage still?

Hi, (cc: kde-devel for heads-up, please reply only to kde-core-devel). we stumbled over some CTestConfig.cmake files in some of the KDE git repositories. Which seem to originate from a time where people worked on integration with cdash.org, that is a decade ago :) It seems though this

Re: Challenge: adding new method overloads when existing consumers use {} with args

Am Donnerstag, 28. Juli 2022, 14:38:38 CEST schrieb Friedrich W. H. Kossebau: > Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira: > > But {} is particularly special, so I don't know how we'd deal with it. I > > don't think this has come up for us yet. For one, t

Re: Challenge: adding new method overloads when existing consumers use {} with args

Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira: > [cross-posting to Qt dev ML - dunno if it'll arrive because I'm subscribed > with different addresses] > > On Wednesday, 27 July 2022 14:54:55 PDT Friedrich W. H. Kossebau wrote: > > And has n

Re: Challenge: adding new method overloads when existing consumers use {} with args

Am Mittwoch, 27. Juli 2022, 13:51:48 CEST schrieb Friedrich W. H. Kossebau: > Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra: > > You could try using SFINAE: > > > > ``` > > struct Test { > > > > void foo() { } &g

Re: Challenge: adding new method overloads when existing consumers use {} with args

(David, somehow your emails do not make it from the mailinglist to my inbox sadly, no idea yet why. Saw your email by chance on the list web interface, and tosky forwarded it manually to me, so I can reply now here. So might miss out more :() Am Samstag, 23. Juli 2022, 20:26:47 CEST schrieb

Re: Challenge: adding new method overloads when existing consumers use {} with args

Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra: > On Monday, 25 July 2022 14:22:45 CEST Friedrich W. H. Kossebau wrote: > > Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo: > > > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W.

Re: Challenge: adding new method overloads when existing consumers use {} with args

Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo: > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau: > Adding such an overload as in your example is source incompatible > regardless. See also our guidelines. > https://community.kde.

Challenge: adding new method overloads when existing consumers use {} with args

Hi, (cc: kde-frameworks-devel for heads-up, please reply to kde-devel only) given a class C with a method foo(A a): --- 8< --- class C { public: void foo(A a); }; --- 8< --- Now you want to add an overload, to serve further use-cases as requested by API consumers: ---

Challenge: adding new method overloads when existing consumers use {} with args

Hi, (cc: kde-frameworks-devel for heads-up, please reply to kde-devel only) given a class C with a method foo(A a): --- 8< --- class C { public: void foo(A a); }; --- 8< --- Now you want to add an overload, to serve further use-cases as requested by API consumers: ---

Re: On ECMDeprecationSettings

Am Dienstag, 28. Juni 2022, 13:12:33 CEST schrieb Aleix Pol: > I wonder if it would make sense to have the ECMDeprecationSettings > calls in KDEFrameworkCompilerSettings rather than in each separate > framework in a copy-paste manner. The calls are more-pr-less replacing the current direct

MRs for dropping dead(?) Python bindings generation, scheduled for Feb 26/27

Hi, so no-one has been found so far who is building or even using the Python bindings for KF modules (see also query on distributions ML*), and those with insight consider it not easily unrecoverable by what I understood. * https://mail.kde.org/pipermail/distributions/2022-February/001148.html

Reminder: When requiring ECM 5.85 or newer, be aware of KDE_COMPILERSETTINGS_LEVEL concept

Hi, ((kde-core-devel as CC:, please reply only to kde-devel) Time for a quick reminder after half a year, given this is not daily business but people might more & more require newer ECM and run into this. Quoting the important bit below, for the full initial email, please see

Reminder: When requiring ECM 5.85 or newer, be aware of KDE_COMPILERSETTINGS_LEVEL concept

Hi, ((kde-core-devel as CC:, please reply only to kde-devel) Time for a quick reminder after half a year, given this is not daily business but people might more & more require newer ECM and run into this. Quoting the important bit below, for the full initial email, please see

Reminder about KDE_COMPILERSETTINGS_LEVEL (was: Re: Requiring ECM 5.85 makes apps stop compiling)

Am Montag, 14. Februar 2022, 16:32:57 CET schrieb Albert Astals Cid: > It introduces code breaking defines, some of them even of questionable > benefit for an application like QT_NO_KEYWORDS > > I don't understand how such a breaking commit was accepted. > > Who is going to fix all the

D7274: Allow to only build the kauth-policy-gen code generator

kossebau added inline comments. Herald added a subscriber: kde-frameworks-devel. INLINE COMMENTS > CMakeLists.txt:91 > > -install(EXPORT KF5AuthTargets DESTINATION "${CMAKECONFIG_INSTALL_DIR}" > +if(TARGET KF5Auth) > +install(EXPORT KF5AuthTargets DESTINATION "${CMAKECONFIG_INSTALL_DIR}"

Dropping dead(?) Python bindings generation code?

Hi, trying to ensure some changes do not break the Python binding generation, I actually tried to activate that, but found at least on current openSUSE TW there seem to be no longer any working dependencies. Also the openSUSE TW packages of the KF modules seem to also be build without

KF 5.91: 24 modules with failing unit tests (Re: Please fix failing unit tests with Windows platform)

Am Montag, 24. Januar 2022, 01:06:40 CET schrieb Friedrich W. H. Kossebau: > Hi, > > since a long time there are lots of failing unit tests across multiple > repositories. Could the Windows platform maintainers/stakeholders please > look soonish into either fixing those tests or p

Re: Please fix failing unit tests with Windows platform

Am Montag, 24. Januar 2022, 01:22:05 CET schrieb Albert Astals Cid: > Are you going to propose the same for Linux and FreeBSD where we also have > long running tests that don't succeed and no one bothers to fix them? Yes, if a test is known to fail, and no solution is known, it should be tagged

Please fix failing unit tests with Windows platform

Hi, since a long time there are lots of failing unit tests across multiple repositories. Could the Windows platform maintainers/stakeholders please look soonish into either fixing those tests or properly marking them as expected to fail, so the resources the KDE CI spends on running the tests

Maintainers of KDE Frameworks for the Windows platform?

Hi, in the past it was hard to find someone to fix things for KDE Frameworks on Windows, and too often people not interested in Windows had instead to spend their costly leisure time to solve problems, e.g. by debugging via CI runs. I do not think we can expect from every contributor/patch

Gitlab CI: failed unit tests vs. currently passing CI

Hi, seems that Gitlab CI is currently configured to show the green "Success" checkmark for pipeline runs even if unit tests are failing. Reasons seems to be that there Gitlab only knows Yay or Nay, without the warning state level known from Jenkins. And given that quite some projects (sadly)

Re: Developer setups for user D-Bus service files?

Am Mittwoch, 12. Januar 2022, 11:49:26 CET schrieb David Edmundson: > > This triggered yet another idea with me, and I came across > > https://www.freedesktop.org/software/systemd/man/environment.d.html > > upon which I tried to add a file > > /home/mydevuser/.config/environment.d/60-test.conf > >

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > I did start another idea. > > If you populate the dev session environment variables *really* early > must we even go through pam you can set your XDG_DATA_DIRS before DBus > daemon has loaded it will then have the right stuff.

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > >at least with systemd controlled start (but possibly also before > > Since forever. Okay, guessed so, as I had found decade old queries trying to solve similar challenges, though systemd also is that age, thus was not that

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 19:38:09 CET schrieb Friedrich W. H. Kossebau: > YOUR INPUT NEEDED > So, what standard approach should we take as developers here? Ideally we all > do something similar, so any issues hit are more easy to > understand/reproduce when we discuss them.

Developer setups for user D-Bus service files?

Hi, (plasma-devel as CC: for heads-up, please reply only to kde-devel to keep discussion in one place) at least with systemd controlled start (but possibly also before) of the session D-Bus (based on what I understood so far, please correct me) for a user is not possible just by editing their

Re: SPDX and docbook documentation, how to do properly?

Am Mittwoch, 5. Januar 2022, 15:21:24 CET schrieb Luigi Toscano: > Harald Sitter ha scritto: > > On Wed, Jan 5, 2022 at 1:45 PM Friedrich W. H. Kossebau > > > > wrote: > >> Hi, > >> > >> the section "License Statements in Non-Source-Co

SPDX and docbook documentation, how to do properly?

Hi, the section "License Statements in Non-Source-Code Files" at https://community.kde.org/Guidelines_and_HOWTOs/ Licensing#License_Statements_in_Non-Source-Code_Files currently does not hold an example how to add SPDX tags. And by a quick look it seems not many docbook files in KDE repos

Includes (was: Re: KF6 meeting notes 2022-01-04)

Am Dienstag, 4. Januar 2022, 18:07:45 CET schrieb Volker Krause: > - in some places includes with the framework prefix don't seem to work > anymore (ie. vs ), any idea where those extra > include directories came from/got lost? FTR, pointed on irc to some insights about design of include folder

Re: Merge stable to master vs cherry-picking

Am Donnerstag, 9. Dezember 2021, 11:08:01 CET schrieb Ben Cooksley: > On Wed, Dec 8, 2021 at 10:38 PM Friedrich W. H. Kossebau > > wrote: > > Am Mittwoch, 8. Dezember 2021, 07:44:32 CET schrieb Ben Cooksley: > > > This is why I have been pushing for people to use @st

Re: Merge stable to master vs cherry-picking

Am Mittwoch, 8. Dezember 2021, 07:44:32 CET schrieb Ben Cooksley: > This is why I have been pushing for people to use @stable in their > .kde-ci.yml files - even for the 'master' branch. > It is much simpler for people if you can use stable/released dependencies > when conducting development.

D7700: Show list of tags in PlacesView

kossebau added inline comments. INLINE COMMENTS > kfileplacesitem.cpp:351 > +{ > +KBookmark bookmark = createSystemBookmark(manager, tag, tag, > QUrl(QStringLiteral("tags:/") + tag), QStringLiteral("tag")); > +bookmark.setMetaDataItem(QStringLiteral("tag"), tag); @nicolasfella Hi. this

Re: Fwd: KDE CI: Administration » Dependency Build Applications kf5-qt5 FreeBSDQt5.15 - Build # 127 - Still Failing!

Am Donnerstag, 18. November 2021, 18:37:37 CET schrieb Volker Krause: > I looked into this and it seems the problem had already been addressed prior > to your email, so all I ended up doing is pressing the rebuild button. > > > The change starting this was

Re: How do you label code to be deleted in KF6?

Am Dienstag, 9. November 2021, 03:33:44 CET schrieb Glen Ditchfield: > I would like to have some members of KCalendarCore's incidence classes > removed during the transition from KF5 to KF6, and I'd like to be sure > that the changes won't be missed in the excitement. > > Do you have some

Making Grantlee a KF5 Framework, take 2

Hi (especially those who would be in contact with Stephen, see end). OLD PLANS REVISITED The old plan was to turn the two libraries part of Grantlee (main one being for text templating, second one for markup generation, see grantlee.org) into KF modules in time for KF6. With KF6 still some

Making Grantlee a KF5 Framework, take 2

Hi (especially those who would be in contact with Stephen, see end). OLD PLANS REVISITED The old plan was to turn the two libraries part of Grantlee (main one being for text templating, second one for markup generation, see grantlee.org) into KF modules in time for KF6. With KF6 still some

D19565: kconfig_compiler: new kcfgc args HeaderExtension & SourceExtension

kossebau added a comment. In D19565#678804 , @alex wrote: > However the option seems pretty unused, even from a github search: https://github.com/search?q=HeaderExtension%3D+extension%3Akcfgc=Code=advsearch== In comparison to how many

D19565: kconfig_compiler: new kcfgc args HeaderExtension & SourceExtension

kossebau added a comment. In D19565#678799 , @alex wrote: > I am wondering if there is really a need for it. SourceExtension seems completely unused and HeaderExtension is only used in okteta. > > Though in KDE code, Qt code (and most other

Re: KApiDox move from dedicated server to Jenkins

Am Freitag, 10. September 2021, 19:23:47 CEST schrieb Frederik Schwarzer: > Hi, > > we have been working on getting KApiDox to run on Jenkins. This work has > been taken way longer than I expected but has now reached a state close > to finished. :) Congrats on moving forwards, thanks for the

Re: KF API Documentation proposed, small, addition

Am Donnerstag, 9. September 2021, 23:23:29 CEST schrieb Ahmad Samir: > On 09/09/2021 22:47, Friedrich W. H. Kossebau wrote: > > Am Donnerstag, 9. September 2021, 22:35:05 CEST schrieb Ahmad Samir: > >> On 09/09/2021 22:24, Friedrich W. H. Kossebau wrote: > >>> Am Don

Re: KF API Documentation proposed, small, addition

Am Donnerstag, 9. September 2021, 22:35:05 CEST schrieb Ahmad Samir: > On 09/09/2021 22:24, Friedrich W. H. Kossebau wrote: > > Am Donnerstag, 9. September 2021, 21:45:33 CEST schrieb Ahmad Samir: > >> On 30/08/2021 16:35, Friedrich W. H. Kossebau wrote: > >>>

Re: KF API Documentation proposed, small, addition

Am Donnerstag, 9. September 2021, 21:45:33 CEST schrieb Ahmad Samir: > On 30/08/2021 16:35, Friedrich W. H. Kossebau wrote: > > Thanks for pushing this here. > > > > Am Montag, 30. August 2021, 14:17:42 CEST schrieb Ahmad Samir: > > Open question: > > in whic

When to use "code"-style for code expressions in API docs? (was: Re: KF API Documentation proposed, small, addition)

Thanks for pushing this here. Am Montag, 30. August 2021, 14:17:42 CEST schrieb Ahmad Samir: > I would like to add the following to: > https://community.kde.org/Frameworks/Frameworks_Documentation_Policy#Documen > t_the_Classes > > > One can use [https://www.doxygen.nl/manual/commands.html

ECM 5.85: introducing KDE_COMPILERSETTINGS_LEVEL concept

Hi, ((kde-core-devel as CC:, please reply only to kde-devel) TL;DR Starting with ECM 5.85 KDECompilerSettings will provide some stricter settings, which you can control on the toplevel by KDE_COMPILERSETTINGS_LEVEL and then again per settings category, for a stable set of settings matching

ECM 5.85: introducing KDE_COMPILERSETTINGS_LEVEL concept

Hi, ((kde-core-devel as CC:, please reply only to kde-devel) TL;DR Starting with ECM 5.85 KDECompilerSettings will provide some stricter settings, which you can control on the toplevel by KDE_COMPILERSETTINGS_LEVEL and then again per settings category, for a stable set of settings matching

Re: Raising KF5 version a bit earlier

Am Samstag, 24. Juli 2021, 13:58:56 CEST schrieb Aleix Pol: > Hi, > Would it be possible to get the version bump in master a bit earlier in > this cycle? > https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/2a39f0b235c24 > 2592ae6658f33e7fc7b547f8c6d Please note that the bump of the

Re: Porting notes / deprecation docs

Am Dienstag, 13. Juli 2021, 18:46:35 CEST schrieb Frederik Schwarzer: > On 7/12/21 8:43 PM, Friedrich W. H. Kossebau wrote: > > IIRC main file of the generation is > > https://invent.kde.org/websites/quality-kde-org/-/blob/master/apidox/src/ > > gendox.sh > > > >

Re: Porting notes / deprecation docs

Am Montag, 12. Juli 2021, 20:22:30 CEST schrieb Frederik Schwarzer: > On 7/12/21 7:38 PM, Friedrich W. H. Kossebau wrote: > > Now what is meant by "clickable links to replacements" exactly? Any > > example > > for what you have in mind? > > (Just in case, Dox

  1   2   3   4   5   6   7   8   9   10   >