Re: Review of special packager access

2016-07-08 Thread Ben Cooksley
r your distribution of course). The format I mentioned is just one way of doing it. > > Philip Muskovac > Kubuntu Developer Cheers, Ben > > > Am 08.07.2016 um 13:39 schrieb Ben Cooksley: >> >> Hi all, >> >> My apologies if you're not a packager or someone

Re: Review of special packager access

2016-07-08 Thread Ben Cooksley
On Sat, Jul 9, 2016 at 2:32 AM, Nicolas Lécureuil wrote: > Le 2016-07-08 13:39, Ben Cooksley a écrit : >> >> Hi all, >> >> My apologies if you're not a packager or someone associated with a >> distribution - you can ignore this email. Packagers, please

Re: Review of special packager access

2016-07-08 Thread Ben Cooksley
On Sat, Jul 9, 2016 at 2:49 AM, Eric Hameleers wrote: > On Fri, 8 Jul 2016, Ben Cooksley wrote: > >> Hi all, >> >> My apologies if you're not a packager or someone associated with a >> distribution - you can ignore this email. Packagers, please read on as

Re: Review of special packager access

2016-07-08 Thread Ben Cooksley
On Sat, Jul 9, 2016 at 5:07 AM, Michael Palimaka wrote: > Hi Ben, Hi Michael, > > On 08/07/16 21:39, Ben Cooksley wrote: >> I'd therefore like for someone from each distribution to please >> confirm that their distro is still active and who can serve as a >> g

Usage of QNetworkAccessManager

2016-07-13 Thread Ben Cooksley
Hi all, Just my regular reminder regarding usage of QNetworkAccessManager in your applications and libraries, especially when it comes to interacting with kde.org infrastructure. Unfortunately, from it's first iteration in Qt 4 QNetworkAccessManager was shipped with a severe and fundamental defec

Reminder: Please update kde-build-metadata when making changes to repository branch use

2016-07-15 Thread Ben Cooksley
Hi all, Currently there are a series of build breakages on build.kde.org due to out of date build metadata. Just a reminder: before beginning ports of projects from Qt 4 to KF5, you need to: a) Ensure there is a Qt 4 branch (last stable release will do) b) Update kde-build-metadata appropriately

Re: Review of special packager access

2016-07-20 Thread Ben Cooksley
On Wed, Jul 20, 2016 at 4:26 AM, José Manuel Santamaría wrote: > Hello, Hi Jose, > > El viernes, 8 de julio de 2016 23:39:41 (CEST) Ben Cooksley escribió: >> Hi all, >> >> My apologies if you're not a packager or someone associated with a >> distribution

Re: Review of special packager access

2016-07-20 Thread Ben Cooksley
Hi all, Just as a final reminder, i've yet to see responses from: - Active - Aix - Aosc - Asplinux - Crux - Darwin - Magic - Meego - PCLinuxOS - PLD - Redhat (Fedora has responded, this appears to be a duplicate account) - Rpath - Siduction - Tld - Tru64 - Turbo - Uludag - Uoirix - Uomandriva - U

Re: Review of special packager access

2016-07-20 Thread Ben Cooksley
On Wed, Jul 20, 2016 at 7:59 PM, Vadim Zhukov wrote: > 2016-07-20 10:29 GMT+03:00 Ben Cooksley : >> Hi all, >> >> Just as a final reminder, i've yet to see responses from: >> >> - Asplinux > > BTW, ASPLinux is no more. http://distrowatch.com/table.

Re: Can't release applications

2016-07-28 Thread Ben Cooksley
On Thu, Jul 28, 2016 at 10:34 AM, Aleix Pol wrote: > On Wed, Jul 27, 2016 at 12:57 PM, Boudhayan Gupta wrote: >> Hi, >> >> On 27 July 2016 at 16:00, Harald Sitter wrote: >>> On Wed, Jul 27, 2016 at 12:27 PM, Luigi Toscano >>> wrote: On Wednesday, 27 July 2016 12:22:45 CEST Aleix Pol wrote:

