[Debian-med-packaging] Bug#1130465: Bug#1130465: liborthancframework-dev: should the dependency on libboost-all-dev be versioned?

[Sébastien Jodogne]

Dear Paul,

Thanks for your analysis.

> I've been checking on the autopkgtest regressions triggered by the 
> binNMU of src:orthanc and noticed a pattern that's shared with bug
> 1129823 and it's clones. I have the impression (just a hunch) that the 
> boost major version that gets installed by liborthancframework-dev via 
> libboost-all-dev needs to be the same version as was used during 
> building of liborthancframework1. If so, could you please generate a 
> proper version for a versioned dependency during building?

I have just released a new version of the liborthancframework-dev 
package (1.12.10+dfsg-2), which notably includes the following changeset:

https://salsa.debian.org/med-team/orthanc/-/commit/43304015d951fc6701fe1329769943c10d3301c5

Could you please confirm that this is what you expected? In particular, 
I was wondering whether the ">=" should be replaced with "=". I have not 
used this pattern in this case, as I've read that using "=" might break 
some transitions.

I also wonder why explicit versioning is required only for 
libboost-all-dev in liborthancframework-dev, but not for the other 
"-dev" package dependencies on C++ libraries (i.e. libdcmtk-dev, 
libjsoncpp-dev, and libpugixml-dev).

I also had a look at libgdcm-dev and libdcmtk-dev, and neither of these 
packages uses explicit versioning for any of their dependencies, so I am 
unsure whether the changeset above will actually help.

Kind Regards,
Sébastien-