Bug#839240: saga: Should have a stricter dependency between saga and libsaga

Sebastiaan Couwenberg sebastic at xs4all.nl
Fri Sep 30 15:12:54 UTC 2016


On 09/30/2016 05:03 PM, Nelson A. de Oliveira wrote:
> About https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838915#25 I saw
> that I had saga at version 2.3.1+dfsg-2 and libsaga-* at version
> 2.3.1+dfsg-1+b1

Why weren't the libsaga-* packages upgraded along with saga? You have
gotten version 2.3.1+dfsg-2 for all of the saga packages.

> The dependency was properly satisfied when saga was pulled from unstable
> (it depends on libsaga-api-2.3.1 only, for example, instead on a
> possibly stricter libsaga-api-2.3.1 (= 2.3.1+dfsg-2))
> 
> Shouldn't we have this dependency versioned?

A stricter dependency from saga on the libsaga-* packages may be
worthwhile. With symbols files (which saga doesn't use (yet)) the
version requirement will only be on the upstream version which won't
solve this problem, using dh_makeshlibs -V will have a much stricter
dependency which should solve this issue.

This issue doesn't seem to be a bug in saga per se though, more the
results of an incomplete upgrade.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



More information about the Pkg-grass-devel mailing list