Re: KDE CI: Plasma » kwin » kf5-qt5 SUSEQt5.15 - Build # 54 - Fixed!

e case of subscribe/unsubscribe requests, to -subscr...@kde.org and - unsubscr...@kde.org respectively. Regards, Ben Cooksley KDE Sysadmin > On Jul 21, 2020, at 3:48 AM, CI System wrote: > >  > *BUILD SUCCESS* > Build URL > https://build.kde.org/job/Plasma/job/kwin/job

Re: Breakage in Breeze Icons

On Wed, Jul 22, 2020 at 6:49 AM David Redondo wrote: > > I fixed the build now. There was a symlink to a removed file which > cmake -E copy_directory didn't like. Thanks for the quick response on this. > > Regards, > David > > Regards, Ben

Re: KDE CI: Plasma » kwin » kf5-qt5 FreeBSDQt5.15 - Build # 57 - Still Failing!

On Wed, Jul 22, 2020 at 10:56 AM Aleix Pol wrote: > > *shakes head at the little demon in disappointment* > > > On Wed, Jul 22, 2020 at 12:49 AM David Edmundson > wrote: > > > > > > Investigated, kwin is just failing as BSD is missing some frameworks > > changes. All good from a Plasma POV. Fra

Breakage in Breeze Icons

Hi all, The build of breeze-icons is currently broken according to the CI system. Please see https://build.kde.org/view/Failing/job/Frameworks/job/breeze-icons/ for details on this. This appears to be due to commit 84a9e3953268c499553501a5caafa7ee4f52cc79 Could someone take a look and correct th

Re: Remove stale branches?

te that work branches are also a viable alternative to forking repositories. > > -- > Regards, > Konrad Materka Regards, Ben Cooksley KDE Sysadmin

D29827: Give users the ability to disable the microphone indicator

bcooksley added a comment. You are being rejected because those commits were made using a name that appears to just be a first name - you will need to amend your user.name in your Git configuration and amend the commits accordingly REPOSITORY R115 Plasma Audio Volume Applet REVISION DETAI

D29264: New tabs for Breeze

bcooksley added a comment. Please note that should you have a KDE Developer account, then you can use a work branch instead of forking the repository. For more information on these please see my email to kde-devel and kde-cvs-announce. REPOSITORY R31 Breeze REVISION DETAIL https://pha

Re: Information regarding upcoming Gitlab Migration

