Re: KDE Gear projects with failing CI (master) (6 August 2024)

2024-08-07 Thread Thomas Friedrichsmeier
On Wed, 07 Aug 2024 00:55:00 +0200 Albert Astals Cid wrote: > okular - 3rd week > * https://invent.kde.org/graphics/okular/-/pipelines/748502 > * mac craft packaging fails I do not have a proper diagnosis as to why this is failing. However, the failing lib (libgpg-error) gets pulled in via KF6

Re: Migrating Windows CI to Qt 6.7 - Roadblocks

2024-05-26 Thread Thomas Friedrichsmeier
On Sat, 25 May 2024 13:02:41 +0200 christ...@cullmann.io wrote: > Now that frameworks is QDBus free on Windows and macOS I would even > propose that in a next update of the stuff we really not have QtDBus > around at all on these systems and make the use optional for the apps > that want to supp

Re: Automated usage of Gitlab

2022-07-04 Thread Thomas Friedrichsmeier
On Sun, 3 Jul 2022 22:45:37 +1200 Ben Cooksley wrote: > Recent analysis of the logs of our Giltab instance has revealed > numerous instances of files being directly retrieved from Gitlab > (using the /raw/ API). Much to my incredible sadness, this has > included accesses being made by KDE Applicat

Re: Debugging CI test failures

2022-06-25 Thread Thomas Friedrichsmeier
On Sat, 25 Jun 2022 08:55:16 +1200 Ben Cooksley wrote: > The image change has been rolled out, which should have fixed things. > Guess there are more things missing we need to track down. Works perfectly (for RKWard), now! Thanks! Thomas pgpFmPaaKbOGd.pgp Description: OpenPGP digital signature

Re: Debugging CI test failures

2022-06-24 Thread Thomas Friedrichsmeier
On Fri, 24 Jun 2022 16:22:08 +1200 Ben Cooksley wrote: > On Thu, Jun 23, 2022 at 8:36 PM Ben Cooksley > wrote: > > > On Wed, Jun 22, 2022 at 11:41 PM Thomas Friedrichsmeier < > > thomas.friedrichsme...@kdemail.net> wrote: > > > >> On Wed, 22

Re: Debugging CI test failures

2022-06-22 Thread Thomas Friedrichsmeier
On Wed, 22 Jun 2022 22:49:42 +1200 Ben Cooksley wrote: > On Mon, Jun 20, 2022 at 9:12 AM Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> wrote: > > > On Sun, 19 Jun 2022 22:43:54 +1200 > > Ben Cooksley wrote: > > [...] > > > We there

Re: Debugging CI test failures

2022-06-19 Thread Thomas Friedrichsmeier
On Sun, 19 Jun 2022 22:43:54 +1200 Ben Cooksley wrote: [...] > We therefore have no choice but to address this as annoying as it is. > > Would you like to start this process off with a MR to > https://invent.kde.org/sysadmin/ci-images/-/blob/master/windows-msvc2019/Dockerfile > ? Can do, but I w

Re: Debugging CI test failures

2022-06-19 Thread Thomas Friedrichsmeier
On Sun, 19 Jun 2022 00:44:08 +1200 Ben Cooksley wrote: [...] > Looks like DirectX and it's corresponding components are missing: > > PS C:\> Get-ChildItem -Path C:\ -Recurse -ErrorAction SilentlyContinue > -Force -Filter ddraw.dll > PS C:\> Get-ChildItem -Path C:\ -Recurse -ErrorAction Silently

Re: Debugging CI test failures

2022-06-18 Thread Thomas Friedrichsmeier
On Sat, 18 Jun 2022 21:50:33 +1200 Ben Cooksley wrote: > On Fri, Jun 17, 2022 at 8:04 AM Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> wrote: > > > On Thu, 16 Jun 2022 17:31:16 +0200 > > Thomas Friedrichsmeier wrote: > > > > > On

Re: Debugging CI test failures

2022-06-16 Thread Thomas Friedrichsmeier
On Thu, 16 Jun 2022 17:31:16 +0200 Thomas Friedrichsmeier wrote: > On Thu, 16 Jun 2022 22:26:31 +1200 > Ben Cooksley wrote: > > > On Thu, Jun 16, 2022 at 8:08 AM Thomas Friedrichsmeier < > > thomas.friedrichsme...@kdemail.net> wrote: > > > &g

Re: Debugging CI test failures

2022-06-16 Thread Thomas Friedrichsmeier
On Thu, 16 Jun 2022 22:26:31 +1200 Ben Cooksley wrote: > On Thu, Jun 16, 2022 at 8:08 AM Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> wrote: > > > On Wed, 15 Jun 2022 17:51:52 +0200 > > Thomas Friedrichsmeier wrote: > > [...] > >

Re: Debugging CI test failures

2022-06-15 Thread Thomas Friedrichsmeier
On Wed, 15 Jun 2022 17:51:52 +0200 Thomas Friedrichsmeier wrote: [...] > I suppose, I could try seting up some dummy test binaries, linking > against the various libraries, hoping to narrow down the problem that > way? Ok, that finally led to something. I have no idea, why this is happ

Re: Debugging CI test failures

2022-06-15 Thread Thomas Friedrichsmeier
On Tue, 14 Jun 2022 23:16:04 +1200 Ben Cooksley wrote: > On Mon, Jun 13, 2022 at 7:56 AM Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> wrote: > > > On Sun, 12 Jun 2022 20:48:59 +1200 > > Ben Cooksley wrote: > > > > > On Sun, Jun

Re: Debugging CI test failures

