On 21 September 2015 at 12:34, Simon McVittie wrote: | 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
I'd prefer libquantlib1. Any reason not to? | binNMU the bindings against it, unless you have another way to ensure I fail to understand. The two packages both have sufficient Build-Depends as eg here for quantlib-python Build-Depends: debhelper (>= 7.0.0), python, python-all-dev (>= 2.6.6-3), \ libquantlib0-dev (>= 1.6.2), gcc (>= 4:5.2), g++ (>= 4:5.2), \ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ libboost-dev (>= 1.34.0), libboost-test-dev (>= 1.34.0) resulting in corresponding versioned Depends. | that broken combinations of packages cannot be installed (including | during the upgrade from jessie-as-oldstable to stretch-as-stable after | stretch is released). I don't see how using the package manager. | 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. I guess the renamed libquantlib1 should help. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
