On Tue, 06 Dec 2016 at 14:49:35 +0100, Alexander Larsson wrote: > The flatpak package has versioned build-deps on ostree, but the actual > package-deps (i.e. flatpak -> libostree) are not.
Versioned library dependencies on Debian and its derivatives are normally generated via dpkg-shlibdeps, rather than hard-coded in debian/control. In the case of flatpak depending on libostree, the dependency that is generated is the earliest version that contained all the symbols used by the just-built flatpak. Are you aware of a semantic change in libostree that would require tighter dependencies for users of a particular symbol or symbols? If so, we can do that by editing debian/*.symbols in ostree, which has the advantage of working for all libostree users (not specific to flatpak). In practice flatpak <https://packages.debian.org/unstable/flatpak> and libflatpak0 <https://packages.debian.org/unstable/libflatpak0> currently both have dependencies on libostree-1-1 (>= 2016.14), except for the unofficial ppc64 port which has an outdated build of both flatpak and ostree. So I don't think there's any practical problem here? Can you point me to a concrete example of building the flatpak source package against a particular version of ostree, and getting insufficient dependencies as a result? Thanks, S