On Sun, May 3, 2020 at 2:13 AM Michał Policht wrote: > > Hi all, Hi Michal, > > Sorry for late response, but project "cutehmi" fits into "sdk" category > better than "applications" (technically it's a framework, but I guess > "frameorks" is reserved for well integrated KDE Frameworks). I have n

Re: Information regarding upcoming Gitlab Migration

On Sat, May 2, 2020 at 9:04 AM Nate Graham wrote: > > On 5/1/20 2:09 PM, Ben Cooksley wrote: > > Unfortunately sharing of projects/repositories across groups does not > > impact on tasks and reviews. > > This means that merge requests for Planet (which is currently share

Re: Information regarding upcoming Gitlab Migration

On Sat, May 2, 2020 at 6:17 AM Alexander Potashev wrote: > > On Tue, Apr 28, 2020 at 6:47 AM Bhushan Shah wrote: > > Use case 4 : Tom is a student in Germany and is interested in > > contributing to wikitolearn, and he asks where can I find code of the > > wikitolearn? > > Hi, Hi Alexander, > >

Re: Information regarding upcoming Gitlab Migration

On Sat, May 2, 2020 at 2:33 AM Adriaan de Groot wrote: > > On 2020 mayula d. 1id 07:08:41 CEST Ben Cooksley wrote: > > On Fri, May 1, 2020 at 2:46 AM Nate Graham wrote: > > > If I'm understanding things, we have solutions to most or all of the >

Re: Information regarding upcoming Gitlab Migration: clarifications

On Fri, May 1, 2020 at 4:38 PM Nate Graham wrote: > > > > On 4/30/20 5:59 PM, Aleix Pol wrote: > > El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid > >> Am I the only person that just has all the repos on the same folder? I > >> thought it was the common thing to do :? > > > > I do to

Re: Information regarding upcoming Gitlab Migration

On Fri, May 1, 2020 at 2:46 AM Nate Graham wrote: > > If I'm understanding things, we have solutions to most or all of the > objections raised so far: > > - Projects will be allowed to live in--or at least appear in--multiple > top-level groups (e.g. plasma-framework could appear in both the > Fra

Re: Information regarding upcoming Gitlab Migration: clarifications

On Fri, May 1, 2020 at 5:58 AM Nate Graham wrote: > > > > On 4/30/20 11:43 AM, Aleix Pol wrote: > > IMHO needing tools ad-hoc to KDE development can be a barrier of entrance. > > I feel like these things make us look distant, it's important that > > people's skills translate automatically when the

Re: Information regarding upcoming Gitlab Migration: clarifications

On Fri, May 1, 2020 at 6:04 AM Ivan Čukić wrote: > > > We have made a big fuss in the past about having different projects > > that do the same thing and now we'll have that but also we'll have > > several projects with the same name? > > It really feels off to me and I wonder if this is related t

Re: Information regarding upcoming Gitlab Migration: clarifications

On Fri, May 1, 2020 at 5:44 AM Aleix Pol wrote: > > On Wed, Apr 29, 2020 at 12:25 PM Bhushan Shah wrote: > > > > Good afternoon, > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > I want to clarify some bits for which we have gotten a questions about, >

Re: Information regarding upcoming Gitlab Migration

On Tue, Apr 28, 2020 at 11:09 PM Adriaan de Groot wrote: > > There are a whole bunch of considerations and use-cases being discussed at > once in this thread, and Leinir's post made me think a bit about different > actors can interact with "the collection of repositories". > > One actor is "toolin

Re: Information regarding upcoming Gitlab Migration

On Tue, Apr 28, 2020 at 8:31 AM Albert Astals Cid wrote: > > El dilluns, 27 d’abril de 2020, a les 13:19:07 CEST, Ben Cooksley va escriure: > > On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud > > wrote: > > > > > > Hi, > > > > > > L

Re: Information regarding upcoming Gitlab Migration

On Tue, Apr 28, 2020 at 1:46 AM Nate Graham wrote: > > > > On 4/27/20 4:38 AM, Aleix Pol wrote: > > Does this mean that to clone it we'll have to go "git clone > > kde:games/knetwalk" or something along the lines? > > > > If that's the case I'd much prefer if we didn't do this, at the moment > > i

Re: Information regarding upcoming Gitlab Migration

On Mon, Apr 27, 2020 at 11:12 PM Olivier Churlaud wrote: > > Hi, > > Le lundi 27 avril 2020, 12:38:42 CEST Aleix Pol a écrit : > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > > replies] > > > > > > Hello Com

Re: Information regarding upcoming Gitlab Migration

On Mon, Apr 27, 2020 at 10:50 PM Piyush Aggarwal wrote: > > > > On Mon, 27 Apr, 2020, 4:09 pm Aleix Pol, wrote: >> >> On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: >> > >> > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for >> > replies] >> > >> > Hello Community members, >

Re: Information regarding upcoming Gitlab Migration

On Mon, Apr 27, 2020 at 10:39 PM Aleix Pol wrote: > > On Mon, Apr 27, 2020 at 3:41 AM Bhushan Shah wrote: > > > > [Please keep sysad...@kde.org list or bs...@kde.org in the CC for > > replies] > > > > Hello Community members, > > > > In view of upcoming Gitlab migration, we sysadmin team wants to

Re: Information regarding upcoming Gitlab Migration

On Mon, Apr 27, 2020 at 7:26 PM Ilya Bizyaev wrote: > > Hello Bhushan! > > Thank you for you work on the Gitlab migration! > > The lists look good! Here are some ideas that I have, in case you think they > can be considered before we transition: > • The "applications" category is somewhat mislead

Re: Information regarding upcoming Gitlab Migration

On Mon, Apr 27, 2020 at 6:33 PM Rolf Eike Beer wrote: > > Bhushan Shah wrote: > > > I've worked on draft "move" of the current set of the repositories in > > their respective subgroups at the repo-metadata project's branch [1]. > > You can browse the directory structure to get idea of how final >

Re: Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 FreeBSDQt5.14 - Build # 8 - Still Failing!

On Mon, Apr 20, 2020 at 10:29 AM Friedrich W. H. Kossebau wrote: > > Am Sonntag, 19. April 2020, 21:13:01 CEST schrieb Ben Cooksley: > > Hi all, > > > > Another breakage in Qt? > > Should be fixed now (restarted build now completed), with similar traps also >

Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 FreeBSDQt5.14 - Build # 8 - Still Failing!