Re: Can't release applications

2016-07-29 Thread Ben Cooksley
On Sat, Jul 30, 2016 at 4:57 AM, Aleix Pol wrote: > On Thu, Jul 28, 2016 at 9:25 AM, Ben Cooksley wrote: >> On Thu, Jul 28, 2016 at 10:34 AM, Aleix Pol wrote: >>> On Wed, Jul 27, 2016 at 12:57 PM, Boudhayan Gupta wrote: >>>> Hi, >>>> >>&

Phabricator move and update

2016-09-10 Thread Ben Cooksley
ns (the current 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 l

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

2016-09-21 Thread Ben Cooksley
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

[sysadmin/repo-metadata] projects/kdereview/kwave: Move KWave back to KDE Review.

2016-10-02 Thread Ben Cooksley
Git commit 90fe2e20f10341449620d169430248eff2bc1f63 by Ben Cooksley. Committed on 03/10/2016 at 05:52. Pushed by bcooksley into branch 'master'. Move KWave back to KDE Review. CCMAIL: kde-core-devel@kde.org CCMAIL: kde-de...@kde.org CCMAIL: release-t...@kde.org R +0-0projects

New project moved to review

2016-10-04 Thread Ben Cooksley
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.

2016-10-07 Thread Ben Cooksley
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

Moved to KDE Review: KDb, KReport, KProperty

2016-10-07 Thread Ben Cooksley
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

2016-10-08 Thread Ben Cooksley
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

Re: Dropping kdelibs4-based applications in KDE Applications 17.12

2016-11-14 Thread Ben Cooksley
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: >> >> Hi, my proposal would be to mak

Discontinuing Qt mirror

2016-11-22 Thread Ben Cooksley
the 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, B

Discontinuing repository tarballs

2016-11-22 Thread Ben Cooksley
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

Re: Discontinuing repository tarballs

2016-11-23 Thread Ben Cooksley
On Thu, Nov 24, 2016 at 2:30 PM, Michael Pyne 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 should be maintained going >&g

Please cleanup your scratch and clone repositories

2016-11-25 Thread Ben Cooksley
h/username/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! Re

Re: Discontinuing repository tarballs

2016-11-25 Thread Ben Cooksley
On Thu, Nov 24, 2016 at 8:41 PM, Ben Cooksley wrote: > On Thu, Nov 24, 2016 at 2:30 PM, Michael Pyne 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 >

Re: Please cleanup your scratch and clone repositories

2016-11-27 Thread Ben Cooksley
On Sat, Nov 26, 2016 at 7:53 AM, Ben Cooksley 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 repositories they're no lon

Scheduled downtime: spring.kde.org

2016-12-26 Thread Ben Cooksley
) otherwise any unreceived messages will be lost when ZNC is shutdown as part of the system upgrade. Thanks, Ben Cooksley KDE Sysadmin

Re: Scheduled downtime: spring.kde.org

2016-12-27 Thread Ben Cooksley
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

Replacement of notes.kde.org

2016-12-28 Thread Ben Cooksley
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 shoul

CI Requirements - Lessons Not Learnt?

2017-01-05 Thread Ben Cooksley
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 XKBCo

Re: CI Requirements - Lessons Not Learnt?

2017-01-05 Thread Ben Cooksley
On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin 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 bumps on the CI system have gone completely >

Re: CI Requirements - Lessons Not Learnt?

2017-01-05 Thread Ben Cooksley
On Fri, Jan 6, 2017 at 12:38 AM, Martin Gräßlin wrote: > Am 2017-01-05 11:20, schrieb Ben Cooksley: >> >> On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin >> wrote: >>> >>> Am 2017-01-05 09:44, schrieb Ben Cooksley: >>>> >>>> >>

Re: CI Requirements - Lessons Not Learnt?

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

Re: CI Requirements - Lessons Not Learnt?

