Re: Review Kid3

On Thu, Feb 13, 2020 at 9:12 PM Christoph Feck wrote: > > On 02/13/20 07:11, Urs Fleisch wrote: > > As you may know, Kid3, an audio tagger, has moved from SourceForge.net to > > kde.org. Jonathan Riddell is attending the incubation process as a sponsor. > > To complete the incubation, I would

[sysadmin/repo-metadata] projects/extragear/sdk/ikona: Move Ikona to Extragear/SDK per the request of it's maintainer.

Git commit 3d997e588c3e237cf92a78294467342f69cd3a56 by Ben Cooksley. Committed on 12/02/2020 at 07:18. Pushed by bcooksley into branch 'master'. Move Ikona to Extragear/SDK per the request of it's maintainer. Fixes T12684 CCMAIL: kde-core-devel@kde.org R +0-0projects/extragear/sdk

Re: Banning QNetworkAccessManager

On Mon, Feb 3, 2020 at 11:51 PM Johan Ouwerkerk wrote: > > On Mon, Feb 3, 2020 at 11:27 AM laurent Montel wrote: > > > > Le lundi 3 février 2020, 10:49:10 CET David Edmundson a écrit : > > > I updated: > > > > > > https://community.kde.org/Policies/API_to_Avoid > > > > > > Which had no mention

Re: Banning QNetworkAccessManager

On Mon, Feb 3, 2020 at 10:49 PM David Edmundson wrote: > > I updated: > > https://community.kde.org/Policies/API_to_Avoid > > Which had no mention of this. Many thanks for updating the wiki David. > > David Cheers, Ben

Re: Banning QNetworkAccessManager

On Mon, Feb 3, 2020 at 7:42 AM Volker Krause wrote: > > I agree on the problem of QNAM's default, see also https://conf.kde.org/en/ > akademy2019/public/events/135 on that subject. > > On Saturday, 1 February 2020 23:24:14 CET Ben Cooksley wrote: > [...] > > Prior to now,

Banning QNetworkAccessManager

QNetworkAccessManager and the associated classes within the appropriate Framework (to be determined), where the defective behaviour can then be corrected. Comments? Regards, Ben Cooksley KDE Sysadmin

Re: Get Hot New Stuff - Legacy Endpoints and Multiple Requests (Discover?)

rmation from the "Details" pane as to why KIO refuses to trust connections to autoconfig.kde.org on your system. Cheers, Ben > > On Thu, Jan 30, 2020, 4:20 AM Ben Cooksley wrote: >> >> Hi all, >> >> While diagnosing an issue this evening with cdn.kde.org, I not

Get Hot New Stuff - Legacy Endpoints and Multiple Requests (Discover?)

Hi all, While diagnosing an issue this evening with cdn.kde.org, I noticed that we are still getting an extremely large number of requests for the legacy OCS/GHNS providers.xml endpoint, which is supposed to only exist for compatibility with older applications. Looking on LXR i've found that a

Re: CMake config & target challenges on moving to KF5 namespace; dir structure & API dox (Re: Submitting Grantlee as a KF5 Framework)

On Mon, Dec 30, 2019 at 3:03 AM Stephen Kelly wrote: > > > On 28/12/2019 23:30, Friedrich W. H. Kossebau wrote: > > Why are you proposing to do a step back instead to the old state, which > > everyone including you considered not that satisfying? > > Because it's a temporary situation. We still

[sysadmin/repo-metadata] projects/kdereview/grantlee: Strip Grantlee of it's KDE Git repository and therefore terminate it's status as a KDE project.

Git commit 510628f46bf2ecc6cba15e6940ca1bf3e941224c by Ben Cooksley. Committed on 09/01/2020 at 09:39. Pushed by bcooksley into branch 'master'. Strip Grantlee of it's KDE Git repository and therefore terminate it's status as a KDE project. Ref T12387 CCMAIL: kde-core-devel@kde.org CCMAIL: kde

[sysadmin/repo-metadata] projects/kdereview/ikona: Move Ikona to KDE Review

