Package: antimony Version: 0.9.3-1+b1 Followup-For: Bug #951979 Dear Maintainer,
Is it possible to update the package on the current Debian stable to fix this bug? Currently it won't start at all. For anyone who can't start antimony on the the current Debian stable (buster), this seems to make it work: $ ln -s /usr/lib/x86_64-linux-gnu/libboost_python37.so.1.67.0 /usr/lib/x86_64-linux-gnu/libboost_python36.so.1.67.0 Regards, LZY -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing') Architecture: amd64 (x86_64) Versions of packages antimony depends on: ii libboost-python1.67.0 1.67.0-13+deb10u1 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libpng16-16 1.6.36-6 ii libpython3.7 3.7.3-2+deb10u1 ii libqt5concurrent5 5.11.3+dfsg1-1+deb10u3 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5gui5 5.11.3+dfsg1-1+deb10u3 ii libqt5network5 5.11.3+dfsg1-1+deb10u3 ii libqt5opengl5 5.11.3+dfsg1-1+deb10u3 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libstdc++6 8.3.0-6 ii python3 3.7.3-1 ii zlib1g 1:1.2.11.dfsg-1 antimony recommends no packages. antimony suggests no packages. -- no debconf information
