On 2022-04-05 22:36:30, Axel Beckert wrote:
> Package: slop
> Version: 7.6-1
> Severity: serious
> Control: affects -1 maim
>
> Slop seems to provide a shared library without having a proper SONAME or
> ABI in the package name and bumping the library made at least "maim" to
> fail to work:
>
> maim: error while loading shared libraries: libslopy.so.7.5: cannot open
> shared object file: No such file or directory
>
> From my point of view, it is an error of slop to provide a shared
> library but not having a proper library package with proper SONAME or
> ABI version in the package name.
>
> In case you disagree, please do not provide a shared library at all and
> do compile this library directly into the binary "slop".
I agree, this is a long-standing bug in the package, and a lintian
warning I have consistently (and incorrectly) ignored.
I would be happy to take whatever fix you think is best for this. The
package is in salsa.debian.org/debian and i'm LowNMU.
I think my main blocker is fixing this is that I am not super familiar
with shared libs packages. It also seems a little silly to have a shared
lib for something that's essentially called by other packages (although
now it seems that maim does use it as a shared lib).
The other problem is introducing a shared lib would make us go through a
round trip in NEW, but hopefully that should be trivial enough to be
fast.
Anyways, thanks for the bug report, and definitely something that needs
fixing. In the meantime I think a binNMU might fix this on maim's side,
right?
a.
--
The steel horse fills a gap in modern life, it is an answer not only to
its needs, but also to its aspirations. It's quite certainly here to
stay.
- Le Vélocipède Illustré, 1869
