Package: eclipse-titan Version: 7.2.0-1.1 Severity: wishlist I just noticed that even unstable still ships eclipse-titan 7.2, while upstream has released 8.0.0 in August 2021 and now already 8.1.0 yesterday.
It is my general assumption (I may be wrong) that unstable is tracking upstream with relatively small delay, so that whenever stabilization of a new debian release happens the then-latest versions of the software are frozen. If unstable lags behind upstream significantly, then the versions appearing in stable distributions are going to be even older. Maybe the new upstream releases were just not noticed? Or are there known problems why one should avoid upgrading? Thanks in advance! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages eclipse-titan depends on: ii expect 5.45.4-2+b1 ii gcc 4:11.2.0-2 ii libc6 2.32-4 ii libedit-dev 3.1-20210910-1 ii libedit2 3.1-20210910-1 ii libgcc-s1 11.2.0-12 ii libpcap-dev 1.10.1-4 ii libpcre3-dev 2:8.39-13 ii libsctp-dev 1.0.19+dfsg-1 ii libssl-dev 1.1.1l-1 ii libssl1.1 1.1.1l-1 ii libstdc++6 11.2.0-12 ii libxml2 2.9.12+dfsg-5+b1 ii libxml2-dev 2.9.12+dfsg-5+b1 ii make 4.3-4.1 ii perl 5.32.1-6 ii python3 3.9.8-1 Versions of packages eclipse-titan recommends: ii default-jdk 2:1.11-72 eclipse-titan suggests no packages. -- no debconf information
