Bug#1109176: Broken liblapacke:amd64 Breaks on libatlas3-base

[Jochen Sprickerhof]

Hi,

I looked into it a bit more and got it working with a transitional dummy 
package as described here:

https://wiki.debian.org/RenamingPackages

I have added this to lapack:

Package: libatlas3-base
  Depends: libblas3, ${misc:Depends}
  Architecture: all
  Priority: optional
  Section: oldlibs
  Description: transitional package
   This is a transitional package. It can safely be removed.

As it is already late for trixie I uploaded it to NEW/experimental. The 
release team agreed to take it afterwards. I will take care of the rest 
unless someone disagrees with the approach.

Cheers Jochen


* Jochen Sprickerhof <jspricke at debian.org> [2025-07-18 10:26]:
>Hi,
>
>* M. Zhou <lumin at debian.org> [2025-07-17 22:35]:
>>I'm still a little bit confused about the report.
>>
>>Based on the podman image debian:bookwork, I can upgrade psfex without apt
>>reporting issue like reported. So the problem seems to be highly specific
>>to the -14 revision of atlas.
>
>There is a reproducer in the initial bug report that is still valid 
>for me.
>
>>Do that mean making lapack break the -14 version is enough to fix this bug?
>>```
>>-        libatlas3-base (<< 3.10.3-14)
>>+        libatlas3-base
>>```
>
>From a quick look libatlas3-base in bookworm was split into multiple 
>packages and there is a Break: but no Replaces: see
>
>https://wiki.debian.org/PackageTransition
>
>I think #7 applies.
>
>Cheers Jochen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20250719/4808064f/attachment.sig>