Your message dated Wed, 1 Oct 2025 09:19:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#1116932: nmu: xindy_2.5.1.20160104-12
has caused the Debian Bug report #1116932,
regarding nmu: xindy_2.5.1.20160104-12
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 [email protected]
immediately.)
--
1116932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116932
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:xindy
User: [email protected]
Usertags: binnmu
Hello,
In order for clisp to get migrated into testing xindy needs to get
rebuild using this new clisp image in unstable.
Rebuilding xindy against this new clisp should automatically update the
dependency and fix this problem.
Thanks!
nmu xindy_2.5.1.20160104-12 . ANY . unstable . -m "Rebuilding for new clisp
release 1:2.49.20250504.gitf662209-1"
--- End Message ---
--- Begin Message ---
On 30/09/2025 20:26, Peter Van Eynde wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:xindy
User: [email protected]
Usertags: binnmu
Hello,
In order for clisp to get migrated into testing xindy needs to get
rebuild using this new clisp image in unstable.
Rebuilding xindy against this new clisp should automatically update the
dependency and fix this problem.
Thanks!
nmu xindy_2.5.1.20160104-12 . ANY . unstable . -m "Rebuilding for new clisp release
1:2.49.20250504.gitf662209-1"
Scheduled.
Emilio
--- End Message ---