On Tue, Feb 04, 2025 at 08:27:35PM +0000, asikrom wrote:
Installing package 'libmodplug1' manually seems to make the issue
disappear, as the main program is then able to start as expected.
However, according to an upstream bug/issue entry [1] and upstream
documentation [2], libmodplug1 is not supposed to be strictly required.
There is an upstream commit [3] which fixes this so that libmodplug1
once again becomes optional.
Thanks for tracking this down. I'll cherry-pick that patch.
--
Colin Watson (he/him) [cjwat...@debian.org]