Hi all, Another breakage in Qt? Cheers, Ben -- Forwarded message - From: CI System Date: Sun, Apr 19, 2020 at 11:44 PM Subject: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 FreeBSDQt5.14 - Build # 8 - Still Failing! To: *BUILD FAILURE* Build URL https://bui

Re: Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 FreeBSDQt5.14 - Build # 7 - Still Failing!

On Sun, Apr 19, 2020 at 3:13 AM David Faure wrote: > > On Saturday, April 18, 2020 5:06:43 PM CEST Friedrich W. H. Kossebau wrote: > > Am Samstag, 18. April 2020, 16:26:57 CEST schrieb David Faure: > > > On Saturday, April 18, 2020 7:09:25 AM CEST Ben Cooksley

Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 FreeBSDQt5.14 - Build # 7 - Still Failing!

Hi all, Please see below - any ideas as to why KHelpCenter no longer successfully builds? It doesn't look like KHelpCenter has changed... Cheers, Ben -- Forwarded message - From: CI System Date: Sat, Apr 18, 2020 at 4:38 PM Subject: KDE CI: Administration » Dependency Build Pla

Re: Update on Status of Gitlab Migration

On Tue, Apr 14, 2020 at 2:37 PM Nate Graham wrote: > > On 4/13/20 6:59 PM, Ben Cooksley wrote: > > Why do we need to mimic them? > > > > If you Google "KDE Gitlab" then the first hit is invent.kde.org > > <http://invent.kde.org>. > > To flip it

Re: Update on Status of Gitlab Migration

On Mon, Apr 13, 2020 at 9:29 AM Johan Ouwerkerk wrote: > > On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk > wrote: > > > > > > > > We may need to do on-the-fly conversion of the kde: repo paths if they > > > won't be expressible as 'kde:foo' in the future, but we should have the > > > informat

Re: Update on Status of Gitlab Migration

On Tue, 14 Apr 2020, 11:45 am Aleix Pol, wrote: > On Mon, Apr 13, 2020 at 8:30 PM Ben Cooksley wrote: > > > > On Tue, Apr 14, 2020 at 3:35 AM Nate Graham wrote: > > > > > > On 4/13/20 4:44 AM, Albert Vaca Cintora wrote: > > > > Regarding this: is th

Re: Update on Status of Gitlab Migration

On Tue, Apr 14, 2020 at 3:35 AM Nate Graham wrote: > > On 4/13/20 4:44 AM, Albert Vaca Cintora wrote: > > Regarding this: is the subdomain going to stay invent.kde.org once we > > have officially moved? I find it's a bit confusing to use that instead > > of gitlab.kde.org > > I agree. gitlab.kde.o

Re: Update on Status of Gitlab Migration

On Sun, Apr 12, 2020 at 11:04 AM Johan Ouwerkerk wrote: > > On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk > wrote: > > > > Yes the only reason why a cleanup script might be needed is if the > > logical path used to express the repo in dependency information > > changes at the same time. E.g.

Re: Update on Status of Gitlab Migration

On Sat, Apr 11, 2020 at 11:31 PM Johan Ouwerkerk wrote: > > On Sat, Apr 11, 2020 at 11:36 AM Ben Cooksley wrote: > > > > Should anyone have any questions on the above, please let us know. > > > > Does the migration also mean that `git.kde.org` push URL will be

Notice of upcoming changes to the behaviour of the anongit network

of offering support for redirects (should those be needed) Should anyone have any questions regarding this, please let us know. Thanks, Ben Cooksley KDE Sysadmin

Update on Status of Gitlab Migration

f the group, and you have previously logged into Gitlab, please visit KDE Identity and make a change to your details there, which will trigger a sync of your account to Gitlab. Should anyone have any questions on the above, please let us know. Thanks, Ben Cooksley KDE Sysadmin

Re: Making PipeWire required for xdp-kde

On Wed, Apr 8, 2020 at 12:05 AM David Edmundson wrote: > > Check the KDE CI has everything before doing that. > You may also find kde-distro-packagers a better ML to ask to find real > world problems. At the moment per the CMake logs, we do not have Pipewire installed. You'll need to file a tick

D28214: Add background portal

