On 21/09/15 12:23, Dirk Eddelbuettel wrote:
> So they are all compiled with g++-5.4, I just didn't switch to
>
> libquantlib0v5
> libquantlib1 (alternate, as I never renamed ...)
>
> So you say I should?
Yes, you should rename to libquantlib0v5 and ask the release team to
binNMU the bindings against it, unless you have another way to ensure
that broken combinations of packages cannot be installed (including
during the upgrade from jessie-as-oldstable to stretch-as-stable after
stretch is released).
quantlib-python or r-cran-rquantlib from jessie, with libquantlib0 from
stretch, seems very likely to be a broken combination.
If quantlib has not bumped shlibs recently, then the opposite -
libquantlib0 from jessie with bindings from stretch - might also be broken.
S
