Dependencies for shibboleth-sp2 2.6.0+dfsg1-3 jessie backport

[Ferenc Wágner]

Etienne Dysli-Metref <etienne.dysli-metref at switch.ch> writes:

> Just like when backporting opensaml2 for jessie, I'd like the
> backported version of shibboleth-sp2 to require the latest releases.
>
> Here is the diff for debian/control, is that correct? Should all
> "generic" version numbers (like 2.5) be turned into precise versions
> (2.6.0-4~)?

In the build-deps they should be, because these latest revisions
introduced vital changes in the exported pkg-config data (pkgxmldir).

> - shibboleth-sp2-utils (>= 2.5),
> + shibboleth-sp2-utils (>= 2.6),

This should have been done in master, I guess.

> - opensaml2-schemas (>= 2.5),
> - shibboleth-sp2-common (>= 2.5),
> - xmltooling-schemas (>= 1.5),
> + opensaml2-schemas (>= 2.6.0-4~),
> + shibboleth-sp2-common (>= 2.6),
> + xmltooling-schemas (>= 1.6.0-3~),

Likewise, but two parts should be enough here (2.6, 2.6, 1.6).

> - libsaml2-dev (>= 2.5),
> + libsaml2-dev (>= 2.6.0-4~),
>   libshibsp7 (= ${binary:Version}),
>   libxerces-c-dev,
> - libxmltooling-dev (>= 1.5),
> + libxmltooling-dev (>= 1.6.0-3~),

Likewise.  Shall I push a commit for these, or will you?
OpenSAML2 could do with a similar one, too...
-- 
Feri