2022-06-12 Thread Thomas Friedrichsmeier
On Sun, 12 Jun 2022 20:48:59 +1200 Ben Cooksley wrote: > On Sun, Jun 12, 2022 at 6:13 PM Thomas Friedrichsmeier < > thomas.friedrichsme...@kdemail.net> wrote: [...] > > https://invent.kde.org/education/rkward/-/jobs/354885 > > > > Test project C:/builds/education

Debugging CI test failures

2022-06-11 Thread Thomas Friedrichsmeier
Hi! Would anybody have a hint for me on how to diagnose an issue in running tests on the gitlab (Windows) CI? My newly added test fails with an exception: https://invent.kde.org/education/rkward/-/jobs/354885 Test project C:/builds/education/rkward/_build Start 1: rkward-core_test 1/1 Test #

Re: New cmake warning.

2022-05-03 Thread Thomas Friedrichsmeier
On Tue, 3 May 2022 10:35:20 +0200 Méven wrote: > I am guessing you are using cmake >= 3.16 so it allows you to run, but > since the project does not have a cmake minimum, for others using > cmake < 3.16 the build will break. > This warning highlights it, so you inform your contributor they need >

Re: How do you deal with incomplete commits?

2020-11-02 Thread Thomas Friedrichsmeier
Am Mon, 02 Nov 2020 17:51:29 + schrieb David Jarvie : > On Monday 02 Nov 2020 18:39:52 Thomas Friedrichsmeier wrote: > > I ended up writing a local pre-commit hook, which has the advantage > > of triggering on the commit directly after "the problem commit", > >

Re: How do you deal with incomplete commits?

2020-11-02 Thread Thomas Friedrichsmeier
Am Sun, 01 Nov 2020 09:52:27 -0800 schrieb Thiago Macieira : > On Saturday, 31 October 2020 08:25:40 PST Thomas Friedrichsmeier > wrote: > > thanks for your answer (also to Nate). But to clarify, my question > > is really: How do I _force_ myself to clean up in time? > >

Re: How do you deal with incomplete commits?

2020-10-31 Thread Thomas Friedrichsmeier
Am Sat, 31 Oct 2020 17:09:22 +0100 schrieb David Hurka : > Maybe you could write your own commit hook, which prevents commiting > anything when `git log --oneline` matches, say /\A INCOMPLETE/x. Hm, true, it doesn't have to be a server-side hook. Thanks for pointing me in the right direction. Tho

Re: How do you deal with incomplete commits?

2020-10-31 Thread Thomas Friedrichsmeier
Hi, Am Sat, 31 Oct 2020 16:38:09 +0100 schrieb Thomas Baumgart : > Reading your question over and over, I don't see where git is > mentioned :) This leads to a short answer: self-discipline. > > My impression is that you look for a some magic feature in git that > forces you to clean up in time.

Re: How do you deal with incomplete commits?

2020-10-31 Thread Thomas Friedrichsmeier
Hi, thanks for your answer (also to Nate). But to clarify, my question is really: How do I _force_ myself to clean up in time? Am Sat, 31 Oct 2020 15:44:35 +0100 schrieb Thomas Baumgart : > On Samstag, 31. Oktober 2020 13:39:04 CET Thomas Friedrichsmeier > wrote: [...] > > Say I&

How do you deal with incomplete commits?

2020-10-31 Thread Thomas Friedrichsmeier
Hi all, may I pick your brains for this question that keeps coming up for me? Say I'm working on a feature in branch A. I have some changes in my working copy that are so half-baked that I don't want them to end up in the commit history as such, but I don't want to throw them away, either. Now I

Re: Proposal: make squash-merging the default behavior for gitlab MRs

2020-10-07 Thread Thomas Friedrichsmeier
Am Tue, 6 Oct 2020 08:26:02 -0600 schrieb Nate Graham : > GitLab already *kind of* offers this, in the form of the "Squash > commits" checkbox next to the merge button. Apparently it's not > obvious enough though, because I can think of a bunch of cases of > multi-commit MRs with mostly garbage co

Re: kdemail.net as sender address

2020-09-20 Thread Thomas Friedrichsmeier
Am Sun, 20 Sep 2020 07:06:09 +1200 schrieb Ben Cooksley : > On Sun, Sep 20, 2020 at 12:00 AM Thomas Friedrichsmeier < > thomas.friedrichsme...@gmx.de> wrote: > > That's fine and good to know. I added some clarifications to > > https://community.kde.org/Infrastructur

Re: kdemail.net as sender address

2020-09-19 Thread Thomas Friedrichsmeier
Hi Ben! Am Sat, 19 Sep 2020 22:58:35 +1200 schrieb Ben Cooksley : > On Sat, Sep 19, 2020 at 7:57 PM Thomas Friedrichsmeier < > thomas.friedrichsme...@gmx.de> wrote: [...] > > Long story short: How would you (sysadmin, in particular) feel about > > the following: >

kdemail.net as sender address

2020-09-19 Thread Thomas Friedrichsmeier
Hi! In addition to @kde.org mailboxes for core developers and KDE e.V. members, KDE.org offers @kdemail.net-aliases for contributors. This is quite neat in allowing to keep a stable - and dedicated - contact address for contributions across KDE. As such it is great for use in copyright headers and

Re: Gitlab (commit) notifications

2020-05-21 Thread Thomas Friedrichsmeier
Am Thu, 21 May 2020 20:16:22 +1200 schrieb Ben Cooksley : > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier > wrote: [...] > > Is there any self-service way to receive commit/push notifications > > via email from gitlab? > > > > If so, would such notificatio

Gitlab (commit) notifications

2020-05-20 Thread Thomas Friedrichsmeier
Hi! Is there any self-service way to receive commit/push notifications via email from gitlab? If so, would such notifications include work-branches (that would be useful, IMO)? Regards Thomas pgpX1NfO91Ni3.pgp Description: Digitale Signatur von OpenPGP