Le 04/07/18 à 10:02, Luca BRUNO a écrit :
On Wednesday, 4 July 2018 07:31:30 UTC you wrote:
The libargon2-0 package is pulling the libargon2-1 package and contains
a symlink pointing to libargon2.so.1.
This is not a good idea and a proper transition should be done.
Is there a specific issue this is causing?
While odd, the rationale for such setup is described here:
https://salsa.debian.org/debian/argon2/merge_requests/3#note_28753
If a library changes its soname all the reverse dependencies needs to be
rebuild, this is happening 10 times a month in the debian archive (and
there far bigger transition happening in the archive that this one)
Adding the "compatibility" package here is completely useless and is
IMHO against best practices.