2017-01-10 Thread Ben Cooksley
On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin wrote: > > > Am 6. Januar 2017 17:46:30 MEZ schrieb Alexander Neundorf : >>On 2017 M01 6, Fri 22:39:22 CET Ben Cooksley wrote: >>> See my notes above re. why tying this to the dependency freeze date >>is >&g

Re: CI Requirements - Lessons Not Learnt?

2017-01-11 Thread Ben Cooksley
On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin wrote: > > > Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley : >>On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin >>wrote: >>> >>> >>> Am 6. Januar 2017 17:46:30 MEZ schrieb Alexander Neundorf >

Re: CI Requirements - Lessons Not Learnt?

2017-01-11 Thread Ben Cooksley
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 of having a >>> CI. >> >> >> What base system(s)

Re: CI Requirements - Lessons Not Learnt?

2017-01-11 Thread Ben Cooksley
On Thu, Jan 12, 2017 at 4:54 AM, Martin Gräßlin wrote: > Am 2017-01-11 10:46, schrieb Ben Cooksley: >> >> On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin >> wrote: >>> >>> >>> >>> Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley :

Re: CI Requirements - Lessons Not Learnt?

2017-01-12 Thread Ben Cooksley
On Fri, Jan 13, 2017 at 7:39 PM, Martin Gräßlin 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: >>> > It would probably be a

Re: CI Requirements - Lessons Not Learnt?

2017-01-14 Thread Ben Cooksley
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 that reverting the dependency bump in the app

Re: CI Requirements - Lessons Not Learnt?

2017-01-14 Thread Ben Cooksley
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, this draft contains

Re: CI Requirements - Lessons Not Learnt?

2017-01-15 Thread Ben Cooksley
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 de

Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Ben Cooksley
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 interested in.

Phabricator: All repositories registered - upcoming workflow changes

2017-01-28 Thread Ben Cooksley
s replies to this email (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

Communication with Phabricator upstream

2017-02-16 Thread Ben Cooksley
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 y

Phabricator updated

2017-02-18 Thread Ben Cooksley
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. A

Project Releases: Infrastructure Migration

2017-02-21 Thread Ben Cooksley
emove 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

Migration of Download Infrastructure: Please check your applications

2017-02-24 Thread Ben Cooksley
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 nu

[sysadmin/repo-metadata] projects/kde/workspace/plasma-vault: Move Plasma Vault to (Plasma) Workspace

2017-03-06 Thread Ben Cooksley
Git commit b8559f750bfa648ebae4a26882b2a64f07ae3094 by Ben Cooksley. Committed on 07/03/2017 at 06:24. Pushed by bcooksley into branch 'master'. Move Plasma Vault to (Plasma) Workspace Fixes T5335 CCMAIL: release-t...@kde.org CCMAIL: kde-core-devel@kde.org CCMAIL: plasma-de...@kde.

Communication with Phabricator upstream

2017-03-09 Thread Ben Cooksley
communicate on a whole of project basis the things we consider important. This helps simplify things for upstream. Thanks, Ben Cooksley KDE Sysadmin

Re: Review Request 113587: Add support for x-gvfs style options in fstab

2017-03-13 Thread Ben Cooksley
hod to register, AFAICT), > which bars me from adding any comments there ... Anyone with an Identity account can login on Phabricator. > > Kind regards, > > Stefan Regards, Ben Cooksley KDE Sysadmin

[sysadmin/repo-metadata] projects/extragear/utils/usbimagewriter: Rename imagewriter to usbimagewriter, and move it to Extragear/Utils as requested.

2017-04-24 Thread Ben Cooksley
Git commit aa20ad09ba818607b9fe173b5bf97ba8f10c310c by Ben Cooksley. Committed on 24/04/2017 at 20:19. Pushed by bcooksley into branch 'master'. Rename imagewriter to usbimagewriter, and move it to Extragear/Utils as requested. Fixes T5945 CCMAIL: kde-core-devel@kde.org R +0-0

