[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1088074: marked as done (nmu: xindy_2.5.1.20160104-12)

Your message dated Wed, 27 Nov 2024 10:53:22 +0100
with message-id <450924e3-16a7-4465-910d-1aa864d801dc@debian.org>
and subject line Re: Bug#1088074: nmu: xindy_2.5.1.20160104-12
has caused the Debian Bug report #1088074,
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 owner@bugs.debian.org
immediately.)


-- 
1088074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088074
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: xindy@packages.debian.org
Control: affects -1 + src:xindy

nmu xindy_2.5.1.20160104-12 . s390x ppc64 . unstable . -m "BinNMU to correct dependency on clisp."

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 22/11/2024 21:13, Hilmar Preusse wrote:

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: xindy@packages.debian.org
Control: affects -1 + src:xindy

nmu xindy_2.5.1.20160104-12 . s390x ppc64 . unstable . -m "BinNMU to correct dependency on clisp."


Looks like this updates this outdated dependency:
Depends: xindy-rules, clisp-memfile-hash-fbc60b2efef7f8f6f66455cf914597e53e3a3d1a, libc6 (>= 2.34), perl:any, clisp 

The clisp-memfile-hash hash has changed there.
binNMU scheduled on s390x (the ppc64 build failed, so it can't be binNMU'ed. I'll retry it just in case). Please provide some more details next time so that we don't have to go dig up what's going on. 

Cheers,
Emilio

--- End Message ---
Reply to: