Re: Phabricator: All repositories registered - upcoming workflow changes

On Tue, Jan 31, 2017 at 11:36 PM, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Sunday January 29 2017 08:32:21 Ben Cooksley wrote: > > Hi, Hi Rene, > > >From this point forward, communities should be moving away from >>Reviewboard to Phabricator for co

Re: Phabricator differential is not good - WAS - Re: Phabricator: All repositories registered - upcoming workflow changes

On Mon, Feb 6, 2017 at 8:39 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dilluns, 6 de febrer de 2017, a les 8:18:04 CET, Ben Cooksley va escriure: >> On Sun, Feb 5, 2017 at 6:24 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El dissabte, 4 de febrer de

Re: Phabricator differential is not good - WAS - Re: Phabricator: All repositories registered - upcoming workflow changes

On Sun, Feb 5, 2017 at 6:24 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dissabte, 4 de febrer de 2017, a les 12:44:54 CET, Ben Cooksley va > escriure: >> On Sat, Feb 4, 2017 at 11:41 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El divendres, 3 de febrer

Re: Finding contributor email is imposible - was - Re: Phabricator: All repositories registered - upcoming workflow changes

On Wed, Feb 8, 2017 at 4:03 AM, Fredrik Höglund <fred...@kde.org> wrote: > On Monday 06 February 2017, Albert Astals Cid wrote: >> El diumenge, 29 de gener de 2017, a les 8:32:21 CET, Ben Cooksley va >> escriure: >> > Hi everyone, >> > >> > From

Re: Finding contributor email is imposible - was - Re: Phabricator: All repositories registered - upcoming workflow changes

On Tue, Feb 7, 2017 at 3:30 PM, Michael Pyne <mp...@kde.org> wrote: > On Mon, Feb 06, 2017 at 11:35:15PM +0100, Albert Astals Cid wrote: >> El diumenge, 29 de gener de 2017, a les 8:32:21 CET, Ben Cooksley va >> escriure: >> > Hi everyone, >> > >>

Re: Phabricator differential is not good - WAS - Re: Phabricator: All repositories registered - upcoming workflow changes

On Sat, Feb 4, 2017 at 1:15 PM, Kai Uwe Broulik wrote: >> This is not ok, the web interface for reviewboard was as good as rb-tools (I >> guess tbh i never used them) and "forcing" the use of a weird tool noone has >> heard of is not a good way to attract new

Re: Differential commit log keyword is uncomfortable - WAS - Re: Phabricator: All repositories registered - upcoming workflow changes

On Sun, Feb 5, 2017 at 6:30 AM, Albert Astals Cid <aa...@kde.org> wrote: > El diumenge, 29 de gener de 2017, a les 8:32:21 CET, Ben Cooksley va escriure: >> Hi everyone, >> >> We've just completed the registration of all mainline repositories >> (not including Web

Re: CI trouble

On Sun, Feb 5, 2017 at 8:45 AM, Nicolás Alvarez wrote: > 2017-02-04 16:19 GMT-03:00 David Faure : >> Today the CI seems capricious ;) >> >> - build.kde.org was down for a bit > > Yep, Jenkins ran out of memory in the JVM. Restarted a while ago. > >> - DNS

Re: Phabricator: All repositories registered - upcoming workflow changes

On Thu, Feb 2, 2017 at 11:51 PM, Harald Sitter <sit...@kde.org> wrote: > On Thu, Feb 2, 2017 at 10:31 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> On Thu, Feb 2, 2017 at 10:23 PM, Luigi Toscano <luigi.tosc...@tiscali.it> >> wrote: >>> Il 02.02.2017 10:0

Re: Phabricator: All repositories registered - upcoming workflow changes

On 1/02/2017 10:38 PM, "René J.V. Bertin" <rjvber...@gmail.com> wrote: On Wednesday February 1 2017 22:16:50 Ben Cooksley wrote: >We'd still have to keep the software running, and up to date (to avoid >it becoming a security risk). Running yes, but if log-in i

Re: Phabricator: All repositories registered - upcoming workflow changes

