Your message dated Thu, 2 Oct 2025 12:46:39 +0200 with message-id <f322aadb-097e-4254-8c20-208972657f4f@web.de> and subject line Re: Bug#1116700: xindy preventing clisp from migrating to testing has caused the Debian Bug report #1116700, regarding xindy preventing clisp from migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1116700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116700 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xindy preventing clisp from migrating to testing
- From: Peter Van Eynde <pvaneynd@debian.org>
- Date: Tue, 30 Sep 2025 13:15:35 +0200
- Message-id: <175923093528.4132246.9247888993635749192.reportbug@frost.edegem.home>
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
--- End Message ---
--- Begin Message ---
- To: Peter Van Eynde <pvaneynd@debian.org>
- Cc: 1116700-done@bugs.debian.org
- Subject: Re: Bug#1116700: xindy preventing clisp from migrating to testing
- From: Preuße, Hilmar <hille42@web.de>
- Date: Thu, 2 Oct 2025 12:46:39 +0200
- Message-id: <f322aadb-097e-4254-8c20-208972657f4f@web.de>
- In-reply-to: <175923093528.4132246.9247888993635749192.reportbug@frost.edegem.home>
- References: <175923093528.4132246.9247888993635749192.reportbug@frost.edegem.home>
On 9/30/2025 1:15 PM, Peter Van Eynde wrote: Hello,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"clisp has been migrated. Closing. H. -- sigfaultAttachment: OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---