Bug#651997: python-dolfin: unknown symbol: wrapper_dgesv_
Kumar Appaiah
akumar at debian.org
Thu Dec 22 17:08:13 UTC 2011
On Thu, Dec 22, 2011 at 06:04:03PM +0100, Julien Cristau wrote:
> > 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
> here AFAIK.
That clears is up. I'll do the needful. Thanks.
Sorry, Conrad, for causing the confusion.
Kumar
--
Kumar Appaiah
More information about the debian-science-maintainers
mailing list