bcooksley added a comment. This change, as committed does not appear to compile: https://build.kde.org/view/Failing/job/Plasma/job/xdg-desktop-portal-kde/job/kf5-qt5%20FreeBSDQt5.14/lastFailedBuild/console REPOSITORY R838 Flatpak Support: KDE Portal for XDG Desktop REVISION DETAIL http

Re: KDE CI: Administration » Dependency Build Plasma kf5-qt5 SUSEQt5.12 - Build # 95 - Failure!

On Wed, Mar 25, 2020 at 6:39 PM Ömer Fadıl USTA wrote: > > > Ben Cooksley , 25 Mar 2020 Çar, 07:48 tarihinde şunu yazdı: >> >> The Dependency Build says plasma-desktop is broken. >> >> Ideas anyone? >> > Hello ben, It looks like this will solve that prob

D28232: [SpellChecking KCM] Fix the build

bcooksley added a comment. @bport Sorry, but this cannot be left in a broken state like this. Reality is that the `plasma-desktop` repository declares that it depends on a minimum of Qt 5.12 at the moment in CMake, so that is what it needs to build with. Should this be insufficient, th

Fwd: KDE CI: Administration » Dependency Build Plasma kf5-qt5 SUSEQt5.12 - Build # 95 - Failure!

The Dependency Build says plasma-desktop is broken. Ideas anyone? Cheers, Ben -- Forwarded message - From: CI System Date: Wed, Mar 25, 2020 at 4:24 PM Subject: KDE CI: Administration » Dependency Build Plasma kf5-qt5 SUSEQt5.12 - Build # 95 - Failure! To: *BUILD FAILURE* Bui

Re: KDE CI: Plasma » plasma-desktop » kf5-qt5 FreeBSDQt5.14 - Build # 4 - Still Failing!

On Wed, Mar 25, 2020 at 12:05 PM David Edmundson wrote: > > Briefly investigated, it seems another false positive of frameworks being out > of sync which will resolve itself. This means that Plasma has introduced API into Frameworks and then rapidly proceeded with making use of it - so it is a v

Re: CI talk (Was: re: Manner in which kde-gtk-config development is conducted)

On Mon, Mar 23, 2020 at 6:53 AM Albert Astals Cid wrote: > > El diumenge, 22 de març de 2020, a les 16:12:04 CET, Ben Cooksley va escriure: > > On Mon, Mar 23, 2020 at 12:49 AM Albert Astals Cid wrote: > > > > > > El diumenge, 22 de març de 2020, a le

Re: CI talk (Was: re: Manner in which kde-gtk-config development is conducted)

On Mon, Mar 23, 2020 at 12:41 AM Johan Ouwerkerk wrote: > > On Sun, Mar 22, 2020 at 3:20 AM Ben Cooksley wrote: > > > > We already do have a repository of artifacts :) > > You can find the public view of this at > > https://build-artifacts.kde.org/production/ > &

Re: CI talk (Was: re: Manner in which kde-gtk-config development is conducted)

On Mon, Mar 23, 2020 at 12:49 AM Albert Astals Cid wrote: > > El diumenge, 22 de març de 2020, a les 3:19:57 CET, Ben Cooksley va escriure: > > Note however that images based upon Fedora or anything that shares > > it's lineage (including CentOS and it's derivates) is

Re: CI talk (Was: re: Manner in which kde-gtk-config development is conducted)

On Sun, Mar 22, 2020 at 12:00 PM Johan Ouwerkerk wrote: > > On Sat, Mar 21, 2020 at 10:27 PM Ben Cooksley wrote: > > > > On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk > > wrote: > > > > > > On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote: >

Re: Manner in which kde-gtk-config development is conducted

On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk wrote: > > On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote: > > > > Comments welcome. Please note that simply fixing the dependency > > breakage in this case is not enough to resolve this - there are > > unde

Re: Manner in which kde-gtk-config development is conducted

On Sun, Mar 22, 2020 at 3:08 AM David Edmundson wrote: > > You're absolutely right that mistakes were made and have reason to be > frustrated. > > kde-gtk-config is now maintained by new developers. > Plasma has a new influx of new people which is good to see and > something we need to foster care

Re: KDE CI: Plasma » drkonqi » kf5-qt5 FreeBSDQt5.13 - Build # 75 - Still Failing!

On Fri, Mar 20, 2020 at 7:06 AM David Edmundson wrote: > > I investigated this (slightly) it seems these are false positives. Hi David, > > A new method was introduced in kcrash, that symbol is exported, then this > fails to link. > It implies this is just the CI system linking against an old k

