Boost specifications in the debian packages causing some issues in the LHO CDS control room..

The changes to allow packaging framecpp/al/... for bullseye welcome updates. However they are introducing issues with installs due to the range of boost libraries that can satisfy the requirements.

The specification for libboost-filesystem1.74.0 | libboost-filesystem1.71.0 | libboost-filesystem1.67.0 (as an example) is causing issues with installing the cds-workstation package and has implications in the daqd packaging. Apt is seeing that newer versions are availble (if backports are specified), and failing to resolve to old versions if other software needs 1.67 instead of 1.71 or 1.74.

Really, we need the version required to be whatever it was built against. I don't want to debug what happens if we link with 1.67, but the install allows 1.74.

Please also be aware that we need warning if a non-system default boost library may be used. In CDS we use boost asio as the center piece for our core network (in the software that connects the real time systems and the daqd servers), and asio is an example library that is changing (as the networking proposal evolves) between releases. We cannot have that boost version change on us unexpectedly.

Thanks,