On Mon, 19 Dec 2011 12:46:46 +0100, Johannes Ring <joha...@simula.no> wrote:
> On Mon, Dec 19, 2011 at 10:37 AM, Andreas Kloeckner <inf...@tiker.net> wrote:
> > Did, and it helped. Thanks very much!
>
> Good!
>
> > This being as it is, could you upload a new package with tightened
> > dependencies?
>
> The dependency on libarmadillo2 is added automatically by
> ${shlibs:Depends}. I guess I could add a version requirement for
> libarmadillo-dev in Build-Depends, but DOLFIN does not depend on a
> specific version of Armadillo, so I don't see why I should. You had
> this problem because you were using an old libarmadillo2 (version
> 1:2.2.5+dfsg-1) from testing while you using DOLFIN (version 1.0.0-1)
> from unstable, which was built against a newer libarmadillo2 package
> from unstable. I guess this is a problem you will see from time to
> time when mixing packages from testing and unstable.Hmm, I feel like automatic shared library dependencies should have been able to catch this, i.e. someone is supposed to have done something with the soname at some point--I'm just not sure what... :) In any case, thanks very much for your help! Andreas
pgpBjC7dJ8gER.pgp
Description: PGP signature
