[Debian-med-packaging] Bug#1109178: Bug#1109176/1109177/1109179: psfex/scamp/source-extractor

Lucas Nussbaum lucas at debian.org
Mon Jul 14 06:48:16 BST 2025


On 13/07/25 at 14:55 +0200, Ole Streicher wrote:
> Control: tags -1 moreinfo
> 
> Hi Lucas,
> 
> Am 13.07.25 um 10:17 schrieb Lucas Nussbaum:
> > 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
> > Investigating (0) psfex:amd64 < 3.21.1-1 -> 3.24.2-2 @ii umU Ib >
> > Broken psfex:amd64 Depends on liblapacke:amd64 < none | 3.12.1-2 @un uH > (>= 3.12.0)
> >    Considering liblapacke:amd64 0 as a solution to psfex:amd64 0
> >    Holding Back psfex:amd64 rather than change liblapacke:amd64
> >   Try to Re-Instate (1) psfex:amd64
> 
> To me, this looks rather a problem of liblapacke instead of
> psfex/scamp/source-extractor, but I must admit that I do not fully
> understand the problem: libatlas3-base is removed in Trixie and could/should
> therefore be removeable.

Hi,

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.

Lucas



More information about the Debian-med-packaging mailing list