On 2/02/2017 12:41 AM, "Luigi Toscano" wrote: On Wednesday, 1 February 2017 10:31:44 CET Francis Herne wrote: > Sorry, forgot to reply-all and only sent to kdevelop-devel... > > - > > Hi, > > First off, there's a lot of postponed, or at least

Re: Phabricator: All repositories registered - upcoming workflow changes

On Wed, Feb 1, 2017 at 9:48 PM, Milian Wolff <m...@milianw.de> wrote: > On Tuesday, January 31, 2017 7:56:52 PM CET Ben Cooksley wrote: >> On Tue, Jan 31, 2017 at 11:36 PM, René J.V. Bertin <rjvber...@gmail.com> > wrote: >> > On Sunday January 29 2017 08:32:21

Phabricator: All repositories registered - upcoming workflow changes

ail (include sysadmin@ in CC please) or by asking a member of the Community Admins project on Phabricator to make the change for you. Thanks, Ben Cooksley KDE Sysadmin

Phabricator: All repositories registered - upcoming workflow changes

ail (include sysadmin@ in CC please) or by asking a member of the Community Admins project on Phabricator to make the change for you. Thanks, Ben Cooksley KDE Sysadmin

Phabricator: All repositories registered - upcoming workflow changes

ail (include sysadmin@ in CC please) or by asking a member of the Community Admins project on Phabricator to make the change for you. Thanks, Ben Cooksley KDE Sysadmin

Phabricator: All repositories registered - upcoming workflow changes

ail (include sysadmin@ in CC please) or by asking a member of the Community Admins project on Phabricator to make the change for you. Thanks, Ben Cooksley KDE Sysadmin

Re: Screenshot hosting repo (e.g. for Appstream)

On Sun, Jan 22, 2017 at 8:08 AM, Elvis Angelaccio wrote: > On Tue, Nov 29, 2016 at 9:55 AM, Harald Sitter wrote: >> Hey, >> >> We have just finished sorting out a centralized screenshot repo. This >> repo should be used for promotional screenshots of KDE

Project Releases: Infrastructure Migration

files to those trees - which means projects will not be able to make releases. To the knowledge of Sysadmin, this does not affect the release of any project, however anyone who had plans should please contact us immediately. Regards, Ben Cooksley KDE Sysadmin

Project Releases: Infrastructure Migration

files to those trees - which means projects will not be able to make releases. To the knowledge of Sysadmin, this does not affect the release of any project, however anyone who had plans should please contact us immediately. Regards, Ben Cooksley KDE Sysadmin

Phabricator updated

Hi all, Over the weekend we've updated our Phabricator instance to the latest stable version. This has brought in a few changes which you may wish to check out - including the ability to customise the global home menu and setup a favourites menu for yourself to access frequently used functions.

Migration of Download Infrastructure: Please check your applications

Hi all, Sysadmin have now completed the migration of our file distribution systems, download.kde.org and files.kde.org, to a new server. During this migration we also enabled mandatory https for both. Because QNetworkAccessManager does not follow redirects by default (at least in a significant

Migration of Download Infrastructure: Please check your applications

Hi all, Sysadmin have now completed the migration of our file distribution systems, download.kde.org and files.kde.org, to a new server. During this migration we also enabled mandatory https for both. Because QNetworkAccessManager does not follow redirects by default (at least in a significant

Migration of Download Infrastructure: Please check your applications

Hi all, Sysadmin have now completed the migration of our file distribution systems, download.kde.org and files.kde.org, to a new server. During this migration we also enabled mandatory https for both. Because QNetworkAccessManager does not follow redirects by default (at least in a significant

Communication with Phabricator upstream

Hi all, To help simplify things for Phabricator upstream, they've asked that only a couple of people bring things to their attention (including filing tasks). This helps them with figuring out our priorities as a project in regards to usage of Phabricator. Please therefore file all issues / etc

Communication with Phabricator upstream

Hi all, To help simplify things for Phabricator upstream, they've asked that only a couple of people bring things to their attention (including filing tasks). This helps them with figuring out our priorities as a project in regards to usage of Phabricator. Please therefore file all issues / etc

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 19, 2017 at 6:29 AM, Eike Hein wrote: > > > On 01/17/2017 11:46 PM, Adriaan de Groot wrote: >> But CI has a really important function: it shows us the health of the sources >> for everything; and that's something the release team needs, and the whole >> community can be

[Differential] [Updated] D4201: Make it possible to lower KCrash to tier 1

bcooksley updated the test plan for this revision. REPOSITORY R285 KCrash REVISION DETAIL https://phabricator.kde.org/D4201 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: apol, #frameworks, dfaure Cc: anthonyfieroni, graesslin

[sysadmin/ci-master-config] /: Revert "Disable new_delete_type_mismatch ASAN checks, due to defective Qt code."

Git commit 74fecfd9f4dd09e21531cc5378d2f8dd55b0df35 by Ben Cooksley. Committed on 16/08/2016 at 00:41. Pushed by bcooksley into branch 'master'. Revert "Disable new_delete_type_mismatch ASAN checks, due to defective Qt code." This reverts commit 8bdb20f0189da74e9875be45822e7f9aa872543

Re: Re-enable new_delete_type_mismatch in ASAN?

On Tue, Aug 16, 2016 at 9:34 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dijous, 4 d’agost de 2016, a les 19:40:14 CEST, Ben Cooksley va escriure: >> On Thu, Aug 4, 2016 at 9:52 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > We disabled the new_delete_type_m

Re: Differential e-mail subject re-arrangement

On Thu, Mar 2, 2017 at 10:08 AM, Dominik Haumann wrote: > Hi, Hi all, > > On Wed, Mar 1, 2017 at 4:16 PM, David Faure wrote: >> On mercredi 1 mars 2017 13:35:47 CET Kevin Funk wrote: >>> On Tuesday, 28 February 2017 21:31:44 CET Michael Pyne wrote: >>> > On

Re: Various CI build failures

On Thu, Sep 1, 2016 at 10:57 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dimecres, 31 d’agost de 2016, a les 20:48:31 CEST, Ben Cooksley va > escriure: >> On Wed, Aug 31, 2016 at 9:15 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El dimarts, 30 d’agost

Re: Various CI build failures

On Wed, Aug 31, 2016 at 11:49 PM, Michael Palimaka <kensing...@gentoo.org> wrote: > On 30/08/16 19:52, Ben Cooksley wrote: >> Additionally, would anyone mind if CI coverage were dropped for the >> following: >> >> - libechonest Qt 5 branches > > I can

Re: Various CI build failures

On Wed, Aug 31, 2016 at 9:15 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dimarts, 30 d’agost de 2016, a les 21:52:58 CEST, Ben Cooksley va escriure: >> Hi all, >> >> The following projects currently fail to build on the CI system - can >> the respective

Various CI build failures

Hi all, The following projects currently fail to build on the CI system - can the respective devels please investigate and fix? - GCompris: Tries to use a CMake feature which the version on the CI system does not support. Please restore compatibility with earlier CMake versions (the CI system is

Re: Outstanding umbrello tarball move request

On Tue, Aug 30, 2016 at 4:22 PM, Ralf Habacker wrote: > Hi, Hi Ralf, > > a few weeks ago, KDE sysadmin requests has been switched to > phabricator. After that I filed a tar ball move request for umbrello > for windows 2.19.3 release (https://phabricator.kde.org/T3391)

Re: Various CI build failures

On Tue, Aug 30, 2016 at 9:56 PM, Bhushan Shah <bhus...@gmail.com> wrote: > Hello Ben, > > On Tue, Aug 30, 2016 at 3:22 PM, Ben Cooksley <bcooks...@kde.org> wrote: >> - Plasma Mediacenter Qt 4 branches > > I am fine with this. Thanks, i've now actioned it

Phabricator move and update

upstream default) and will probably reset everyone's preferences in this matter to ensure it doesn't happen again. Our apologies for any inconvenience caused by the migration or update. If you experience any issues or problems with Phabricator post migration, please let us know. Regards, Ben

Re: Wanted To Contribute In KDE

Hi Lydia, Rishi had earlier emailed me/Sysadmin and as part of that I sent him some information on a task we'd like to accomplish as part of our Phabricator migration. I've yet to hear back how things are going though. Cheers, Ben

Re: kdereview

On Fri, Sep 30, 2016 at 11:27 AM, Albert Astals Cid wrote: > El dimecres, 21 de setembre de 2016, a les 11:01:18 CEST, Allen Winter va > escriure: >> kwave is now moved to kdemultimedia. > > Why did that happen? It was moved at the request of it's maintainer and Allen. > > Did i

New project moved to review

Hi all, At the request of Elvis Angelaccio sysadmin has moved kio-gdrive to KDE Review. Regards, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/kdereview: Move kdb, kreport and kproperty to KDE Review as requested.

Git commit fe1e155a099a56b44f216190c8bd6c2353631e95 by Ben Cooksley. Committed on 07/10/2016 at 18:46. Pushed by bcooksley into branch 'master'. Move kdb, kreport and kproperty to KDE Review as requested. CCMAIL: kde-core-devel@kde.org Fixes T3957 R +0-0projects/kdereview/kdb/i18n.json

Moved to KDE Review: KDb, KReport, KProperty

Hi all, Just a heads up that at the request of Jaroslaw Staniek, Sysadmin has moved the following repositories to KDE Review: - KDb (kdb) - KReport (kreport) - KProperty (kproperty) >From my understanding these are used as part of Kexi. Regards, Ben

ECM Breakage: Compilation failure for GCC

Hi all, It appears that commit 4b8e8dcc8856d8f438860783e7641d02d1c05630 to ECM broke the whole CI system for all Qt 5 / Frameworks builds. I've therefore reverted it. Regards, Ben Cooksley KDE Sysadmin

ECM Breakage: Compilation failure for GCC

Hi all, It appears that commit 4b8e8dcc8856d8f438860783e7641d02d1c05630 to ECM broke the whole CI system for all Qt 5 / Frameworks builds. I've therefore reverted it. Regards, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/kde/kdemultimedia/kwave: Move KWave to kde/kdemultimedia as requested.

Git commit 40d2107dbe1a958a58bbcb314ab30c42e2b28e05 by Ben Cooksley. Committed on 21/09/2016 at 08:34. Pushed by bcooksley into branch 'master'. Move KWave to kde/kdemultimedia as requested. CCMAIL: release-t...@kde.org CCMAIL: kde-core-devel@kde.org CCMAIL: thomas.eschenbac...@gmx.de CCMAIL

Re: KDE.org Modernization

On Wed, Sep 28, 2016 at 3:00 AM, aayush arora wrote: > Hi all, Hi Lays, Aayush, > Thanks, Lays Rodrigues. > I am Aayush Arora, I am doing front-end development from past three years. > I have worked with Fossasia as a Google Summer of Code student this year. I >

Re: kdereview

On Wed, Sep 28, 2016 at 9:06 AM, Allen Winter wrote: > On Tuesday, September 27, 2016 09:20:32 PM Burkhard Lück wrote: >> Am Mittwoch, 21. September 2016, 11:01:18 CEST schrieb Allen Winter: >> > I suggest we remove bodega-client, kdev-perforce, kdots, kor and kpeg from >> >

Re: kdereview

On Sat, Oct 1, 2016 at 10:49 AM, Albert Astals Cid <aa...@kde.org> wrote: > El divendres, 30 de setembre de 2016, a les 21:17:56 CEST, Ben Cooksley va > escriure: >> On Fri, Sep 30, 2016 at 11:27 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El dimecres, 21 de

Re: Bugzilla Update: Antispam modification deployed

On Thu, Oct 27, 2016 at 3:52 AM, Marco Martin <notm...@gmail.com> wrote: > On Wed, Oct 26, 2016 at 9:42 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> Hi all, >> >> As some of you will already be aware, Bugzilla has recently been >> experiencing some issues

Bugzilla upgraded

Hi all, The production instance of bugs.kde.org has now been upgraded with the latest Bugzilla. Thanks to everyone who tested the instance at bugstest.kde.org. If there are any issues, please let one of us know. Regards, Ben Cooksley KDE Sysadmin

Re: Dropping kdelibs4-based applications in KDE Applications 17.12

On Tue, Nov 15, 2016 at 11:27 AM, Albert Astals Cid wrote: > El divendres, 11 de novembre de 2016, a les 18:24:42 CET, Christoph Feck va > escriure: >> On 11.11.2016 16:45, Dominik Haumann wrote: >> > On Thu, Nov 10, 2016 at 11:42 PM, Albert Astals Cid wrote: >> >>

Re: Dropping kdelibs4-based applications in KDE Applications 17.12

On Tue, Nov 15, 2016 at 11:27 AM, Albert Astals Cid wrote: > El divendres, 11 de novembre de 2016, a les 18:24:42 CET, Christoph Feck va > escriure: >> On 11.11.2016 16:45, Dominik Haumann wrote: >> > On Thu, Nov 10, 2016 at 11:42 PM, Albert Astals Cid wrote: >> >>

Discontinuing Qt mirror

- in part because Phabricator does not support directories for repositories, and requires everything be at top level. This is a distinction which is totally incompatible with Qt's tooling if my understanding is correct. If anyone has any objection please let us know. Regards, Ben Cooksley KDE

Discontinuing repository tarballs

and maintenance complexity involved to operate an anongit mirror, as well as reducing load on the main git.kde.org server which generates the tarballs. If anyone has any objection please let us know. Regards, Ben Cooksley KDE Sysadmin

Please cleanup your scratch and clone repositories

/reponame ssh g...@git.kde.org D rm scratch/username/reponame Please note that the trailing .git should not be included, otherwise the system will not accept your request. You can substitute scratch/... for clones/... as appropriate here. Thanks in advance for removing unused repos! Regards, Ben

Re: Discontinuing repository tarballs

On Thu, Nov 24, 2016 at 8:41 PM, Ben Cooksley <bcooks...@kde.org> wrote: > On Thu, Nov 24, 2016 at 2:30 PM, Michael Pyne <mp...@purinchu.net> wrote: >> On Wed, Nov 23, 2016 at 08:17:29PM +1300, Ben Cooksley wrote: >>> HI all, >>> >>> As of late Sy

Please cleanup your scratch and clone repositories

/reponame ssh g...@git.kde.org D rm scratch/username/reponame Please note that the trailing .git should not be included, otherwise the system will not accept your request. You can substitute scratch/... for clones/... as appropriate here. Thanks in advance for removing unused repos! Regards, Ben

Please cleanup your scratch and clone repositories

/reponame ssh g...@git.kde.org D rm scratch/username/reponame Please note that the trailing .git should not be included, otherwise the system will not accept your request. You can substitute scratch/... for clones/... as appropriate here. Thanks in advance for removing unused repos! Regards, Ben

Re: api.kde.org not generated

On Sat, Nov 26, 2016 at 10:51 AM, Olivier Churlaud wrote: > Hi, Hi Oliver, > > I just realized that api.kde.org was not generated since the 18th (one week). > I just wanted to say that it is known and currently under investigation. I'll > fix this as soon as I can (before

Re: Discontinuing repository tarballs

On Thu, Nov 24, 2016 at 2:30 PM, Michael Pyne <mp...@purinchu.net> wrote: > On Wed, Nov 23, 2016 at 08:17:29PM +1300, Ben Cooksley wrote: >> HI all, >> >> As of late Sysadmin has been assessing what components of our >> infrastructure are in active use and shou

Bugzilla Update: Antispam modification deployed

were previously affecting us. If you see any instances of legitimate comments being blocked, please let us know. Regards, Ben Cooksley KDE Sysadmin

Re: Please cleanup your scratch and clone repositories

On Sat, Nov 26, 2016 at 7:53 AM, Ben Cooksley <bcooks...@kde.org> wrote: > Hi all, Hi all, > > To help Sysadmin assess how these types of repositories would be used > under Phabricator, it would be appreciated if everyone could please > cleanup the scratch and clone

Re: Please cleanup your scratch and clone repositories

On Sat, Nov 26, 2016 at 7:53 AM, Ben Cooksley <bcooks...@kde.org> wrote: > Hi all, Hi all, > > To help Sysadmin assess how these types of repositories would be used > under Phabricator, it would be appreciated if everyone could please > cleanup the scratch and clone

Re: Please cleanup your scratch and clone repositories

On Sat, Nov 26, 2016 at 7:53 AM, Ben Cooksley <bcooks...@kde.org> wrote: > Hi all, Hi all, > > To help Sysadmin assess how these types of repositories would be used > under Phabricator, it would be appreciated if everyone could please > cleanup the scratch and clone

Re: Jenkins-kde-ci: frameworkintegration master stable-kf5-qt5 » Linux,gcc - Build # 334 - Still Failing!

On Fri, Dec 16, 2016 at 3:46 AM, Aleix Pol <aleix...@kde.org> wrote: > On Thu, Dec 15, 2016 at 7:19 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> >> On Thu, Dec 15, 2016 at 7:16 PM, <no-re...@kde.org> wrote: >> > >> > GENERAL INFO

Re: Jenkins-kde-ci: frameworkintegration master stable-kf5-qt5 » Linux,gcc - Build # 334 - Still Failing!

On Thu, Dec 15, 2016 at 7:16 PM, wrote: > > GENERAL INFO > > BUILD FAILURE > Build URL: > https://build.kde.org/job/frameworkintegration%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/334/ > Project: PLATFORM=Linux,compiler=gcc > Date of build: Thu, 15 Dec 2016 06:14:40

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 12, 2017 at 3:23 AM, Scarlett Clark wrote: > > > On Wed, Jan 11, 2017 at 4:40 AM, Jan Kundrát wrote: >> >> On středa 11. ledna 2017 6:57:50 CET, Martin Gräßlin wrote: >>> >>> That doesn't work. Such inflexibility take away the advantage

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 12, 2017 at 4:54 AM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-11 10:46, schrieb Ben Cooksley: >> >> On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin <mgraess...@kde.org> >> wrote: >>> >>> >>> >>> Am

Re: CI Requirements - Lessons Not Learnt?

On Sat, Jan 14, 2017 at 11:42 PM, Kai-Uwe wrote: > Am 14.01.2017 um 08:29 schrieb Martin Gräßlin: >> Am 14. Januar 2017 00:58:55 MEZ schrieb Kevin Kofler >> : >>> The common case is that the new library version is used for an API >>> addition, >>> and

Re: CI Requirements - Lessons Not Learnt?

On Sat, Jan 14, 2017 at 5:23 AM, Martin Gräßlin wrote: > Am 2017-01-13 13:21, schrieb Eike Hein: >> >> Ok, here we go. My draft of a formal policy for dep changes and the CI: >> >> https://community.kde.org/Policies/Dependency_Changes_and_CI >> >> Compared to my earlier email,

Re: CI Requirements - Lessons Not Learnt?

On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin <mgraess...@kde.org> wrote: > > > Am 6. Januar 2017 17:46:30 MEZ schrieb Alexander Neundorf <neund...@kde.org>: >>On 2017 M01 6, Fri 22:39:22 CET Ben Cooksley wrote: >>> See my notes above re. why tyin

Re: CI Requirements - Lessons Not Learnt?

On Fri, Jan 13, 2017 at 7:39 PM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-13 03:10, schrieb Michael Pyne: >> >> On Thu, Jan 12, 2017 at 05:02:40PM +0100, Martin Gräßlin wrote: >>> >>> Am 2017-01-12 08:32, schrieb Ben Cooksley: >>>

Re: CI Requirements - Lessons Not Learnt?

On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin <mgraess...@kde.org> wrote: > > > Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley <bcooks...@kde.org>: >>On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin <mgraess...@kde.org> >>wrote: >>> >>

[sysadmin/repo-metadata] projects/frameworks/prison: Move Prison to Frameworks.

Git commit 53be28ae533973c04e381b314e4030af4157427e by Ben Cooksley. Committed on 03/12/2016 at 10:40. Pushed by bcooksley into branch 'master'. Move Prison to Frameworks. Last minute moves just before a release aren't ideal... CCMAIL: release-t...@kde.org CCMAIL: kde-frameworks-devel@kde.org Ref

Re: CI Requirements - Lessons Not Learnt?

On Fri, Jan 6, 2017 at 9:52 PM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-06 05:57, schrieb Ben Cooksley: >> >> On Fri, Jan 6, 2017 at 12:38 AM, Martin Gräßlin <mgraess...@kde.org> >> wrote: >>> >>> Am 2017-01-05 11:20, schrieb Ben

Re: CI Requirements - Lessons Not Learnt?

On Fri, Jan 6, 2017 at 9:52 PM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-06 05:57, schrieb Ben Cooksley: >> >> On Fri, Jan 6, 2017 at 12:38 AM, Martin Gräßlin <mgraess...@kde.org> >> wrote: >>> >>> Am 2017-01-05 11:20, schrieb Ben

Replacement of notes.kde.org

Hi all, Sysadmin is currently in the process of testing and evaluating Collabora Online (CODE) as a replacement for notes.kde.org. We've enabled this on share.kde.org. It would be appreciated if people please test it out - anyone who is a Developer, member of the e.V, or Visual Design Group

Replacement of notes.kde.org

Hi all, Sysadmin is currently in the process of testing and evaluating Collabora Online (CODE) as a replacement for notes.kde.org. We've enabled this on share.kde.org. It would be appreciated if people please test it out - anyone who is a Developer, member of the e.V, or Visual Design Group

CI Requirements - Lessons Not Learnt?

Hi all, It seems that my previous vocal complaints about system level / serious impact dependency bumps on the CI system have gone completely unnoticed by (some) members of our Community. This was demonstrated earlier this week when components of Plasma bumped their version requirements for

CI Requirements - Lessons Not Learnt?

Hi all, It seems that my previous vocal complaints about system level / serious impact dependency bumps on the CI system have gone completely unnoticed by (some) members of our Community. This was demonstrated earlier this week when components of Plasma bumped their version requirements for

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin <pri...@martin-graesslin.com> wrote: > Am 2017-01-05 09:44, schrieb Ben Cooksley: >> >> Hi all, >> >> It seems that my previous vocal complaints about system level / >> serious impact dependency bump

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin <pri...@martin-graesslin.com> wrote: > Am 2017-01-05 09:44, schrieb Ben Cooksley: >> >> Hi all, >> >> It seems that my previous vocal complaints about system level / >> serious impact dependency bump

Re: CI Requirements - Lessons Not Learnt?

On Fri, Jan 6, 2017 at 12:38 AM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-05 11:20, schrieb Ben Cooksley: >> >> On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin >> <pri...@martin-graesslin.com> wrote: >>> >>> Am 2017-01-05

Re: CI Requirements - Lessons Not Learnt?

On Fri, Jan 6, 2017 at 12:38 AM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-01-05 11:20, schrieb Ben Cooksley: >> >> On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin >> <pri...@martin-graesslin.com> wrote: >>> >>> Am 2017-01-05

Re: Scheduled downtime: spring.kde.org

Hi all, The system upgrade has now been completed - all of the previously mentioned services should now be back online. Please let us know if you find anything which is not functioning correctly. Thanks, Ben

Re: Scheduled downtime: spring.kde.org

Hi all, The system upgrade has now been completed - all of the previously mentioned services should now be back online. Please let us know if you find anything which is not functioning correctly. Thanks, Ben

Re: Scheduled downtime: spring.kde.org

Hi all, The system upgrade has now been completed - all of the previously mentioned services should now be back online. Please let us know if you find anything which is not functioning correctly. Thanks, Ben

Scheduled downtime: spring.kde.org

unreceived messages will be lost when ZNC is shutdown as part of the system upgrade. Thanks, Ben Cooksley KDE Sysadmin

Scheduled downtime: spring.kde.org

unreceived messages will be lost when ZNC is shutdown as part of the system upgrade. Thanks, Ben Cooksley KDE Sysadmin

Re: All Frameworks modules are now available as repositories on Phabricator

On Wed, Dec 28, 2016 at 8:56 AM, Luigi Toscano wrote: > Elvis Angelaccio ha scritto: >> On Mon, Dec 26, 2016 at 1:19 AM, Luigi Toscano >> wrote: >>> ... so that it's easier to use Differential for reviews. >> >> Thanks! >> What about tasks?

Re: CI Requirements - Lessons Not Learnt?

Hi all, Can we please keep this thread on-topic. For the record, going off topic means: a) Mentioning anything about distro patching b) Mentioning anything about ifdefs. All the above is serving to do is inflame things, and divert from the current topic of this thread which is to sort out the

Re: How am i supposed to use arc? - was - Re: Phabricator: All repositories registered - upcoming workflow changes

admin and Community Working Groups >> >>> +49 151 71032970 >> >>> >> >>> On 26 March 2017 at 18:33, Albert Astals Cid <aa...@kde.org> wrote: >> >>>> El diumenge, 29 de gener de 2017, a les 8:32:21 CEST, Ben Cooksley va >>

D5178: QtCurve/Qt5 : further KF5 adaptation

bcooksley added a comment. We won't be modifying Phabricator, in part because Arcanist as shipped by upstream is designed to work with that text. Modifying it will create maintenance burden in the long run and lead to incompatibility with the software which runs on developers systems -

Threadweaver compilation failure: Windows

Hi all, If someone could take a look at the following build log that would be appreciated: https://paste.kde.org/pzyhxydjw/xxx39x/raw Cheers, Ben

Re: KAuth buildability: new CI architecture

On Mon, Apr 17, 2017 at 12:48 AM, Martin Gräßlin <mgraess...@kde.org> wrote: > Am 2017-04-16 13:52, schrieb Ben Cooksley: >> >> On Sun, Apr 16, 2017 at 11:09 PM, Harald Sitter <sit...@kde.org> wrote: >>> >>> Not particularly related to the issue at ha

Re: Threadweaver compilation failure: Windows

2db5ef.png ) Okay. Could you try building with these arguments to CMake and see what happens? -DCMAKE_BUILD_TYPE=Debug -DECM_ENABLE_SANITIZERS='address' -DBUILD_TESTING=ON Thanks, Ben > > 2017-04-20 15:31 GMT+05:00 Ben Cooksley <bcooks...@kde.org>: >> On Wed, Apr 19, 2017 at 7:24

Re: Threadweaver compilation failure: Windows

t;Use default native compilers" > > and full build log https://paste.kde.org/pvhyt3xxo > Cheers, Ben > > 2017-04-18 14:37 GMT+05:00 Ben Cooksley <bcooks...@kde.org>: >> On Tue, Apr 18, 2017 at 6:53 PM, Kevin Funk <kf...@kde.org> wrote: >>>

KAuth buildability: new CI architecture

Hi all, As some will be aware i've been working on a new architecture for the CI system which will solve a number of the problems we currently have with the current iteration. The new design should allow us to: 1) Use different base systems for different groupings of projects 2) Will eliminate

Re: KAuth buildability: new CI architecture

On Sun, Apr 16, 2017 at 11:09 PM, Harald Sitter wrote: > Not particularly related to the issue at hand (which is probably > polkitqt having meh cmake files), but relocating stuff in general is > sper unreliable and I would absolutely advise against it as it can > easily screw

Re: Threadweaver compilation failure: Windows

tps://paste.kde.org/p8wj1dqzf >> Looks like a problem in STL header with debug iterator? Compiler >> unable to find proper overload... >> >> 2017-04-20 16:03 GMT+05:00 Ben Cooksley <bcooks...@kde.org>: >>> >>> Okay. Could you try building with th

<    3   4   5   6   7   8   9   10   11   12   >