Re: Build and test failures with Qt 5.6 and Qt 5.3

On Saturday 07 November 2015 21:42:33 Jan Kundrát wrote: > Hi David, > thanks for looking into this. I'm happy that you find the additional > coverage useful. At this time, the infrastructure cannot easily send out > automated e-mails only upon a change in the state of a build job -- if >

[mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

Hi, I have some questions related to where KF5 expects its configuration files and other local stuff, how KF5 and KDE4 applications cohabit (or not) in that aspect, etc. Some of these are inspired by the fact that I have noticed several weird issues on my Kubuntu KDE4.14 desktop after having

Re: Review Request 121861: Remove obsolate class KFileSystemWatcher, which is handled by Windows implementation of Qt5 QFileSystemWatcher.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121861/#review88156 --- Why was this re-opened? It was committed, AFAICS. - David

Jenkins-kde-ci: kxmlgui master kf5-qt5 » Linux,gcc - Build # 35 - Fixed!

GENERAL INFO BUILD SUCCESS Build URL: https://build.kde.org/job/kxmlgui%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/35/ Project: PLATFORM=Linux,compiler=gcc Date of build: Sun, 08 Nov 2015 10:34:48 + Build duration: 1 min 42 sec CHANGE SET No changes JUNIT RESULTS Name:

Jenkins-kde-ci: kxmlgui master kf5-qt5 » Linux,gcc - Build # 35 - Fixed!

GENERAL INFO BUILD SUCCESS Build URL: https://build.kde.org/job/kxmlgui%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/35/ Project: PLATFORM=Linux,compiler=gcc Date of build: Sun, 08 Nov 2015 10:34:48 + Build duration: 1 min 42 sec CHANGE SET No changes JUNIT RESULTS Name:

Re: Private Qml pugin for Baloo

On Wednesday 19 August 2015 16:03:34 Pinak Ahuja wrote: > I am planning to add a baloo-monitor model to baloo's Qml plugin. The > problem is that we cannot guarantee API stability right now. Is exporting a > new plugin under the namespace org.kde.baloo.experimental acceptable or is > there some

Re: [mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

David Faure wrote: Thanks, David, > It will be for sure, since KF5 doesn't use ~/.kde at all anymore. > It uses what QSP returns for GenericConfigLocation. > > So on Linux it uses ~/.config (or $XDG_CONFIG_HOME if set) > and ~/.local (or $XDG_DATA_HOME if set). I suppose it's left to

Re: Review Request 124147: Create Data Dir If it Does Not Exist

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124147/#review88157 --- Ship it! sorry about the delay, this fell through the

Jenkins-kde-ci: plasma-framework master stable-kf5-qt5 » Linux,All,gcc - Build # 133 - Still Unstable!

GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/plasma-framework%20master%20stable-kf5-qt5/PLATFORM=Linux,Variation=All,compiler=gcc/133/ Project: PLATFORM=Linux,Variation=All,compiler=gcc Date of build: Sun, 08 Nov 2015 11:20:33 + Build duration: 2 min 43 sec CHANGE SET

Splitting KActivities, 2nd attempt...

Hi everybody, We have a few problems at the moment because all the activities components are in a single repository. Sometimes dependencies of the service creep up into the library, builds break because components that are meant only for Plasma start requiring Qt versions that Plasma require,

Re: [mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

On Sunday 08 November 2015 13:11:56 René J.V. Bertin wrote: > > - Both on OS X (MacPorts) and in my Linux packaging, I'd want my ~/.kf5 (to > give it a name) to be independent from KDE4's ~/.kde It will be for sure, since KF5 doesn't use ~/.kde at all anymore. It uses what QSP returns for

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Saturday 07 November 2015 12:55:45 Ivan Čukić wrote: > For how long are we going to support [Qt] 5.3? Good question. So that we don't need to reopen this discussion regularly, I would like to suggest a general rule/policy: We will always support the last 3 Qt x.y releases. Right now that

Re: Build and test failures with Qt 5.6 and Qt 5.3

>> For how long are we going to support [Qt] 5.3? > > Good question. > > So that we don't need to reopen this discussion regularly, I would like to > suggest a general rule/policy: > > We will always support the last 3 Qt x.y releases. > > Right now that means 5.3 + 5.4 + 5.5. > > When 5.6 is out,

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Sunday, 8 November 2015 12:17:19 CET, David Faure wrote: Any chance you could do some debugging around there? I'm afraid I don't have time and motivation to fix this, sorry. I'll be happy to spin a VM with an identical setup for you, though, if you're OK with IPv6-only access. If so,

Jenkins-kde-ci: plasma-framework master kf5-qt5 » Linux,All,gcc - Build # 124 - Still Unstable!

GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/plasma-framework%20master%20kf5-qt5/PLATFORM=Linux,Variation=All,compiler=gcc/124/ Project: PLATFORM=Linux,Variation=All,compiler=gcc Date of build: Sun, 08 Nov 2015 11:20:33 + Build duration: 2 min 38 sec CHANGE SET Revision

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Saturday, 7 November 2015 11:59:48 CET, David Faure wrote: Having this for all of KF5 would definitely be useful. And it's done now: http://ci-logs.kde.flaska.net/matrix.html - [5.3] ballo, missing QList::join - [5.3] knewstuff, QTimer::singleShot and new slots - [5.3] modemmanager-qt,

Jenkins-kde-ci: kxmlgui master stable-kf5-qt5 » Linux,gcc - Build # 33 - Fixed!

GENERAL INFO BUILD SUCCESS Build URL: https://build.kde.org/job/kxmlgui%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/33/ Project: PLATFORM=Linux,compiler=gcc Date of build: Sun, 08 Nov 2015 10:42:08 + Build duration: 2 min 7 sec CHANGE SET No changes JUNIT RESULTS Name:

Jenkins-kde-ci: kxmlgui master stable-kf5-qt5 » Linux,gcc - Build # 33 - Fixed!

GENERAL INFO BUILD SUCCESS Build URL: https://build.kde.org/job/kxmlgui%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/33/ Project: PLATFORM=Linux,compiler=gcc Date of build: Sun, 08 Nov 2015 10:42:08 + Build duration: 2 min 7 sec CHANGE SET No changes JUNIT RESULTS Name:

Re: Review Request 124714: Add support to qmake's options to api.kde.org

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124714/ --- (Updated Nov. 8, 2015, 9:40 p.m.) Status -- This change has been

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: > On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > > Hi all, > > > > It appears the test running with the binary name of "threadtest" in > > kio has a grave bug which can lead to it entering into an infinite > >

Re: kf5 frameworks autotest alters KDE4 desktop workspace settings?!

On 2015-11-06 10:34, René J.V. Bertin wrote: Hi, I've been building KF5 frameworks to install under /opt/local on a KUbuntu 14.04 host running a KDE4 desktop, using the same packaging scripts I'm developing for Mac OS X (MacPorts; evidently with some modifications for using them on Linux). I'm

Re: [mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

On Sunday November 08 2015 18:25:25 David Faure wrote: > Don't even think about it. What, I'm not allowed to scare myself? :) > But you can of course export a different value for > XDG_CONFIG_HOME or XDG_DATA_HOME. A bit difficult to do that only for KF5 applications, eh? Except maybe through

rocs fails to compile? - was -Re: KDE Applications 15.08.3 available for packagers

El Friday 06 November 2015, a les 18:08:57, Albert Astals Cid va escriure: > Tarballs at the usual location. Does anybody have problems building rocs? It builds fine here but CI complains

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Sunday 08 November 2015 15:06:51 Jan Kundrát wrote: > >> [root@ci-el7-a-4 ~]# grep -c opendocument /usr/share/mime/subclasses > >> 0 > >> [root@ci-el7-a-4 ~]# rpm -qf /usr/share/mime/subclasses > >> shared-mime-info-1.1-7.el7.x86_64 OK, clearly CentOS patches the application/zip inheritance

Re: Review Request 124714: Add support to qmake's options to api.kde.org

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124714/#review88165 --- Ship it! Ship It! - Alex Merry On Nov. 8, 2015, 1:21

Re: [mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

On Sunday 08 November 2015 19:02:38 René J.V. Bertin wrote: > On Sunday November 08 2015 18:25:25 David Faure wrote: > > But you can of course export a different value for > > XDG_CONFIG_HOME or XDG_DATA_HOME. > > A bit difficult to do that only for KF5 applications, eh? Not really. I do

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-07 7:23 GMT-03:00 David Faure : > On Saturday 07 November 2015 10:36:18 David Faure wrote: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in >> > kio has a grave bug which

Re: [mostly OS X]: KDEHOME vs. ~/.kde best practices, *rc files and related questions

On Sunday 08 November 2015 15:11:48 René J.V. Bertin wrote: > > So on Linux it uses ~/.config (or $XDG_CONFIG_HOME if set) > > and ~/.local (or $XDG_DATA_HOME if set). > > I suppose it's left to individual app discretion whether or not things are > store > in the .local/.config root, or in

Review Request 126001: In KConfigTest::testEntryMap, convert QByteArray with nulls using a char *

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/126001/ --- Review request for KDE Frameworks. Repository: kconfig Description

Re: Qt 5.6 behavior change with QByteArray(str, size) and QFile::encodeName()

On November 7, 2015 08:07:11 PM David Faure wrote: > KTar's unittests detected a behavior change in Qt. > Thiago, is it intentional, or should it be fixed in Qt ? > > KTar does > > QString name = QFile::decodeName(QByteArray(buffer, 100)); > > where buffer is e.g. "filename\0\0\0\0\0\0[...]" >

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in

Re: Review Request 121861: Remove obsolate class KFileSystemWatcher, which is handled by Windows implementation of Qt5 QFileSystemWatcher.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/121861/ --- (Updated Nov. 8, 2015, 10:37 a.m.) Status -- This change has been

Re: Review Request 125762: External extractor plugin support for KFileMetaData

> On Oct. 30, 2015, 12:43 p.m., Boudhayan Gupta wrote: > > Ping? :-) Err, ship it or drop it? It's been about two weeks sitting, so I was hoping to get some feedback now, either way. - Boudhayan --- This is an automatically generated

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Saturday, November 7, 2015 11:59:48 AM CET David Faure wrote: > > - [5.6] kwindowsystem: KWindowInfoX11Test fails tests > > Martin, can you take a look at > http://ci-logs.kde.flaska.net/0c/0c4039dc8d4c3fa9eed18a4f5604a90648fe3e84/re >

Re: Moving KWayland to frameworks

On Thursday, November 5, 2015 10:50:06 AM CET Martin Graesslin wrote: > 2. We use Qt 5.4. Given David's suggestion on having the last three released Qt releases supported, this issue will resolve itself once Qt 5.6 is released. Given that this is on the horizon I will delay the move of KWayland

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

On Monday 09 November 2015 19:36:09 Ben Cooksley wrote: > On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: > >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > >> > Hi all, > >> > > >> >

Re: Review Request 126001: In KConfigTest::testEntryMap, convert QByteArray with nulls using a char *

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/126001/#review88177 --- Isn't this exactly the wrong fix? The goal of the test with

Review Request 126002: remove unused var

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/126002/ --- Review request for KDE Frameworks. Repository: karchive Description

Re: Review Request 126002: Fix KArchive for behavior change in Qt 5.6

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/126002/ --- (Updated Nov. 9, 2015, 7:54 a.m.) Review request for KDE Frameworks.