Git commit 426b91e5d9e42a875d4afadc715eda93ce88ebec by Ben Cooksley. Committed on 30/12/2019 at 17:31. Pushed by bcooksley into branch 'master'. Move Ikona to KDE Review Fixes T12449 CCMAIL: kde-core-devel@kde.org R +0-0projects/kdereview/ikona/i18n.json [from: projects/playground

Re: KDE Itinerary in kdereview

On Sat, Dec 21, 2019 at 7:59 PM Volker Krause wrote: > > On Friday, 20 December 2019 22:50:54 CET Sandro Knauß wrote: > > Hi, > > > > > KDE Itinerary has been moved to kdereview: > > > > > > Code: https://invent.kde.org/kde/itinerary > > > Workboard:

Re: Blacklisting of PIM from the CI system

On Sun, Dec 1, 2019 at 10:17 AM Volker Krause wrote: > > sigh... > > On Saturday, 30 November 2019 19:14:38 CET Ben Cooksley wrote: > [...] > > Which is where the problem with PIM comes in - because it currently > > has many repositories failing to build from source

Blacklisting of PIM from the CI system

. Fixing the current set of failures will not prevent this blacklisting action from being carried out - as a recurring issue it needs a permanent solution. Regards, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/frameworks/kquickcharts: Move KQuickCharts into Frameworks.

Git commit 81bc7c68537639a739d0f89f103a1c26b61d by Ben Cooksley. Committed on 29/11/2019 at 18:49. Pushed by bcooksley into branch 'master'. Move KQuickCharts into Frameworks. Ref T12022 CCMAIL: kde-frameworks-de...@kde.org CCMAIL: kde-core-devel@kde.org R +0-0projects/frameworks

Changes to CI System and Binary Factory

let us know. Cheers, Ben Cooksley KDE Sysadmin

Re: Work Branches

ce pushed or deleted. > > Regards, > > - Johan Cheers, Ben > > On Sat, Oct 5, 2019 at 4:11 AM Ben Cooksley wrote: > > > > Hi all, > > > > Recently we had a discussion (which I think may have ended up spread > > over a couple of mailing lists in the end) con

Re: Work Branches

On Fri, Oct 11, 2019 at 11:05 PM Michel Hermier wrote: > > Hi, > What about a refinement of that solution with "work/" and only users to > commit on their branch? In would help, if desired in the future, to enforce a > review of submited code by third party reviews even for maintainers. Hi

Re: Work Branches

Hi all, Thanks for your responses confirming Option 2 as the preferred way forward. We'll schedule this for implementation in the next few days and will announce this once it has been completed. Thanks, Ben

Re: Work Branches

On Wed, Oct 9, 2019 at 11:32 PM David Edmundson wrote: > > > 2) Protect all branches, aside from a given prefix (proposed to be work/) > > Works for me. > Would protection here also cover deletion? If so we need some heads up > notice in Plasma to do a mass move of people's forks. It would not

Re: Work Branches

On Mon, Oct 7, 2019 at 4:28 AM Luigi Toscano wrote: > > Ben Cooksley ha scritto: > > Hi all, > > > > Recently we had a discussion (which I think may have ended up spread > > over a couple of mailing lists in the end) concerning branches and the >

Work Branches

ion problems (as the branch naming conventions will be universal across all our repositories). Thoughts? Thanks, Ben Cooksley KDE Sysadmin

Re: [IMPORTANT] Binary Factory & CI System Maintenance

adding support to the Binary Factory straight forward and efficient in terms of resource utilisation. Existing work on Appimages has tended to be application specific and therefore not suitable for easy reuse (which Craft would solve) Cheers, Ben > > On Mon, Sep 16, 2019 at 3:47 PM Ben Coo

[IMPORTANT] Binary Factory & CI System Maintenance

that require the services of the Binary Factory & CI system it would be appreciated if you could please let me know so I can take that into account for scheduling the various changes. Thanks, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/kdereview/ruqola: Move Ruqola to KDE Review per the request of Laurent Montel.

