Source: xindy Version: 2.5.1.20160104-12 Severity: normal Dear Maintainer,
xindy is preventing clisp from migrating to testing, see [1] "migrating clisp/1:2.49.20250504.gitf662209-1/ppc64el to testing makes xindy/2.5.1.20160104-12/ppc64el uninstallable" Simply rebuilding the package against an updated clisp would be enough. However this problem would reappear every time a new clisp is released. How would you like to solve this going forward? Would it be acceptable for me to rebuild xindy (perhaps do some maintenance too) and upload it when I release a new clisp package, or do you prefer do a binNMU? Best regards, Peter 1 https://tracker.debian.org/pkg/clisp -- System Information: Debian Release: 13.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.43+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
