On 19 June 2014 08:50, Kevin Ottens <er...@kde.org> wrote: > On Thursday 19 June 2014 08:21:30 Ben Cooksley wrote: >> On 19 June 2014 07:19, Kevin Ottens <er...@kde.org> wrote: >> > On Monday 16 June 2014 20:55:10 Michael Pyne wrote: >> >> On Mon, June 16, 2014 13:14:47 Kevin Ottens wrote: >> >> > On Monday 16 June 2014 12:58:30 Àlex Fiestas wrote: >> >> > > I encountered this yesterday, for a quick workaround rollback to >> >> > > cmake >> >> > > 3.0 >> >> > > (cmake-git is what makes this happen) >> >> > >> >> > In fact, maybe a sign that our kdesrc-build config file should request >> >> > a >> >> > fixed version of cmake nowadays? >> >> >> >> I'd recommend requesting a stable branch if that's doable instead of a >> >> fixed tag, but that's a good idea, yes. >> > >> > Just pushed the change to depend on the release branch now. So hopefully >> > we >> > should be back to stable soon on the CI. >> >> Hm? The CI system is still configured to use the 'next' branch for CMake... > > Somehow I thought it was following the info from kdesrc-build include files. > OK, so I fixed the situation only for the developers. :-) > > How do we get the CI to use the release branch as well?
By filing a ticket :) Then we can adjust the CMake job configuration and force a build to be made. Note though that I consider this a workaround for an upstream regression which we have detected. One of the reasons the CI system runs the next branch is to detect such regressions before they end up in a release and impact us. > > Regards. > -- > Kévin Ottens, http://ervin.ipsquad.net > > KDAB - proud supporter of KDE, http://www.kdab.com Thanks, 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
