Bug#651997: python-dolfin: unknown symbol: wrapper_dgesv_
julien.cristau at logilab.fr
Thu Dec 22 17:04:03 UTC 2011
On Thu, Dec 22, 2011 at 10:19:46 -0600, Kumar Appaiah wrote:
> Dear Julien,
> On Wed, Dec 21, 2011 at 10:29:55PM +0100, Julien Cristau wrote:
> > > > To fix this issue, just make sure that the system uses the same
> > > > version of the header files as the version of the run-time library.
> > > > Specifically, this means if Armadillo 2.4.2 is used, both the headers
> > > > _and_ the run-time library must be at version 2.4.2.
> > >
> > > Shouldn't the dependencies save me from shooting myself in the foot like
> > > that, somehow ?
> > >
> > Yes, this is a packaging bug in libarmadillo2, I reassigned this report
> > there.
> After some discussion with upstream here is the summary:
> - Upstream will not raise the soname, since this, in their view, is
> does not warrant one. Their opinion is that armadillo's ABI isn't
> really for direct use by the end user, so a recompile should
> - They recommend eliminating all versions of the old libraries and
> rebuilding dolfin with the new ones.
> Now, this breaks existing installs of dolfin, so this is not an
> option. I am now wondering what the best course of action is. Do I
> create a new named package, or manually update the soname locally to
> Debian? Or, do I request removal of offending versions of the package,
> like upstream suggests?
So I haven't actually *checked*, but from what I understood of this
thread the ABI changes were compatible, which means there is and was no
reason to bump the SONAME, only the version in the shlibs packaging
metadata, for the added symbols in 2.4.2. This is not an upstream
problem, it's a bug in the package, there is nothing for upstream to do
Julien Cristau <julien.cristau at logilab.fr>
Informatique scientifique & gestion de connaissances
More information about the debian-science-maintainers