On 14/06/2021 10.06, Sebastiaan Couwenberg wrote:
What actual problems do are solved by making them co-installable? So far the only actualy problem that has been identified is the need for `apt full-upgrade` twice when the Breaks/Replaces on libgdal20 is not present.
apt currently fails to find an upgrade path for libmrpt-dev (logfile attached, no bug filed, yet). The only solution I could find so far was the big hammer: adding a Breaks against libopencv-core3.2 (or similar) to gcc-10-base. With a co-installable libgdal20/libgdal28 this is gone because the huge dependency trees no longer conflict with each other.
Co-installable libgdal20/28 solves a lot of buster->bullseye upgrade issues. So I can concentrate on fixing the remaining incomplete (unversioned) python (2) removal bits. ;-)
Andreas
Attachment:
libmrpt-dev.1.norm.log.gz
Description: application/gzip