[sysadmin/repo-metadata] projects/kde/pim/kdepim-runtime: Move kdepim-runtime to kde/pim/ in the virtual hierarchy.

2017-04-27 Thread Ben Cooksley
Git commit 01bc4814fa11272f54e6f33f7a3f3e2ae883913c by Ben Cooksley. Committed on 27/04/2017 at 09:59. Pushed by bcooksley into branch 'master'. Move kdepim-runtime to kde/pim/ in the virtual hierarchy. WARNING: All projects which depend on kdepim-runtime on the CI system will be br

[sysadmin/repo-metadata] projects/kde/workspace/plymouth-kcm: Move plymouth-kcm from KDE Review to Plasma Workspace in the virtual hierarchy after it cleared review last year.

2017-04-28 Thread Ben Cooksley
Git commit c52788ab01cf08b359842a44a3213239533d810a by Ben Cooksley. Committed on 28/04/2017 at 19:15. Pushed by bcooksley into branch 'master'. Move plymouth-kcm from KDE Review to Plasma Workspace in the virtual hierarchy after it cleared review last year. Fixes T5967 CCMAIL: kde-

Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

2017-05-06 Thread Ben Cooksley
for all who have reached this point - my apologies again for it's length. Note that the Next Gen system isn't finished yet - Notifications are yet to be setup and there are a few other touches left to be made. Regards, Ben Cooksley KDE Sysadmin

Re: Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

2017-05-06 Thread Ben Cooksley
On Sat, May 6, 2017 at 10:15 PM, Elvis Angelaccio wrote: > On sabato 6 maggio 2017 11:37:51 CEST, Ben Cooksley wrote: >> >> Hi everyone, >> >> This is going to be quite a long email, my apologies in advance for that. >> If you use the CI system regularly as part

Re: Next Gen CI: framework dependencies for KWin

2017-05-12 Thread Ben Cooksley
On Sun, May 7, 2017 at 4:55 AM, Martin Flöser wrote: > Am 2017-05-06 11:37, schrieb Ben Cooksley: >> Hi Martin, >> This is the second point that requires your attention. If your >> development process is dependent on using the latest development >> version of so

Re: Next Gen CI - frameworks requirements for plasma

2017-05-12 Thread Ben Cooksley
On Fri, May 12, 2017 at 11:09 PM, David Edmundson wrote: > Following up from Ben's email where we won't have master of frameworks in > buidling master of Plasma. > >> If this affects you, please start a > new thread (CC'ing sysadmin and kde-core-devel along with your > Product's main list) stating

Re: Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

2017-05-14 Thread Ben Cooksley
On Wed, May 10, 2017 at 2:09 AM, Andrea Scarpino wrote: > On Sat, May 6, 2017 at 11:37 AM, Ben Cooksley wrote: >> Which brings me to the third point of attention. We'll only be adding >> projects to the Next Gen CI system at their request going forward. For >> Framework

Re: Next Gen CI Will Be Moving to Production Shortly: Upcoming Changes

2017-05-15 Thread Ben Cooksley
On Mon, May 15, 2017 at 1:42 PM, Robby Stephenson wrote: > On Sat, May 6, 2017 at 5:37 AM, Ben Cooksley wrote: >> >> Which brings me to the third point of attention. We'll only be adding >> projects to the Next Gen CI system at their request going forward. For >&

[sysadmin/repo-metadata] projects/kdereview/zanshin: Move Zanshin to KDE Review.

2017-06-07 Thread Ben Cooksley
Git commit 866a38766e5c33ef81e9f2434f6d8995bd5f1aea by Ben Cooksley. Committed on 08/06/2017 at 06:29. Pushed by bcooksley into branch 'master'. Move Zanshin to KDE Review. CCMAIL: kde-core-devel@kde.org Fixes T6277 R +0-0projects/kdereview/zanshin/i18n.json [from: projects/

Notice of significant adjustment to KWin

2017-06-09 Thread Ben Cooksley
fixes are lost. Apologies for the inconvenience. Regards, Ben Cooksley KDE Sysadmin lost-commits.log Description: Binary data

[sysadmin/repo-metadata] projects/kdereview/qtcurve: Move QtCurve to KDE Review at request of it's maintainer

2017-06-09 Thread Ben Cooksley
Git commit 8464153d3e7b76c37a3114a9c639c17fc07f6e8e by Ben Cooksley. Committed on 10/06/2017 at 03:36. Pushed by bcooksley into branch 'master'. Move QtCurve to KDE Review at request of it's maintainer CCMAIL: kde-core-devel@kde.org Fixes T6306 R +0-0projects/kdereview/qt

Re: kio-stash is in KDE Review

2017-06-15 Thread Ben Cooksley
On Thu, Jun 15, 2017 at 9:04 AM, Albert Astals Cid wrote: > El dimecres, 14 de juny de 2017, a les 21:42:58 CEST, Arnav Dhamija va > escriure: >> Just to check I setup a brand new virtualbox with KDE Neon 5.8 LTS and >> ran the following commands after cloning the repo and creating a build >> dire

Re: [sysadmin/repo-metadata] projects/kdereview/qtcurve: Move QtCurve to KDE Review at request of it's maintainer

2017-06-15 Thread Ben Cooksley
On Wed, Jun 14, 2017 at 5:46 AM, Albert Astals Cid wrote: > Can you please tell whoever asked for that to send an email here, because i've > seen nothing. I'll do so shortly. > > Cheers, > Albert Regards, Ben > > El dissabte, 10 de juny de 2017, a les 3:36:46

Re: Application usage statistics and targeted user surveys

2017-06-15 Thread Ben Cooksley
On Fri, Jun 16, 2017 at 1:42 AM, Aleix Pol wrote: > On Tue, Jun 13, 2017 at 6:56 PM, Volker Krause wrote: >> On Monday, 12 June 2017 01:56:21 CEST Aleix Pol wrote: >>> On Sat, Jun 10, 2017 at 10:22 AM, Volker Krause wrote: >>> > On Tuesday, 6 June 2017 15:01:57 CEST Aleix Pol wrote: >>> >> On Th

Re: who is authorised to move repos around?

2017-06-22 Thread Ben Cooksley
On Thu, Jun 22, 2017 at 4:14 AM, Jonathan Riddell wrote: > I'm unclear who is authorised to move git repos around, e.g. from > playground to kdereview to kde-extra > > It used to be only sysadmins which seems like a political burden on a tech > team. > > Now anyone can edit repo-metadata. So can

Re: Moving AtCore to Extragear

2017-06-22 Thread Ben Cooksley
nsit KDE Review including the full 2 week process. Jonathan and Lays, please read the documentation as contained in sysadmin/repo-metadata before making any further changes to the repository. > > -- > Luigi > Regards, Ben Cooksley KDE Sysadmin

Re: Moving AtCore to Extragear

2017-06-23 Thread Ben Cooksley
On Fri, Jun 23, 2017 at 10:45 PM, Jonathan Riddell wrote: > On Fri, Jun 23, 2017 at 08:22:39AM +1200, Ben Cooksley wrote: >> On Fri, Jun 23, 2017 at 7:56 AM, Luigi Toscano >> wrote: >> > Albert Astals Cid ha scritto: >> >> El diumenge, 18 de juny de 2017, a

[sysadmin/repo-metadata] projects/kdereview: Move Atelier and AtCore to KDE Review proper.

2017-06-23 Thread Ben Cooksley
Git commit ce94f3398e4abf08bc5620f8ca7cdaccc5f9371f by Ben Cooksley. Committed on 24/06/2017 at 02:05. Pushed by bcooksley into branch 'master'. Move Atelier and AtCore to KDE Review proper. CCMAIL: kde-core-devel@kde.org Fixes T6383 R +0-0projects/kdereview/atcore/i18n.

Re: libqaccessibilityclient now in kdereview

2017-07-25 Thread Ben Cooksley
On Tue, Jul 25, 2017 at 11:25 PM, Jonathan Riddell wrote: > libqaccessibilityclient is now in kdereview. It's in a git repo > called libkdeaccessibilityclient but we filed a sysadmin request to > rename it. That request has since been actioned. > > We just released 0.2.0 in unstable (for some r

Re: libqaccessibilityclient now in kdereview

2017-07-25 Thread Ben Cooksley
On Wed, Jul 26, 2017 at 9:18 AM, Mario Fux wrote: > Am Dienstag, 25. Juli 2017, 14:55:42 CEST schrieb Albert Astals Cid: > > Morning Albert Hi Mario, > >> El dimarts, 25 de juliol de 2017, a les 13:25:39 CEST, Jonathan Riddell va >> >> escriure: >> > libqaccessibilityclient is now in kdereview.

Retirement of Reviewboard - Transition to Phabricator

2017-08-24 Thread Ben Cooksley
Hi all, The following is Sysadmin's suggested plan for the retirement of Reviewboard now that Phabricator is fully up and running for hosting of code reviews. Phase 1: Commences September 2: All repositories are closed for accepting new reviews on Reviewboard. A notice is added to the top of the

Re: Retirement of Reviewboard - Transition to Phabricator

2017-08-24 Thread Ben Cooksley
On 25/08/2017 5:41 AM, "Albert Astals Cid" wrote: El dijous, 24 d’agost de 2017, a les 21:07:49 CEST, Ben Cooksley va escriure: > Hi all, > > The following is Sysadmin's suggested plan for the retirement of > Reviewboard now that Phabricator is fully up and running fo

Re: Retirement of Reviewboard - Transition to Phabricator

2017-08-28 Thread Ben Cooksley
On Mon, Aug 28, 2017 at 8:20 PM, René J.V. Bertin wrote: > On Friday August 25 2017 07:33:43 Ben Cooksley wrote: > > Hi, Hi Rene, > >>> Note that due to how Reviewboard stores diffs and reproduces them for >>> use, some reviews may have decayed and may no longer b

Re: Latte Dock in review phase

2017-10-13 Thread Ben Cooksley
On Fri, Oct 13, 2017 at 11:12 AM, Albert Astals Cid wrote: > El dijous, 5 d’octubre de 2017, a les 0:00:01 CEST, Michail Vourlakos va > escriure: >> Hello everyone, >> >> we decided to make Latte an active kde project and so now it is in review >> phase. I believe the best place to be is extragear

Re: http://commitfilter.kde.org/ ?

2017-10-30 Thread Ben Cooksley
On Mon, Oct 30, 2017 at 6:38 PM, Martin Koller wrote: >> On Sun, Oct 29, 2017 at 9:47 PM, Martin Koller wrote: >> > Should http://commitfilter.kde.org/ still exist ? >> > Currently I get "unknown host" > > On Sonntag, 29. Oktober 2017 22:33:20 CET Harald Sitter wrote: >> See >> >> http://markmail

Re: http://commitfilter.kde.org/ ?

2017-11-02 Thread Ben Cooksley
On Mon, Oct 30, 2017 at 9:11 PM, Elias Probst wrote: > On 10/30/2017 08:38 AM, Ben Cooksley wrote: >> Anyone who is interested in writing and maintaining replacement >> functionality should get in touch with me as mentioned in my previous >> mail in the second link there. &

Significant CI Maintenance

2017-11-10 Thread Ben Cooksley
while the transition is made. Once the builds are fully operational under the SUSE builds, all of the Fedora builds will be removed. My apologies for the inconvenience, particularly given an Applications release has just taken place. Regards, Ben Cooksley KDE Sysadmin

Advance Downtime Notification

2017-11-28 Thread Ben Cooksley
into account potential system unavailability, and where possible reschedule the release outside of the window. Should anyone have any concerns please contact us. Regards, Ben Cooksley KDE Sysadmin

Re: Advance Downtime Notification

2017-12-05 Thread Ben Cooksley
On Wed, Nov 29, 2017 at 8:11 PM, Ben Cooksley wrote: > Hi all, Hi everyone, > > Over the past 24 hours we have received initial warning notifications > that a disk in our bulk storage server has begun to show signs of > failure. We have now begun the process of having thi

Mirror of Qt being discontinued

2017-12-25 Thread Ben Cooksley
e let us know. Cheers, Ben Cooksley KDE Sysadmin

Re: Review Request 130239: Exclude kconf_update from catching by uac on Windows

2017-12-26 Thread Ben Cooksley
> On Dec. 26, 2017, 1:07 p.m., Alexey Min wrote: > > Ship It! > > Ralf Habacker wrote: > got push error > > xxx@yyy:~/src/kdelibs> git push > fatal: remote error: service not enabled: /kdelibs You're trying to push to anongit - Ben -

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

2018-01-02 Thread Ben Cooksley
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 address, so I either ha

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

2018-01-02 Thread Ben Cooksley
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 Phabricator hides the email ad

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

2018-01-02 Thread Ben Cooksley
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 else (first-time c

Re: 2 New Plasmoids in Kdereview

2018-01-11 Thread Ben Cooksley
On Thu, Jan 11, 2018 at 1:15 PM, Martin Kostolný wrote: > Hello! Hi Martin, > > I'd like to move forward with my new plasmoid projects that landed in > kdereview some time ago. > > https://phabricator.kde.org/source/plasma-redshift-control/ > https://phabricator.kde.org/source/plasma-active-win

Re: 2 New Plasmoids in Kdereview

2018-01-13 Thread Ben Cooksley
On Fri, Jan 12, 2018 at 11:18 AM, Ingo Klöcker wrote: > On Donnerstag, 11. Januar 2018 21:10:51 CET Ben Cooksley wrote: >> On Thu, Jan 11, 2018 at 1:15 PM, Martin Kostolný > wrote: >> > I'd like to move forward with my new plasmoid projects that landed in &g

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

2018-01-15 Thread Ben Cooksley
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 solution before a proper appme

Re: 2 New Plasmoids in Kdereview

2018-01-15 Thread Ben Cooksley
s 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, 11 Janua

Re: Rebase of kopete branch and push it to master

2018-01-16 Thread Ben Cooksley
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 much fuss. The proble

Re: Rebase of kopete branch and push it to master

2018-01-16 Thread Ben Cooksley
the push if it clashes with an Applications module release or freeze for which an exception has not been granted. Regards, Ben Cooksley KDE Sysadmin

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

2018-01-17 Thread Ben Cooksley
hat was being uploaded 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 KD

Re: Rebase of kopete branch and push it to master

2018-01-17 Thread Ben Cooksley
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 kde-buil

Re: Rebase of kopete branch and push it to master

2018-01-19 Thread Ben Cooksley
On Fri, Jan 19, 2018 at 12:06 PM, Pali Rohár 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 repository. >&g

Re: Plasma-Mycroft is in kdereview

2018-01-19 Thread Ben Cooksley
ng 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

2018-01-24 Thread Ben Cooksley
On Thu, Jan 25, 2018 at 11:26 AM, Pali Rohár wrote: > On Friday 19 January 2018 21:56:10 Ben Cooksley wrote: >> On Fri, Jan 19, 2018 at 12:06 PM, Pali Rohár wrote: >> > On Thursday 18 January 2018 20:50:35 Ben Cooksley wrote: >> >> Hi all, >> >> >&g

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

2018-01-30 Thread Ben Cooksley
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@

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

2018-02-05 Thread Ben Cooksley
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'

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

2018-02-05 Thread Ben Cooksley
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/

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

2018-02-25 Thread Ben Cooksley
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

CI & Binary Factory maintenance

2018-02-25 Thread Ben Cooksley
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

<    1   2   3   4   5   6   7   8   >