❦ 12 May 2020 14:25 +02, Yuri D'Elia:
> I didn't realize maim depended on slop through a dso (I assumed it
> simply called the binary).
>
> slop was updated to 7.5, which broke maim as a result:
>
> maim: error while loading shared libraries: libslopy.so.7.4: cannot
> open shared object file: No
Hi there.
The solution mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960420#10 (splitting slop
into two packages) would actually be the right way to go.
If maim were to automatically generate a versioned dependency on slop based
on the version installed during build, you would
On 2020-05-12 14:25:43, Yuri D'Elia wrote:
> Package: maim
> Version: 5.5.3-1
> Severity: important
>
> I didn't realize maim depended on slop through a dso (I assumed it
> simply called the binary).
>
> slop was updated to 7.5, which broke maim as a result:
>
> maim: error while loading shared
Package: maim
Version: 5.5.3-1
Severity: important
I didn't realize maim depended on slop through a dso (I assumed it
simply called the binary).
slop was updated to 7.5, which broke maim as a result:
maim: error while loading shared libraries: libslopy.so.7.4: cannot open shared
object file:
4 matches
Mail list logo
