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 still end up with the need for a (small) migration: You would still need to upload a new maim every time a new version of slop gets uploaded. And until that builds, maim would be uninstallable.
But if you split slop up, that migration would be easier, as the archive would keep the old libsloppy-<ABI-version> package around until nothing depends on it anymore, so until maim would be rebuilt (which could even be a binary-rebuild, so without actual new upload), it would still remain installable. Additionally, Debian release tooling would properly identify this (which it currently can't) and could (not sure if it would) trigger the binary-rebuild. Cheers, Sven
