Source: tulip
Version: 4.8.0dfsg-2+b7
Severity: important
Dear Maintainer,
# apt install tulip
The following packages have unmet dependencies:
tulip : Depends: binutils (< 2.29) but 2.33.1-2 is to be installed
Depends: libglew2.0 (>= 1.12.0) but it is not installable
Depends: libtulip-gui-4.8 but it is not going to be installed
Depends: libtulip-ogl-4.8 but it is not going to be installed
Depends: libtulip-python-4.8 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
#
binutils is 2.33.1-2 in testing. and 2.31.1-16 in stable/buster.
This makes tulip not installable.
I have a strong suspiecious that the dependence on binutils is actually
not needed at all.
Also I see this removal from testing over 2 years ago:
https://tracker.debian.org/news/863415/tulip-removed-from-testing/
Which also mentions binutils.
Also upstream version is now 5.3.1, and 5.2.1 supports even Python 3. So
it would be greate to have it all fixed in Debian.
Best regards,
Witold
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
