I think that changes in Processing to support newer SAGA versions have not been backported to the 2.8.x series, which explains that.
However, with SAGA being the less predictable software ever having tons of API breaks in each version...I dont think our LTR should move the supported SAGA version. If 1.8 had support for SAGA 2.1, it should stick to that for all 2.8.x, and actually the installers and bundles should not advance the version and ship that same version of SAGA always. And if not using a bundled version, the user should install the supported version of SAGA, not a more recent one, since that will probably compromise the stability. My 2 cents 2015-12-24 6:26 GMT+01:00 Paolo Cavallini <[email protected]>: > Il 11/12/2015 23:17, Sebastiaan Couwenberg ha scritto: > >> In the git repository only the master & release-2_12 branches support >> SAGA 2.2 looking at the history of python/plugins/processing/algs/saga/. >> >> It would be great if this can be backported for QGIS 2.8.5. That would >> enable us to close Debian Bug #807339 which also reports the lack of >> support for SAGA 2.2 as found in Debian testing & unstable. Fortunately >> the qgis backport is not affected because jessie ships with SAGA 2.1.2. > > Hi all, > as far as I can see, in 2.8.5 new saga is still not usable: any hope to > have it back? I think this is a major drawback for a LTR version. > All the best. > > -- > Paolo Cavallini - www.faunalia.eu > QGIS & PostGIS courses: http://www.faunalia.eu/training.html > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
