El dilluns, 25 d’abril de 2016, a les 9:05:58 CEST, Ben Cooksley va escriure: > On Sun, Apr 24, 2016 at 11:46 AM, Michael Pyne <mp...@kde.org> wrote: > > On Sat, April 23, 2016 13:09:00 Ben Cooksley wrote: > >> On Sat, Apr 23, 2016 at 1:04 PM, Daniel Vrátil <dvra...@kde.org> wrote: > >> > any chance to get this patch into our Qt build on the CI since it has > >> > been > >> > integrated upstream now? As it affects all tests that interact with > >> > DBus > >> > it > >> > would be nice to resolve this on the CI. > >> > >> We'll need upstream to update qt5.git (I think that's still required > >> for changes to fully flow through) I think. > >> We could try to hack the patch in, but then we'll end up having to > >> undo that in a few weeks time. > > > > If we're talking about Qt commit 1b9d082b, that appears to already be in > > the 5.6 branch (though not dev). I'm not sure which the CI uses though, > > if it's not 5.6 or less then it is probably more work than its worth to > > try to downgrade (something I've run into too much myself). > > The CI system uses the 5.6 branch, from qt5.git. > I've now triggered a build, but as qt5.git hasn't been updated since > our last build I have no idea whether this will pull the relevant > commit in.
Is there any special reason we inflict ourselves the pain of using qt5.git instead of the standalone repos? Cheers, Albert > > > Regards, > > > > - Michael Pyne > > Cheers, > Ben > _______________________________________________ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel