[Debian-med-packaging] Bug#1130465: Bug#1134597: Please hint orthanc/1.12.11+dfsg-3 migration (force-badtest orthanc-wsi/3.3+dfsg-2)

[Adrian Bunk]

On Fri, Apr 24, 2026 at 08:28:45AM +0200, Sébastien Jodogne wrote:
> Hi,
> 
> > Unfortunately I can't really tell you what the exact solution should be
> > because I don't know how boost and orthanc work together. To avoid
> > breakage the expectations of orthanc on boost should be reflected in the
> > Depends. Maybe people better in figuring out library relations can jump
> > in? To avoid the issue in bug 1130465 I think a reasonable upper limit
> > is needed, to avoid the migration issue you're having now, you need a
> > better lower limit. How to pick/generate that, I don't know.
> 
> Orthanc is known to be compatible with Boost 1.69.0 (this is verified on our
> upstream integration servers), so I don't think #1130465 is a source-level
> problem because of an incompatible version of Boost, but rather a (maybe
> transient?) issue specific to Debian packaging.
>...

The issue is related to static linking.

The shared library has a dependency on the boost packages it was built 
with encoded in libOrthancFramework.so.1.12.11:
  NEEDED               libboost_locale.so.1.90.0
  NEEDED               libboost_filesystem.so.1.90.0
  NEEDED               libboost_thread.so.1.90.0
  NEEDED               libboost_iostreams.so.1.90.0

There are no dependencies encoded in static libraries, it has to be 
ensured in a different way that when linking with libOrthancFramework.a
the correct libraries are linked - like with depending on the exact
boost version that was used as suggested by Paul.

The proper solution would be:
- rename liborthancframework1 to liborthancframework1.12.11, and
- link with the shared library instead of the static library, and
- make a library transition on every new orthanc version

With NEW processing being much faster now this should be feasible.

> Kind Regards,
> Sébastien-

cu
Adrian

BTW: Shipping libOrthancFramework.a in liborthancframework1 is wrong in 
     any case, the static library should be in liborthancframework-dev
     to avoid users having this 13 MB file installed they don't need.