Package: xar Version: 1.8.0.498-2 Severity: normal Dear Ole,
the recent BinNMU of xar looks broken or at least odd: xar/1.8.0.498-2+b1 depends on "libxar1 (= 1.8.0.498-2)" despite libxar1/1.8.0.498-2+b1 has been built, too. Shouldn't it depend on "libxar1 (= 1.8.0.498-2+b1)" instead? Feel free to raise or lower the severity, as I'm filing this with a default severity because I'm unsure of how severe the impact actually is: It kinda looks RC (and hence might need a fix for trixie/stable, too), but at least "xar --help" doesn't throw any linking error. Stumbled upon it when I looked at why libxar1 wasn't upgraded to the latest version. -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.37+deb13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages xar depends on: ii libc6 2.41-12 ii libxar1 1.8.0.498-2 xar recommends no packages. xar suggests no packages. -- no debconf information