Git commit ad16c293e8a0caf000157d4a1a589515ddc0f2e4 by Ben Cooksley. Committed on 12/09/2019 at 06:32. Pushed by bcooksley into branch 'master'. Move Ruqola to KDE Review per the request of Laurent Montel. CCMAIL: kde-core-devel@kde.org R +0-0projects/kdereview/ruqola/i18n.json [from

Re: Possible to move some KF5 frameworks to invent?

On Fri, Aug 16, 2019 at 6:30 AM Christoph Cullmann wrote: > > Hi, Hi Christoph, > > >> perhaps this would be some good BoF at Akademy: > >> > >> What is needed to move frameworks development to invent.kde.org. > >> > >> (I assume we want to do that some when in the future anyways) > > > > At

Re: Possible to move some KF5 frameworks to invent?

On Wed, Aug 14, 2019 at 8:25 AM Albert Astals Cid wrote: > > El dimarts, 13 d’agost de 2019, a les 13:26:43 CEST, Harald Sitter va > escriure: > > On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote: > > > > > > On Mon, Aug 12, 2019 at 11:48 PM David Faure w

Re: Possible to move some KF5 frameworks to invent?

On Wed, Aug 14, 2019 at 9:07 AM Christoph Cullmann wrote: > > Hi, > > >> > Unfortunately the problem isn't with Frameworks, Applications and > >> > Plasma - they're easy to handle and their naming can be scripted > >> > without too much trouble. > >> > The problem lies with Extragear, which has a

Re: Possible to move some KF5 frameworks to invent?

On Tue, Aug 13, 2019 at 11:27 PM Harald Sitter wrote: > > On Tue, Aug 13, 2019 at 12:54 PM Ben Cooksley wrote: > > > > On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote: > > > > > > On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote: > > > &

Re: Possible to move some KF5 frameworks to invent?

On Mon, Aug 12, 2019 at 11:48 PM David Faure wrote: > > On lundi 12 août 2019 13:04:29 CEST Ben Cooksley wrote: > > On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora > > > > wrote: > > > On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote: > > >>

Re: Possible to move some KF5 frameworks to invent?

On Mon, Aug 12, 2019 at 10:54 PM Albert Vaca Cintora wrote: > > > On Mon, Aug 12, 2019, 18:46 Ben Cooksley wrote: >> >> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora >> wrote: >> > >> > Could we use sysadmin/repo-metadata to know whic

Re: Possible to move some KF5 frameworks to invent?

esn't let us know what the other (either historical or up and coming) stable branches are called. Cheers, Ben > > On Mon, Aug 12, 2019, 17:39 Ben Cooksley wrote: >> >> On Mon, Aug 12, 2019 at 6:24 PM Kevin Ottens wrote: >> > >> > Hello, >> >> Hi Ke

Re: Possible to move some KF5 frameworks to invent?

On Mon, Aug 12, 2019 at 6:24 PM Kevin Ottens wrote: > > Hello, Hi Kevin, > > On Sunday, 11 August 2019 22:14:19 CEST Albert Astals Cid wrote: > > With phabricator you can do a "force push" to your review[1], with gitlab > > you can not[2]. > > [...] > > [2] without having your own fork of a

Re: Possible to move some KF5 frameworks to invent?

On Mon, Aug 12, 2019 at 2:53 AM Albert Astals Cid wrote: > > El diumenge, 11 d’agost de 2019, a les 12:33:19 CEST, Christoph Cullmann va > escriure: > > Hi, > > > > is it possible to move individual framework modules over to > > invent.kde.org or will that be > > done at once somewhen in the

Issues with Jenkins Builds

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

Re: Tipping the apple cart?

On Tue, Jul 2, 2019 at 7:09 PM Kai Uwe Broulik wrote: > > Hi, > > > What are you missing? > > The description of the change (Review Board had that, Phabricator > doesn't, so I got used to it, I guess...), the context of the comment > (i.e. the code snippet a comment was added to), so I don't need

Re: Tipping the apple cart?

On Tue, Jul 2, 2019 at 6:42 PM Boudewijn Rempt wrote: > > On maandag 1 juli 2019 23:34:14 CEST Albert Astals Cid wrote: > > El dilluns, 1 de juliol de 2019, a les 9:42:34 CEST, Boudewijn Rempt va > > escriure: > > > > Krita has switched from Phabricator to Gitlab a while ago, so maybe I can > >

Re: Kdiff3 gitlab move

On Sun, 30 Jun 2019, 23:34 Michael Reeves, wrote: > What would be involved in moving kdiff3 to gitlab? > Hi Michael, This is a relatively straight forward process - please file a Sysadmin ticket and we can action this. Regards, Ben >

Downtime Announcement: Transactional Email Infrastructure

and will catchup once service resumes as well. Email aliases and mailing lists will not be affected by this downtime, and the services themselves should continue to operate normally. Should anyone have any questions, please let us know. Regards, Ben Cooksley KDE Sysadmin

Re: What means having an application in "KDE Applications"

On Mon, Jun 17, 2019 at 9:42 AM Luigi Toscano wrote: > > Jonathan Riddell ha scritto: > > On Fri, Jun 07, 2019 at 12:09:27AM +0200, Albert Astals Cid wrote: > >> Can we please discuss what being in KDE Applications is first? > >> > >> You're telling apps they can join KDE Applications if they

Re: Craft missing icon on start menu shortcut

On Fri, May 10, 2019 at 3:19 AM Michael Reeves wrote: > > This message has been stuck waiting for approval for three days. Will someone > kindly address this? Hi Michael, There are currently no messages pending approval for either the kde-core-devel or kde-windows mailing lists (which is the

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 > > > tea

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. > >

Re: CI system maintainability

On Fri, Mar 29, 2019 at 10:35 PM David Faure wrote: > > On jeudi 28 mars 2019 16:56:33 CET laurent Montel wrote: > > CI: sometime I look at it, sometime not, sometime some guys informs me that > > it's broken (I remember that Luca told me some days ago that a package > > didn't compile, so I

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

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

Re: EBN Still Needed?

On Thu, Mar 28, 2019 at 6:26 AM Volker Krause wrote: > > On Tuesday, 26 March 2019 21:15:31 CET Allen Winter wrote: > > I was notified today that the Krazy runs on the EBN have been stuck (due to > > a stale lockfile) for over 3 months. Is this an indication that nobody > > looks at the EBN

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

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: EBN Still Needed?

On Wed, Mar 27, 2019 at 9:43 AM Elv1313 . wrote: > > Hello, > > First for my 2 cents, I do have it locally installed in a docker > container and I use it from time to time. Some checks (like typos) are > still worthwhile. Some other are obsoleted by Clazy and some other are > dubious in

Re: Bug 405506

On Sun, Mar 24, 2019 at 12:35 AM Michael Reeves wrote: > > https://bugs.kde.org/show_bug.cgi?id=405506. Could someone familiar with > craft help me with this one. kdiff3 doesn't require any special setup in > craft. CC'ing the appropriate mailing list for Craft related questions. Cheers, Ben

Re: KDiff3 craft setup

On Tue, Feb 19, 2019 at 7:36 PM Kevin Funk wrote: > > On Monday, 18 February 2019 17:06:25 CET Michael Reeves wrote: > > https://download.kde.org/stable/applications/18.12.1/src/kdiff3-18.12.1.tar. > > xz > > > > Get some one tell me how to change where it's trying to download from. > > KDiff3 is

[sysadmin/repo-metadata] projects/extragear/base/plasma-pass: Move plasma-pass to Extragear as requested by it's maintainer following the completion of the review.

Git commit 4a81f737b5926a1c2f7b63e4640c4e25585b2260 by Ben Cooksley. Committed on 08/02/2019 at 07:53. Pushed by bcooksley into branch 'master'. Move plasma-pass to Extragear as requested by it's maintainer following the completion of the review. Fixes T10453 CCMAIL: kde-core-devel@kde.org R

Upcoming Service Downtime

Hi all, Sysadmin is currently in the process of planning server migrations for a large number of services which have significant visibility, and which are often substantially involved in the release process for projects as well as general community operation. As it may take several hours to

Bugzilla Server Move

Hi all, We've just completed the migration of Bugzilla from a previous system to a newer system. While this hasn't changed Bugzilla itself much, it did involve an update from Ubuntu 14.04 to Ubuntu 18.04. >From our testing everything appears to be operating correctly. Should anyone see anything

Re: CI system disruption

On Sun, Jan 6, 2019 at 10:14 PM Ben Cooksley wrote: > > Hi all, Hi everyone, > > Due to a massive translation change which took place in the last 24 > hours, the CI system is currently in the process of rebuilding the > whole of KDE for all the platforms it covers

CI system disruption

. Regards, Ben Cooksley KDE Sysadmin

Re: [EBN] Re: Fwd: Cron /home/api/bin/update-all

On Sun, Dec 30, 2018 at 3:14 AM Allen Winter wrote: > > This is about investigating brokenness with the API generation on the EBN > machine. > If you know anything about it please contact me so we can fix properly. > -Allen > > On Thursday, December 27, 2018 8:13:04 AM EST Allen Winter wrote: >

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Tue, Dec 4, 2018 at 9:45 AM Elvis Angelaccio wrote: > > > > On 03/12/18 09:46, Ben Cooksley wrote: > > Hi all, > > Hi Ben Hi Elvis, > > > > > I've been informed by the PIM developers that they would like to bump > > the dependency of th

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Mon, Dec 3, 2018 at 10:31 PM René J.V. Bertin wrote: > > Hi, > > Can't you just configure the CI to use Qt 5.10? I think it's not good to > hardcode an "overzealous" (for lack of a better word) Qt version in projects > that don't require them AND I think that one should support the current

Transitioning CI builds of all non-Frameworks from Qt 5.9

Hi all, I've been informed by the PIM developers that they would like to bump the dependency of the Qt version they use, from Qt 5.9 which it's on currently, to Qt 5.10. As a consequence, due to many KDE projects using PIM libraries, their dependency on Qt will also be effectively bumped. To

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

Downtime announcement: www.kde.org

a 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

Re: Emergency downtime notice

On Wed, Oct 10, 2018 at 9:35 PM Ben Cooksley wrote: > > On Wed, Oct 10, 2018 at 8:51 PM Ben Cooksley wrote: > > > > Hi all, > > > > We've just received notice that both disks in the server hosting > > Phabricator, along with our Git and Subversion repositor

Re: Emergency downtime notice

On Wed, Oct 10, 2018 at 8:51 PM Ben Cooksley wrote: > > Hi all, > > We've just received notice that both disks in the server hosting > Phabricator, along with our Git and Subversion repositories have > failed their SMART self-assessment tests. > > I have now requested rep

Emergency downtime notice

be replaced. To preserve our data in the meantime I have shutdown the container hosting Phabricator/Git/Subversion, so they will be unavailable for the next few hours. My apologies for the inconvenience. Regards, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/kdereview/rkward: Move RKWard to KDE Review per their request.

Git commit 045ad2dee96281a9b2b97df31f3635f5e897fa05 by Ben Cooksley. Committed on 05/10/2018 at 23:01. Pushed by bcooksley into branch 'master'. Move RKWard to KDE Review per their request. Ref T9804 CCMAIL: kde-core-devel@kde.org R +0-0projects/kdereview/rkward/i18n.json [from

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

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

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,

Upcoming reorganisation of the CI system

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

Re: KDE Frameworks 5.48.0 released

org or visit https://mail.kde.org/mailman/options/ and follow the prompts there. This information is also included in the RFC standard List-Unsubscribe header, contained in all emails you've received from our lists. Regards, Ben Cooksley KDE Sysadmin > > On Sat, Jul 14, 2018, 5:37 AM David Fau

Mail system switchover complete

from KTown to Postbox) We'd like to thank Bytemark (bytemark.co.uk) for sponsoring the Letterbox server. Should anyone have any queries regarding the status of the system, please contact sysad...@kde.org, or file a Sysadmin ticket. Thanks, Ben Cooksley KDE Sysadmin

Re: Kde CI setup

On Tue, Jun 5, 2018 at 9:37 AM, Michael Reeves wrote: > I am the mantainer for kdiff3. Thanks for the reply. What systems are > currently part of this CI? I want to try and catch any issues before getting > this turned on. It depends on what platforms you want to have enabled. Currently we have

Windows CI KO until further notice

Hi all, Due to a regression of unknown origin which results in meinproc being unusable, all Windows builds which are dependent on kdoctools are currently KO on Windows. This breakage was introduced sometime shortly after the new builders became operational (but was working at that time). Until

Re: Upcoming CI changes - service disruption

On Tue, Apr 10, 2018 at 10:42 PM, Ben Cooksley <bcooks...@kde.org> wrote: > Hi all, Hi everyone, > > In order to allow for two replacement physical build hosts to be > rotated in and the old ones to be decommissioned, i'm scheduling some > downtime for both the CI system a

Upcoming CI changes - service disruption

Hi all, In order to allow for two replacement physical build hosts to be rotated in and the old ones to be decommissioned, i'm scheduling some downtime for both the CI system and the Binary Factory tomorrow. Assuming all goes well, this downtime should be fairly short. During the downtime

Phabricator mail disruption

HTML based email. My apologies for the disruption. Regards, Ben Cooksley KDE Sysadmin

Re: Falkon in kdereview

On Mon, Mar 26, 2018 at 10:08 AM, David Rosca wrote: > On Sat, Mar 24, 2018 at 7:58 PM, Dr.-Ing. Christoph Cullmann > wrote: >> Hi, >> >> no objections from my side, >> >> just a note that we need to take care of the last remaining things on >> >>

Phabricator Notification Mails

Hi all, It has been brought to my attention that some find that they are receiving too much mail or other notifications from Phabricator. For those who are unaware there are numerous options available within Phabricator to allow you to control how much it notifies you of changes. To customise

Re: Global Dependency and Release Freeze

Hi all, We've now finished catching up on everything and getting the CI system settled down again so we're now able to lift the freeze. I'll start sorting out the releases which have been requested shortly. There is still some lingering breakage impacting Akonadi and KIO however those can be

Global Dependency and Release Freeze

images, in addition to sorting out the other tickets we have received over the past few days some of which will require some time to deal with. Requests for exceptions to these freezes are not available, however we will endeavour to lift them as soon as is practicable. Regards, Ben Cooksley KDE

CI & Binary Factory maintenance

ered as they normally would. Following the maintenance the system will need to perform a complete rebuild of all Windows based projects, and will also need to catch up on the builds it has missed. As such it may take up to 24-48 hours before the system is fully functional again. Regards, Ben Cooksley

[sysadmin/repo-metadata] projects/extragear/multimedia/elisa: Move Elisa from KDE Review to Extragear - Multimedia as requested.

Git commit dbf563df2979361e9b97088e757f95315296ea19 by Ben Cooksley. Committed on 26/02/2018 at 07:19. Pushed by bcooksley into branch 'master'. Move Elisa from KDE Review to Extragear - Multimedia as requested. Ref T8080 CCMAIL: release-t...@kde.org CCMAIL: kde-core-devel@kde.org R +0-0

[sysadmin/repo-metadata] projects/kdereview/elisa: Move Elisa to KDE Review per the request of it's maintainer

Git commit 0ebff8bc19138c04a9b05f808d92c1a6bcfbc620 by Ben Cooksley. Committed on 05/02/2018 at 08:42. Pushed by bcooksley into branch 'master'. Move Elisa to KDE Review per the request of it's maintainer Fixes T7885 CCMAIL: kde-core-devel@kde.org R +0-0projects/kdereview/elisa

[sysadmin/repo-metadata] projects/kde/kdeutils/kbackup: Move KBackup to it's new home in KDE Utils.

Git commit 9146d557b5d0c00ef400241736d1bfe564576c81 by Ben Cooksley. Committed on 05/02/2018 at 08:36. Pushed by bcooksley into branch 'master'. Move KBackup to it's new home in KDE Utils. This application was in KDE Review per the mailing list announcements, it just hadn't been moved

[sysadmin/repo-metadata] projects/extragear/utils/plasma-mycroft: Move Plasma Mycroft from KDE Review to it's final home at the request of it's maintainer.

Git commit fcd2fd6eb661bec284e08cef9f844843b5696c19 by Ben Cooksley. Committed on 30/01/2018 at 09:52. Pushed by bcooksley into branch 'master'. Move Plasma Mycroft from KDE Review to it's final home at the request of it's maintainer. Ref T7814 CCMAIL: kde-core-devel@kde.org R +0-0

Re: Rebase of kopete branch and push it to master

On Thu, Jan 25, 2018 at 11:26 AM, Pali Rohár <pali.ro...@gmail.com> wrote: > On Friday 19 January 2018 21:56:10 Ben Cooksley wrote: >> On Fri, Jan 19, 2018 at 12:06 PM, Pali Rohár <pali.ro...@gmail.com> wrote: >> > On Thursday 18 January 2018 20:50:35 Be

Re: Plasma-Mycroft is in kdereview

d be moved, along with anything else that is required now that it has passed review such as CI coverage, Bugzilla products, etc. > > -- > Marco Martin Regards, Ben Cooksley KDE Sysadmin

Re: Rebase of kopete branch and push it to master

On Fri, Jan 19, 2018 at 12:06 PM, Pali Rohár <pali.ro...@gmail.com> wrote: > On Thursday 18 January 2018 20:50:35 Ben Cooksley wrote: >> Hi all, >> >> I have now completed the merge from Pali's clone repository into the >> 'master' branch of the main Kopete repo

Re: Rebase of kopete branch and push it to master

Hi all, I have now completed the merge from Pali's clone repository into the 'master' branch of the main Kopete repository. Phabricator processing of all the commits has been completed without incident. Pali, please revise the metadata accordingly in sysadmin/repo-metadata (for i18n) and

Re: Python bindings using cppyy (was: An update on Python bindings)

oaded worked). For binaries, that would be best handled by the Binary Factory. > > Finally, now would be a good time for anybody else who wants to get involved > to step up, especially as a new job limits my free time. > > Thanks, Shaheed Cheers, Ben Cooksley KDE Sysadmin > > P

Re: Rebase of kopete branch and push it to master

On Tue, Jan 16, 2018 at 9:24 PM, Ivan Čukić wrote: > Hi all, Hi Ivan (and others), > > Would it be possible for sysadmins to just rename master -> > master-kde4, and master-kf5 -> master? If master were merged into frameworks we could of course do such a rename without too

Re: 2 New Plasmoids in Kdereview

nks for that detail, and for starting the separate threads for each. In about 2 weeks time please file Sysadmin tickets and we can get both moved to Extragear, and from there look towards making first releases of both. > > Thank You, > Martin Cheers, Ben > > > On Thursday,

Re: plasma-active-window-control - was -Re: 2 New Plasmoids in Kdereview

On Mon, Jan 15, 2018 at 12:15 PM, Martin Kostolný wrote: > You are right, integration of global-menu functionality is copied from > appmenu widget code. It is also mentioned in > plasma-active-window-control/plugin/README. Hi Martin, > > I consider it a temporary

Re: 2 New Plasmoids in Kdereview

On Fri, Jan 12, 2018 at 11:18 AM, Ingo Klöcker <kloec...@kde.org> wrote: > On Donnerstag, 11. Januar 2018 21:10:51 CET Ben Cooksley wrote: >> On Thu, Jan 11, 2018 at 1:15 PM, Martin Kostolný <clearmar...@zoho.com> > wrote: >> > I'd like to move forward with my

Re: Phabricator: How to get the email address of contributors?

On Wed, Jan 3, 2018 at 11:02 AM, Albert Astals Cid wrote: > El dimarts, 2 de gener de 2018, a les 22:24:13 CET, Luigi Toscano va escriure: >> Dominik Haumann ha scritto: >> > Hi everyone, >> > >> > it just happened to me again, that I want to commit/push a change of >> > someone

Re: Phabricator: How to get the email address of contributors?

On Wed, Jan 3, 2018 at 10:24 AM, Luigi Toscano wrote: > Dominik Haumann ha scritto: >> Hi everyone, >> >> it just happened to me again, that I want to commit/push a change of >> someone else (first-time contributor) with the correct --author="x y >> " data. >> >> But

Re: Phabricator: How to get the email address of contributors?

On Wed, Jan 3, 2018 at 10:15 AM, Dominik Haumann wrote: > Hi everyone, Hi Dominik, > > it just happened to me again, that I want to commit/push a change of > someone else (first-time contributor) with the correct --author="x y > " data. > > But Phabricator hides the email

<    1   2   3   4   5   6   7   8   >