Manner in which kde-gtk-config development is conducted

fixing the dependency breakage in this case is not enough to resolve this - there are underlying issues which need to be addressed here. Regards, Ben Cooksley KDE Sysadmin

D28098: remove pointless and arbitrary 4 line frame limit

bcooksley requested changes to this revision. bcooksley added a comment. This revision now requires changes to proceed. There should be no further changes to Dr Konqi at this time as it fails to build from source on both FreeBSD and Windows. Please see the relevant CI jobs for more informati

D28076: [GTK3] Add module to reload colorscheme in GTK3 apps without restarting them

bcooksley added a comment. This change, and changes subsequent to it have broken the build of kde-gtk-config. Please see https://build.kde.org/view/Failing/job/Plasma/job/kde-gtk-config/job/kf5-qt5%20SUSEQt5.12/ and https://build.kde.org/view/Failing/job/Plasma/job/kde-gtk-config/job/k

Re: Moving bugzilla components

On Wed, Mar 11, 2020 at 6:12 PM David Edmundson wrote: > > As a reminder, bugzilla components should not be moved without prior > discussion with maintainers. > > @nate please inform everyone of the bulk changes made and we'll see which we > keep. Please also note that bulk changes which are ja

Re: breeze-gtk now in invent

On Wed, 26 Feb 2020, 1:50 AM Jonathan Riddell, wrote: > breeze-gtk seems to have moved to invent for development. > > Looking through the list on invent I don't see any other Plasma projects > there. > > That's cool but it's useful to know when and why moves like this happens > as it needs change

Re: 2 kirigami fixes for a point release

On Mon, Feb 17, 2020 at 10:55 AM Friedrich W. H. Kossebau wrote: > > Sorry, no time to rewrite to make this short. > > Am Mittwoch, 12. Februar 2020, 21:59:32 CET schrieb Nate Graham: > > [+ frameworks and plasma mailing lists] > > > > On 2020-02-12 11:31, Albert Astals Cid wrote: > > > El dimecre

Re: 2 kirigami fixes for a point release

On Mon, Feb 17, 2020 at 10:43 AM Albert Astals Cid wrote: > > El diumenge, 16 de febrer de 2020, a les 22:34:51 CET, David Faure va > escriure: > > On dimanche 16 février 2020 22:17:17 CET Albert Astals Cid wrote: > > > This is their fault, they as a distribution have decided to support a > > >

Re: 2 kirigami fixes for a point release

On Sun, Feb 16, 2020 at 8:35 AM Nate Graham wrote: > > On 2020-02-15 11:55, Ben Cooksley wrote: > > My point above was that the version you decide to freeze on should > > only be the version you depend on during development. > > The version you depend on when you release

Re: 2 kirigami fixes for a point release

On Sat, Feb 15, 2020 at 8:10 AM Nate Graham wrote: > > On 2020-02-13 00:42, Ben Cooksley wrote: > > A better way of approaching this would be to freeze the Frameworks > > version you are going to require API wise at an earlier point in the > > Plasma development cycle. Thi

Re: 2 kirigami fixes for a point release

