On Wed, May 8, 2024 at 10:03 AM 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.
>
>
> Bad news: 1 repository is still failing and 3 new ones started
On Wed, May 8, 2024 at 7:19 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.
>
> Bad news: 9 repositories have started failing and 1 is still
On Sun, May 5, 2024 at 10:50 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: 1 repo was fixed
>
> Bad news: 2 repo started failing
>
On Sun, May 5, 2024 at 8:37 AM wrote:
> On 2024-05-04 21:56, Akseli Lahtinen wrote:
> > On Saturday 4 May 2024 14:47:35 GMT+3 christ...@cullmann.io wrote:
> >> My proposal: we enforce Breeze as icon set and style everywhere. And
> >> we
> >> provide still a way to overwrite that for the user,
On Wed, May 1, 2024 at 12:57 PM Nicolas Fella wrote:
> On 01.05.24 01:54, 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
On Sun, Apr 28, 2024 at 9:23 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.
>
> Bad news: 1 repo started failing
>
> kconfig:
> *
Hi all,
I have just flipped the switch that has moved the CI system over to using
Qt 6.7 for Linux builds on our SUSE images.
Should you see any issues with builds failing as a result of packages being
missing in the registry then please submit a merge request to
sysadmin/ci-management to ensure
Hi all,
I have just flipped the switch that has moved the CI system over to using
Qt 6.7 for Linux builds on our SUSE images.
Should you see any issues with builds failing as a result of packages being
missing in the registry then please submit a merge request to
sysadmin/ci-management to ensure
Hi all,
I have just flipped the switch that has moved the CI system over to using
Qt 6.7 for Linux builds on our SUSE images.
Should you see any issues with builds failing as a result of packages being
missing in the registry then please submit a merge request to
sysadmin/ci-management to ensure
Hi all,
As part of routine maintenance on Invent (Gitlab) i've been reviewing the
total amount of space currently being consumed by repositories.
At this time, the top 100 largest repositories on Invent (we have 14,000 or
so for context) are consuming around 21% of the total space. It would
Hi all,
As part of routine maintenance on Invent (Gitlab) i've been reviewing the
total amount of space currently being consumed by repositories.
At this time, the top 100 largest repositories on Invent (we have 14,000 or
so for context) are consuming around 21% of the total space. It would
On Sun, Apr 21, 2024 at 5:07 AM Ashark wrote:
> Hello.
>
Hey Andrew,
>
> I have seen a bug that kdewebkit is failing to build (406342). I was
> looking
> why the person was building that module in the first place.
>
> Afaict, this module is not used in any project. Searching in repo-metadata
On Sat, Apr 20, 2024 at 4:39 AM Kevin Ottens wrote:
> Hello,
>
Hi all,
>
> Unsurprisingly I'll be pretty much aligned with Luigi, Sune and Volker
> here I
> think. I'll try to add a couple of extra aspects to feed the thinking on
> this
> topic.
> On Friday 19 April 2024 11:04:33 CEST Carl
On Thu, Apr 11, 2024 at 1:15 AM Ralf Habacker
wrote:
> Am 10.04.24 um 10:51 schrieb Ben Cooksley:
> > umbrello - 3rd week
> > * https://invent.kde.org/sdk/umbrello/-/pipelines/657665
> > <https://invent.kde.org/sdk/umbrello/-/pipelines/657665>
> >*
On Wed, Apr 10, 2024 at 4:33 AM Volker Krause wrote:
> On Sonntag, 7. April 2024 23:02:06 CEST 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.
On Wed, Apr 10, 2024 at 9:33 AM 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: 1 repository was fixed
>
> Bad news: 2 repositories are
On Wed, Apr 10, 2024 at 9:26 AM 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: 3 repositories got fixed
>
> Bad news: 2 repositories
Git commit 9b33873bf75e362f24d6b03a2c7873fb5fa16668 by Ben Cooksley.
Committed on 10/04/2024 at 08:42.
Pushed by bcooksley into branch 'master'.
Ensure we include QtKeychain in our Windows images for Qt 5.15 and Qt 6.6.
This dependency on QtKeychain was added by PIM developers to KLDAP
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
> > * https://invent.kde.org/utilities/ktrip/-/pipelines/657661
> > * craft_android builds fail
>
> *sigh* Why does kirigami master depend on the not yet
On Mon, Apr 8, 2024 at 1:55 AM Marc Deop i Argemí wrote:
> On Saturday, 6 April 2024 18:22:22 CEST Sven Brauch wrote:
> > This is basically a discussion about whether it is less risky to trust
> > the individual developers, or the people with access to the CI signing
> > key. You are trading
On Mon, Apr 8, 2024 at 9:03 AM 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.
>
> Bad news: 1 repositories is still failing and 1 has started failing
On Sat, Apr 6, 2024 at 4:23 AM Johannes Zarl-Zierl
wrote:
> Am Freitag, 5. April 2024, 13:45:35 CEST schrieb Carl Schwan:
> > On Friday, April 5, 2024 12:04:28 PM CEST Albert Vaca Cintora wrote:
> > > - Tarballs should only be generated in a reproducible manner using
> > > scripts. Ideally by
On Sat, Apr 6, 2024 at 1:43 AM Heiko Becker wrote:
> On Friday, 5 April 2024 12:04:28 CEST, Albert Vaca Cintora wrote:
> > It seems a lot of people feel conservative in favor of tarballs, so
> > maybe I aimed too far. At least I think the discussion brought some
> > interesting points that we
On Thu, Apr 4, 2024 at 10:48 PM Sune Vuorela wrote:
> On 2024-04-03, Albert Vaca Cintora wrote:
> > What's the advantage of providing tarballs?
>
> I do think there is an advantage in being able to verify that the soure
> tarball is the same across distributions. Using a checksum on the
>
On Wed, Apr 3, 2024 at 11:41 AM 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: 1 repository was fixed
>
> Bad news: 2 repositories are
Hi all,
Due to recent updates in SUSE around signond, i've just had to remove
signond-libs-devel from our SUSE Qt 5.15 images.
This is due to signond now being built with Qt 6 - and therefore being
incompatible with Qt 5.
Looking in signon-kwallet-extension though I see it is still Qt 5 code
On Wed, Mar 27, 2024 at 5:40 AM Volker Krause wrote:
> On Dienstag, 26. März 2024 08:59:29 CET Heiko Becker wrote:
> > On Monday, 25 March 2024 23:23:01 CET, Albert Astals Cid wrote:
> > > El dissabte, 23 de març de 2024, a les 21:06:46 (CET), Julius Künzel va
> > >
> > > escriure:
> > >>
On Wed, Mar 27, 2024 at 5:55 AM Volker Krause wrote:
> On Dienstag, 26. März 2024 00:42:53 CET Albert Astals Cid wrote:
> > El dilluns, 25 de març de 2024, a les 18:03:27 (CET), Volker Krause va
> >
> > escriure:
> > > On Sonntag, 24. März 2024 23:14:12 CET Albert Astals Cid wrote:
> > > >
On Wed, Mar 13, 2024 at 12:12 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: 6 repositories got fixed
>
> Bad news: 2 repository
On Wed, Mar 13, 2024 at 12:34 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.
>
>
> VERY BAD NEWS:
> * Cantor made it to its 4th week with FreeBSD
On Mon, Mar 11, 2024 at 12:46 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.
>
> Bad news: 1 repository is still failing and 1 new has started
Hi all,
For those that have been experimenting with the Craft Continuous Delivery
jobs on Gitlab, one of the many questions we've been receiving is how to
best link to those from your websites.
I'm happy to advise that going forward build results will now be published
for release branches on
On Wed, Mar 6, 2024 at 1:22 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: 7 failing repositories from previous report got fixed
>
On Tue, Feb 27, 2024 at 1:12 PM Michael Reeves wrote:
> Does anyone have insight as to why this is happeing:
>
>
> /Resources/qml/org/kde/i18n/localeData/libki18nlocaledataqmlplugin.dylib']
> succeeded with exit code 0
> Library dependency
>
On Wed, Feb 28, 2024 at 9:45 PM Sune Vuorela wrote:
> On 2024-02-28, Albert Astals Cid wrote:
> > konversation - 1st week
> > * https://invent.kde.org/network/konversation/-/pipelines/616933
> > * cmake fails to find dbus on Linux CI
>
> This seems like intentional sillyness from the
On Mon, Feb 26, 2024 at 11:18 AM 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: 1 repository has been fixed
>
> Bad news: 3 NEW
On Sat, Feb 24, 2024 at 11:35 PM Konstantin Kharlamov
wrote:
> On Sat, 2024-02-24 at 23:07 +1300, Ben Cooksley wrote:
>
> On Sat, Feb 24, 2024 at 10:27 PM Konstantin Kharlamov
> wrote:
>
> On Sat, 2024-02-24 at 22:16 +1300, Ben Cooksley wrote:
>
> On Sat, Feb 24, 20
On Sat, Feb 24, 2024 at 10:27 PM Konstantin Kharlamov
wrote:
> On Sat, 2024-02-24 at 22:16 +1300, Ben Cooksley wrote:
>
> On Sat, Feb 24, 2024 at 8:37 PM Konstantin Kharlamov
> wrote:
>
> On Sat, 2024-02-24 at 16:31 +1300, Ben Cooksley wrote:
>
> On Fri, Feb 23, 2024
On Sat, Feb 24, 2024 at 9:21 PM Volker Krause wrote:
> On Saturday, 24 February 2024 04:31:49 CET Ben Cooksley wrote:
> > On Fri, Feb 23, 2024 at 11:12 PM Sune Vuorela wrote:
> > > On 2024-02-22, Nate Graham wrote:
> > > > I've started pondering post-megarelease p
On Sat, Feb 24, 2024 at 8:37 PM Konstantin Kharlamov
wrote:
> On Sat, 2024-02-24 at 16:31 +1300, Ben Cooksley wrote:
>
> On Fri, Feb 23, 2024 at 11:12 PM Sune Vuorela wrote:
>
> On 2024-02-22, Nate Graham wrote:
> > I've started pondering post-megarelease projects
On Fri, Feb 23, 2024 at 11:12 PM Sune Vuorela wrote:
> On 2024-02-22, Nate Graham wrote:
> > I've started pondering post-megarelease projects. We've spent so long on
> > porting and bugfixing that I think it might be useful to shift gears to
> > feature work, and I'd like to brainstorm
On Wed, Feb 21, 2024 at 12:01 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.
>
> VERY BAD NEWS:
> * Cantor made it to its 4th week with FreeBSD
On Wed, Feb 21, 2024 at 11:06 AM Heiko Becker wrote:
> On Tuesday, 20 February 2024 22:30:56 CET, 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
> >
On Mon, Feb 19, 2024 at 1:22 PM Harald Sitter wrote:
> On Sun, Feb 18, 2024 at 10:23 AM Ben Cooksley wrote:
> >
> > On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder <
> computersemiexp...@outlook.com> wrote:
> >>
> >> On Saturday, February
On Sun, Feb 18, 2024 at 2:58 PM Loren Burkholder <
computersemiexp...@outlook.com> wrote:
> On Saturday, February 17, 2024 8:35:48 PM EST Ben Cooksley wrote:
> > On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley wrote:
> >
> > The Binary Factory, alongside it's two bui
On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley wrote:
> Hi all,
>
> For some time now we have been steadily working on getting our ability to
> build everything that was previously built on the Binary Factory being
> built on Gitlab.
>
> I'm now very happy to advise th
On Sun, Feb 4, 2024 at 10:26 AM Ben Cooksley wrote:
> Hi all,
>
> For some time now we have been steadily working on getting our ability to
> build everything that was previously built on the Binary Factory being
> built on Gitlab.
>
> I'm now very happy to advise th
On Sun, Feb 11, 2024 at 1:13 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: 1 repository was fixed
>
> Bad news: 2 repositories are
On Thu, Feb 8, 2024 at 7:17 AM Friedrich W. H. Kossebau
wrote:
> 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
> >
On Wed, Feb 7, 2024 at 10:24 AM 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: 7 failing repositories from previous report got fixed
>
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
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
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
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
On Mon, Feb 5, 2024 at 1:26 AM 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: 3 repository has been fixed
>
> Bad news: 2 repositories
Hi all,
For some time now we have been steadily working on getting our ability to
build everything that was previously built on the Binary Factory being
built on Gitlab.
I'm now very happy to advise that it is now possible to perform all of
those builds on Gitlab (and depending on how far you
Hi all,
For some time now we have been steadily working on getting our ability to
build everything that was previously built on the Binary Factory being
built on Gitlab.
I'm now very happy to advise that it is now possible to perform all of
those builds on Gitlab (and depending on how far you
On Sun, Feb 4, 2024 at 5:17 AM wrote:
> On 2024-02-03 08:57, Ben Cooksley wrote:
> > On Wed, Jan 31, 2024 at 9:25 PM Ben Cooksley
> > wrote:
> >
> >> On Wed, Jan 31, 2024 at 9:06 AM Volker Krause
> >> wrote:
> >>
> >>> On Dienstag, 30
On Wed, Jan 31, 2024 at 9:25 PM Ben Cooksley wrote:
> On Wed, Jan 31, 2024 at 9:06 AM Volker Krause wrote:
>
>> On Dienstag, 30. Januar 2024 19:08:50 CET Ben Cooksley wrote:
>> > On Wed, Jan 31, 2024 at 5:10 AM Volker Krause wrote:
>> > > On Dienstag, 30. Janu
On Thu, Feb 1, 2024 at 6:40 AM Volker Krause wrote:
> On Mittwoch, 31. Januar 2024 00:12:20 CET 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.
On Thu, Feb 1, 2024 at 12:26 PM Nate Graham wrote:
> Hello folks!
>
> I'd like to gauge interest in an in-person sprint supporting the
> Automation & Systematization goal. Right now we are targeting Berlin on
> April 19th - April 24th. KDE e.V. has budget available to help with
> travel and
On Wed, Jan 31, 2024 at 12:12 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: 10 repositories that were failing are fixed :)
>
> Bad
On Wed, Jan 31, 2024 at 9:06 AM Volker Krause wrote:
> On Dienstag, 30. Januar 2024 19:08:50 CET Ben Cooksley wrote:
> > On Wed, Jan 31, 2024 at 5:10 AM Volker Krause wrote:
> > > On Dienstag, 30. Januar 2024 09:57:32 CET Ben Cooksley wrote:
> > > > On Tue, Jan 30
On Wed, Jan 31, 2024 at 7:04 AM Timothée Ravier wrote:
> 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 in the
On Wed, Jan 31, 2024 at 5:10 AM Volker Krause wrote:
> On Dienstag, 30. Januar 2024 09:57:32 CET Ben Cooksley wrote:
> > On Tue, Jan 30, 2024 at 8:47 PM Sune Vuorela wrote:
> > > On 2024-01-29, Albert Astals Cid wrote:
> > > > Bad news: 6 repositories have started
On Tue, Jan 30, 2024 at 11:59 AM 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.
>
> Bad news: 11 repositories started failing
>
>
> baloo:
> *
On Tue, Jan 30, 2024 at 10:17 AM Alexander Neundorf
wrote:
> Hi,
>
Hi Alex,
>
> I'm still running a Qt5/KF5-based setup on my machine.
> Is there a ready-to-use docker image/Dockerfile which I could use to work
> on a
> KF6-based application, maybe something from KDE neon ?
>
I'd suggest
On Tue, Jan 30, 2024 at 8:47 PM Sune Vuorela wrote:
> On 2024-01-29, Albert Astals Cid wrote:
> > Bad news: 6 repositories have started failing
> >
> > baloo:
> > kconfig:
> > kcontacts
> > kfilemetadata:
> > ki18n:
> > threadweaver:
> > * FreeBSD tests are failing
>
> I haven't studied
On Mon, Jan 29, 2024 at 10:38 PM Sune Vuorela wrote:
> 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 just to
On Thu, Jan 25, 2024 at 6:04 AM Volker Krause wrote:
> On Dienstag, 23. Januar 2024 21:35:56 CET 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.
nd whether it is
just wrong (which should be fixed in the packaging, or even better upstream
with FreeRDP2 itself) or whether that is something where the CI tools just
need to hold CMake's hand a bit more?
Cheers,
Ben
>
>
> mfg Tobias
>
> On Tue, 23 Jan 2024 at 22:11, Ben Cooksley w
On Wed, Jan 24, 2024 at 9:36 AM 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: 5 repositories got fixed
>
> Bad news: 2 repo still
On Mon, Jan 22, 2024 at 10:08 PM Ben Cooksley wrote:
> Hi all,
>
> Over the past few weeks significant work has been undertaken to develop
> the ability to make use of containerised builds for FreeBSD.
>
> Over the weekend i'm happy to report that this has now been rolled out a
On Mon, Jan 22, 2024 at 10:08 PM Ben Cooksley wrote:
> Hi all,
>
> Over the past few weeks significant work has been undertaken to develop
> the ability to make use of containerised builds for FreeBSD.
>
> Over the weekend i'm happy to report that this has now been rolled out a
On Mon, Jan 22, 2024 at 10:08 PM Ben Cooksley wrote:
> Hi all,
>
> Over the past few weeks significant work has been undertaken to develop
> the ability to make use of containerised builds for FreeBSD.
>
> Over the weekend i'm happy to report that this has now been rolled out a
Hi all,
Over the past few weeks significant work has been undertaken to develop the
ability to make use of containerised builds for FreeBSD.
Over the weekend i'm happy to report that this has now been rolled out and
is now in use across all 5 CI workers that support invent.kde.org. This
means
Hi all,
Over the past few weeks significant work has been undertaken to develop the
ability to make use of containerised builds for FreeBSD.
Over the weekend i'm happy to report that this has now been rolled out and
is now in use across all 5 CI workers that support invent.kde.org. This
means
Hi all,
Over the past few weeks significant work has been undertaken to develop the
ability to make use of containerised builds for FreeBSD.
Over the weekend i'm happy to report that this has now been rolled out and
is now in use across all 5 CI workers that support invent.kde.org. This
means
On Wed, Jan 3, 2024 at 10:51 AM Volker Krause wrote:
> On Dienstag, 2. Januar 2024 22:01:25 CET 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.
On Wed, Dec 27, 2023 at 6:52 AM Rafael Sadowski
wrote:
> On Tue Dec 26, 2023 at 11:33:16AM -0500, Neal Gompa wrote:
> > On Tue, Dec 26, 2023 at 9:26 AM Rafael Sadowski
> wrote:
> > >
> > > Hi,
> > >
> > > I am pleased to announce that KDE Plasma is available on OpenBSD
> > > alongside all KDE
On Tue, Dec 19, 2023 at 7:31 AM wrote:
> On 2023-12-18 19:14, Ben Cooksley wrote:
> > On Mon, Dec 18, 2023 at 7:48 PM Shubham Arora
> > wrote:
> >
> >> Hi Ben,
> >>
> >> Nate suggested on matrix that we can move inactive components to a
> >&
e
sorting of projects except by renaming them to something that starts with a
Z.
>
> Regards,
> Shubham
>
Cheers,
Ben
>
> Sent with Proton Mail secure email.
>
> On Monday, December 18th, 2023 at 12:12 PM, Ben Cooksley <
> bcooks...@kde.org> wrote:
>
&
ith Proton Mail secure email.
>
> On Monday, December 18th, 2023 at 10:51 AM, Ben Cooksley <
> bcooks...@kde.org> wrote:
>
>
> > On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora <
> shubhamar...@protonmail.com> wrote:
> >
> > > Hi,
> >
> >
On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora
wrote:
> Hi,
>
HI Shubham,
>
> I have compiled a list of all bugzilla components and products that need
> to be archived or removed to remove some clutter from the bugzilla
> interface.
>
> All inactive components can be archived as they are no
Hi all,
Back in May 2020, some work was done to bring a WebAssembly based build of
QML online, which resulted in https://qmlonline.kde.org/ being setup.
I'm not sure to what degree it is in use, however while looking into
porting it from the Binary Factory to Gitlab it has come to my attention
On Thu, Nov 30, 2023 at 12:06 AM Albert Astals Cid wrote:
> El dimarts, 28 de novembre de 2023, a les 11:25:42 (CET), Ben Cooksley va
> escriure:
> > On Tue, Nov 28, 2023 at 9:51 PM Anton Golubev
> >
> > wrote:
> > > On 11/25/23 02:14, Albert Astals Cid wr
On Tue, Nov 28, 2023 at 9:51 PM Anton Golubev
wrote:
> On 11/25/23 02:14, Albert Astals Cid wrote:
> > Since you don't seem to be a KDE devel just yet this would probably have
> to go
> > through the https://community.kde.org/Incubator program.
>
> The instructions on the link say that I need to
On Tue, Nov 21, 2023 at 6:29 AM wrote:
> On 2023-11-19 09:58, Ben Cooksley wrote:
> > Hi all,
> >
> > As you'll be aware, we've been working on moving CI over to Qt 6.6 for
> > a little while now, and as part of this have hit a bit of a roadblock
> &g
On Tue, Nov 21, 2023 at 6:29 AM wrote:
> On 2023-11-19 09:58, Ben Cooksley wrote:
> > Hi all,
> >
> > As you'll be aware, we've been working on moving CI over to Qt 6.6 for
> > a little while now, and as part of this have hit a bit of a roadblock
> &g
Hi all,
Over this weekend I completed a series of updates to invent.kde.org, moving
it to the latest supported version of Postgres (14) and Gitlab (16.6).
As part of that Gitlab update, additional security policies began to be
enforced by Gitlab which mean our existing method of including CI
Hi all,
Over this weekend I completed a series of updates to invent.kde.org, moving
it to the latest supported version of Postgres (14) and Gitlab (16.6).
As part of that Gitlab update, additional security policies began to be
enforced by Gitlab which mean our existing method of including CI
Hi all,
Over this weekend I completed a series of updates to invent.kde.org, moving
it to the latest supported version of Postgres (14) and Gitlab (16.6).
As part of that Gitlab update, additional security policies began to be
enforced by Gitlab which mean our existing method of including CI
Hi all,
As you'll be aware, we've been working on moving CI over to Qt 6.6 for a
little while now, and as part of this have hit a bit of a roadblock with
the Framework Syndication.
The roadblock is more likely to be due to the transition to using MSVC 2022
(and all the compiler changes that come
Hi all,
As you'll be aware, we've been working on moving CI over to Qt 6.6 for a
little while now, and as part of this have hit a bit of a roadblock with
the Framework Syndication.
The roadblock is more likely to be due to the transition to using MSVC 2022
(and all the compiler changes that come
Hi all,
For some time now the workflow for independently released KDE software
(that is, projects outside of Frameworks, Plasma and Gear) has been to
upload it to ftp://upload.kde.org/incoming/ and then file a Sysadmin ticket
(with the file hashes and destination)
There has now been a small
Hi all,
For some time now the workflow for independently released KDE software
(that is, projects outside of Frameworks, Plasma and Gear) has been to
upload it to ftp://upload.kde.org/incoming/ and then file a Sysadmin ticket
(with the file hashes and destination)
There has now been a small
On Wed, Nov 8, 2023 at 12:22 AM Jonathan Esk-Riddell
wrote:
> On Sun, Nov 05, 2023 at 12:59:28PM +0100, Friedrich W. H. Kossebau wrote:
> > kactivities and kactivities-stats: please consider proper de-KF-ication
> now
> >
> > Hi,
> >
> > with plasma-framework, kactivities and kactivities
On Sat, Nov 4, 2023 at 2:48 AM Ingo Klöcker wrote:
> On Freitag, 3. November 2023 13:01:26 CET Harald Sitter wrote:
> > What are your thoughts on having the CI be less verbose by default and
> > instead have an env var or some other toggle to switch into verbose
> > mode?
>
> +1
>
> Ideally, the
On Sat, Nov 4, 2023 at 1:01 AM Harald Sitter wrote:
> What are your thoughts on having the CI be less verbose by default and
> instead have an env var or some other toggle to switch into verbose
> mode?
>
> Specifically I'm talking about the qtlogging rules that are currently
> enabling
On Fri, Nov 3, 2023 at 12:57 PM Albert Astals Cid wrote:
> El dimecres, 1 de novembre de 2023, a les 13:25:42 (CET), Friedrich W. H.
> Kossebau va escriure:
> > Am Mittwoch, 1. November 2023, 11:55:08 CET schrieb Christophe Marin:
> > > With various alpha coming out soon, here are the notes
1 - 100 of 2350 matches
Mail list logo
