Bug#651997: python-dolfin: unknown symbol: wrapper_dgesv_

Johannes Ring johannr at simula.no
Tue Dec 20 10:35:53 UTC 2011


[Adding Kumar (maintainer of Armadillo) in Cc]

On Tue, Dec 20, 2011 at 10:16 AM, Julien Cristau
<julien.cristau at logilab.fr> wrote:
> On Mon, Dec 19, 2011 at 12:46:46 +0100, Johannes Ring wrote:
>> On Mon, Dec 19, 2011 at 10:37 AM, Andreas Kloeckner <inform at tiker.net> wrote:
>> > 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.
>>
> No, it absolutely isn't.  If libarmadillo2 exports new symbols then it
> has to bump the version in its shlibs declaration.  If it didn't do
> that, this is a serious bug in that package.

Yes, you are absolutely right. What I wrote above wasn't thought through.

Johannes





More information about the debian-science-maintainers mailing list