On Thu, Feb 13, 2020 at 9:00 PM Christoph Feck wrote: > > On 02/13/20 08:42, Ben Cooksley wrote: > > Part of the issue here is that Plasma has been known to add API to > > Frameworks and then immediately, without any delay, start using it > > (pretty much always br

Re: 2 kirigami fixes for a point release

On Thu, Feb 13, 2020 at 10:00 AM Nate Graham wrote: > > [+ frameworks and plasma mailing lists] > > > On 2020-02-12 11:31, Albert Astals Cid wrote: > > El dimecres, 12 de febrer de 2020, a les 15:37:09 CET, Nate Graham va > > escriure: > >> Personally I think it would be nice to have > >> 86f9884

D26733: sync tooltip delay with systemsettings

bcooksley added a comment. The code if memory serves originates from Dolphin, it was copied from there into System Settings (which was done by me - we weren't sure about API stability at the time for upstreaming to kdelibs as it was at the time), and then must have been copied again from the

D26544: Switch the Plasma Desktop KCMs to using KNewStuffQuick

bcooksley added a comment. Cancel that, it fails to build on Linux as well - i'm guessing that the KNetstuff changes have not been landed? REPOSITORY R119 Plasma Desktop REVISION DETAIL https://phabricator.kde.org/D26544 To: leinir, mart, ngraham Cc: bcooksley, davidedmundson, ngraham,

D26544: Switch the Plasma Desktop KCMs to using KNewStuffQuick

bcooksley added a comment. This change fails to build from source on FreeBSD due to missing headers in Frameworks. REPOSITORY R119 Plasma Desktop REVISION DETAIL https://phabricator.kde.org/D26544 To: leinir, mart, ngraham Cc: bcooksley, davidedmundson, ngraham, plasma-devel, LeGast00n,

[sysadmin/ci-tooling] system-images: Include libXxf86vm in our images for KGamma5.

Git commit fb5f3e02330c9d8a95d1580f16adbf7ca016da90 by Ben Cooksley. Committed on 15/01/2020 at 07:29. Pushed by bcooksley into branch 'master'. Include libXxf86vm in our images for KGamma5. CCMAIL: plasma-devel@kde.org M +2-0system-images/suse-qt512/Dockerfile M +2-0

D26544: Switch the Plasma Desktop KCMs to using KNewStuffQuick

bcooksley added a comment. In the case of three Frameworks (namely plasma-framework, kwayland and kwindowsystem) I have on file requests from the Plasma and KWin developers informing me that their software does indeed require latest HEAD (with no delay) of those particular frameworks, hence

D26399: Don't run qmllint if ECM_ENABLE_SANITIZERS is defined

bcooksley added a comment. It was the Latte Dock code that needed adjusting to make use of ECM's `KDECompilerSettings` module. REVISION DETAIL https://phabricator.kde.org/D26399 To: jjazeix, bcooksley, mvourlakos Cc: plasma-devel, acemond, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fb

D26399: Don't run qmllint if ECM_ENABLE_SANITIZERS is defined

bcooksley added a comment. Thanks for sorting that Johnny, it's appreciated. REVISION DETAIL https://phabricator.kde.org/D26399 To: jjazeix, bcooksley, mvourlakos Cc: plasma-devel, acemond, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, GB_2, niccolove, ragreen, lavender, Zre

D26399: Don't run qmllint if ECM_ENABLE_SANITIZERS is defined

bcooksley added a comment. Unfortunate, it definitely looked like QMLLint was the cause of the issues. Given that Latte Dock is the only application impacted by this, does it do anything else special with regards to linking the application (such as not making use of ECM). REVISION DETAI

D25185: Icon: solve threading issue on when the source is http

bcooksley added a comment. As a reminder, please ensure that all QNetworkAccessManager code is built to force handling of redirects on - code that interacts with KDE.org and does not explicitly handle redirects is not supported by Sysadmin. REPOSITORY R169 Kirigami REVISION DETAIL https

FreeBSD CI Failures

Hi all, Apologies for the failures which took place in the past hour for the FreeBSD section of the CI system. This was caused by a regression within the Jenkins durable task plugin, so we've reverted to a previous version of this plugin and will await a fix from the responsible developers. Chee

D23342: Add a per-process network information plugin

bcooksley added a comment. Please see https://build.kde.org/job/Plasma/job/ksysguard/job/kf5-qt5%20FreeBSDQt5.13/10/console This has now caused Dependency Builds to fail, which means CI for Plasma is now unmaintainable. Could we please get this fixed? REPOSITORY R106 KSysguard R

D24011: Provide a telemetrics kcm module for Plasma

bcooksley added a comment. Please ensure that the KCM links to https://kde.org/privacypolicy-apps.php. It would also be appreciated if those implementing or modifying Telemetry in their applications read this first as well. Where you need to state what the KCM is for, it would be appre

Re: Plasma 5.12.9 LTS

On Wed, Sep 11, 2019 at 9:20 PM Vlad Zagorodniy wrote: > > On 9/11/19 9:39 PM, Christoph Feck wrote:> sizeInBytes() can be emulated > with bytesPerLine() * height(). > > The issue is already fixed. Please roll out new tar. > > > Would it be possible to adopt the convention "tars are announced a fe

D22106: [Separator] Match Breeze borders' color

bcooksley added a comment. Please note that depending on the repository. Phabricator can take anywhere from a minute or two, to update to an hour to pick up changes to a repository (it polls repositories unfortunately, and those with more frequent changes are polled more often by Phabricator

D23302: Stop installing two desktop files

bcooksley added a comment. The split with two different desktop files was imposed upon us by the GNOME packagers at Ubuntu so eliminating the extra file isn't an option I'm afraid. REPOSITORY R124 System Settings REVISION DETAIL https://phabricator.kde.org/D23302 To: ngraham, apol, #pla

Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 SUSEQt5.12 - Build # 50 - Still Failing!

Hi all, Please see below - can someone take a look at the below build failure? Thanks, Ben -- Forwarded message - From: CI System Date: Sat, Aug 17, 2019 at 10:05 AM Subject: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 SUSEQt5.12 - Build # 50 - Still Failing!

Re: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 SUSEQt5.12 - Build # 46 - Still Failing!

across? Cheers, Ben > > > On Fri, Aug 9, 2019, 23:21 Ben Cooksley wrote: > >> Hi folks, >> >> Could someone please look into the below QMutex include problem within >> plasma-workspace? >> >> Thanks, >> Ben >> >> -- Forwarded mes

Fwd: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 SUSEQt5.12 - Build # 46 - Still Failing!

Hi folks, Could someone please look into the below QMutex include problem within plasma-workspace? Thanks, Ben -- Forwarded message - From: CI System Date: Sat, Aug 10, 2019 at 8:18 AM Subject: KDE CI: Administration » Dependency Build Plasma stable-kf5-qt5 SUSEQt5.12 - Build #

Issues with Jenkins Builds

f you don't have access to do this yourself. Apologies for the inconvenience caused. Regards, Ben Cooksley KDE Sysadmin

Unannounced Dependency Change - plasma-framework

Hi all, Recently builds of plasma-framework have started failing on Windows due to the absence of "gzip", which was added as a Dependency without any announcement as is required of all new dependencies. With regards to Windows in particular, usually Craft based systems will make use of 7-Zip inst

Re: CI system maintainability

On Sat, Mar 30, 2019 at 10:46 PM Volker Krause wrote: > > On Friday, 29 March 2019 20:54:54 CET Ben Cooksley wrote: > > On Fri, Mar 29, 2019 at 6:45 AM Johannes Zarl-Zierl > > > I fear that a mandatory reviews would add too juch strain on smaller > > > teams. If t

Re: CI system maintainability

On Fri, Mar 29, 2019 at 9:56 PM Kevin Ottens wrote: > > Hello, > > On Thursday, 28 March 2019 20:35:11 CET Dr.-Ing. Christoph Cullmann wrote: > > I and others tried to get more reviews done in the past, but actually I > > merged more than once stuff that I reviewed but it did break the CI. > > Tha

Re: CI system maintainability

On Fri, Mar 29, 2019 at 10:33 PM Friedrich W. H. Kossebau wrote: > > Am Donnerstag, 28. März 2019, 23:06:17 CET schrieb laurent Montel: > > Le jeudi 28 mars 2019, 18:27:42 CET Friedrich W. H. Kossebau a écrit : > > > Am Donnerstag, 28. März 2019, 16:56:33 CET schrieb laurent Montel: > > > > Le jeu

Re: CI system maintainability

On Fri, Mar 29, 2019 at 6:45 AM Johannes Zarl-Zierl wrote: > > Hi, Hi, > > (Sorry for top-posting) > > I fear that a mandatory reviews would add too juch strain on smaller teams. > If there's just one person with an intimate knowledge of the code-base, plus > two co-developers, then who should

Re: CI system maintainability

On Thu, Mar 28, 2019 at 7:56 PM Konstantin Kharlamov wrote: > > > > On Чт, Mar 28, 2019 at 19:40, Ben Cooksley wrote: > > Hi all, > > > > We currently have a rather substantial issue, in that the CI system > > has been once again left in a position where it is

CI system maintainability

system vs. the amount of care actually being given by some developers (who are ignoring it's failure emails) it becomes questionable whether the effort is worth the return (and if not, we should just shut it down) Regards, Ben Cooksley KDE Sysadmin

Re: [sysadmin/ci-tooling] build-specs/Plasma: Disable execution of tests for plasma-integration.

On Sun, Jan 27, 2019 at 6:41 AM Albert Astals Cid wrote: > > El dissabte, 26 de gener de 2019, a les 13:05:23 CET, Bhushan Shah va > escriure: > > > > > > Can we try to get this documented? 1.7GB isn't a lot for lots of people > > > with fast internet (if the server serves fast enough). > > > >

Re: [sysadmin/ci-tooling] build-specs/Plasma: Disable execution of tests for plasma-integration.

On Sat, Jan 26, 2019 at 10:35 AM Albert Astals Cid wrote: > > El dilluns, 21 de gener de 2019, a les 6:46:32 CET, Ben Cooksley va escriure: > > Git commit f6c79ff4787148459aa91c17d683e4fd6a57c323 by Ben Cooksley. > > Committed on 21/01/2019 at 05:46. > > Pushed by bcook

[sysadmin/ci-tooling] build-specs/Plasma: Disable execution of tests for plasma-integration.

Git commit f6c79ff4787148459aa91c17d683e4fd6a57c323 by Ben Cooksley. Committed on 21/01/2019 at 05:46. Pushed by bcooksley into branch 'master'. Disable execution of tests for plasma-integration. This is necessary to ensure CI nodes do not become blocked due to hanging tests with

D17154: Go back to SCSS

bcooksley added a comment. Thanks @ngraham. I've now scheduled the addition of `scss` into the images with 63d16727883e9c9f9d09bdd2bc7163fb386c0a57 REPOSITORY R98 Breeze for Gtk REVISION DETAIL https://phabricat

Re: Downtime announcement: www.kde.org

On Sat, Nov 3, 2018 at 7:50 AM Ben Cooksley wrote: > > Hi all, Hi all, > > In order to allow for hardware maintenance, one of our physical > hardware hosts will need to be shutdown for a few hours on Monday. > This downtime will commence around 9:30am UTC and may ta

Re: KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.9 - Build # 69 - Still Failing!

Hi Marco & Plasma Folks, Can someone please look into this? This seems to be the usual class of QTest compilation failures due to changes in how it handles casts between 5.9 / 5.10. Cheers, Ben On Sat, Nov 3, 2018 at 5:06 PM CI System wrote: > *BUILD FAILURE* > Build URL > https://build.kde.or

Downtime announcement: www.kde.org

captive portal) - Any application using GHNS In addition, any other site which is hosted by the server known as "olios.kde.org" will also be unavailable during this time. Apologies for any inconvenience caused. Regards, Ben Cooksley KDE Sysadmin

Fwd: KDE CI: Administration » Dependency Build Plasma kf5-qt5 SUSEQt5.11 - Build # 5 - Failure!

Hi all, Please see below. If someone could please take a look and fix this failure that would be appreciated. On another note, the Marble build recently broke with a similar error - has something been changed in Frameworks to remove a dependency on DBus by any chance? Cheers, Ben -- Fo

Re: CI System Reorganisation

On Mon, 10 Sep 2018, 01:17 Christoph Feck, wrote: > On 09.09.2018 10:59, Ben Cooksley wrote: > > As a followup to my earlier mail sent about 3 weeks ago, i've now > > transitioned all builds on the CI system over to the folder layout > > previously described. > >

CI System Reorganisation

e DSL Job is run the views I mentioned previously, which will provide recursive overviews for those who prefer those, will become available. If anyone encounters any issues please let us know. Thanks, Ben Cooksley KDE Sysadmin

Re: Upcoming reorganisation of the CI system

, "") > qt.qpa.gl: QWindowsOpenGLTester::supportedRenderers > GpuDescription(vendorId=0x0, deviceId=0x0, subSysId=0x0, revision=0, driver: > "", version=, "") renderer: QFlags(0x8|0x20) > qt.qpa.gl: Qt: Using EGL from libEGLd > qt.qpa.gl: Qt: Using OpenG

Re: Upcoming reorganisation of the CI system

Hi all, Final call for objections or queries for this change - i'll be looking to roll this out this weekend. Note: Plasma and KDevelop, i'm not subscribed to your lists so please ensure i'm in CC for any responses. Cheers, Ben

Re: Upcoming reorganisation of the CI system

On Tue, 14 Aug 2018, 17:09 Christoph Feck, wrote: > On 14.08.2018 15:03, Ben Cooksley wrote: > > Currently CI jobs are all created within a flat namespace, meaning > > that it is quite difficult to view the overall status of an individual > > project. Additionally, it creat

Upcoming reorganisation of the CI system

system (although downtime will be needed in order to allow for the changeover). Thanks, Ben Cooksley KDE Sysadmin

<    1   2   3   4   5   >