Hi Lucas, Etienne,
Am 14.07.25 um 07:48 schrieb Lucas Nussbaum:
In #1109178 (emmax: fails to dist-upgrade from bookworm (related to
libatlas3-base removal)), Etienne added a Breaks to libatlas3-base to
work-around the issue.
Maybe the break could be set in libpacke instead.
liblapacke already has a
Breaks: [...], libatlas3-base (<< 3.10.3-14)
which should work for a direct update from bookworm (Bookworm has
3.10.3-13), but not from a later testing (latest version in testing was
3.10.3-14).
However, this break was already detected by apt:
Broken liblapacke:amd64 Breaks on libatlas3-base:amd64 < 3.10.3-13 @ii mK > (<
3.10.3-14)
Considering libatlas3-base:amd64 1 as a solution to liblapacke:amd64 0
Holding Back liblapacke:amd64 rather than change libatlas3-base:amd64
where I don't understand the solution taken by apt. However, even apt
considers liblapacke as "broken"; and I don't see why adding a break to
psfex & Co. would solve this.
I'd really tend to re-assing these bugs to lapack.
Cheers
Ole
