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

Bug#630186: marked as done (sunpinyin-utils: shlib-calls-exit)



Your message dated Tue, 3 Dec 2019 21:19:52 +0900
with message-id <CAEe2ifU1OjtMj4kWbE-b4oAfct7i17rucrCyXs-GDj8X_Xtrhg@mail.gmail.com>
and subject line Re: sunpinyin-utils: shlib-calls-exit
has caused the Debian Bug report #630186,
regarding sunpinyin-utils: shlib-calls-exit
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.)


-- 
630186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630186
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sunpinyin-utils
Version: 2.0.3-2

While backporting sunpinyin to squeeze-backports, I discovered that
there are shlib-call-exit as shown in following lintian reports
(lintian -E):
X: sunpinyin-utils: shlib-calls-exit usr/bin/genpyt
X: sunpinyin-utils: shlib-calls-exit usr/bin/getWordFreq
X: sunpinyin-utils: shlib-calls-exit usr/bin/idngram_merge
X: sunpinyin-utils: shlib-calls-exit usr/bin/ids2ngram
X: sunpinyin-utils: shlib-calls-exit usr/bin/mmseg
X: sunpinyin-utils: shlib-calls-exit usr/bin/slmbuild
X: sunpinyin-utils: shlib-calls-exit usr/bin/slminfo
X: sunpinyin-utils: shlib-calls-exit usr/bin/slmprune
X: sunpinyin-utils: shlib-calls-exit usr/bin/slmseg
X: sunpinyin-utils: shlib-calls-exit usr/bin/slmthread
X: sunpinyin-utils: shlib-calls-exit usr/bin/tslmendian
X: sunpinyin-utils: shlib-calls-exit usr/bin/tslminfo
X: sunpinyin-utils: shlib-calls-exit usr/bin/tslmpack

This should be an upstream bug, and altering it might cause ABI breakage.

-- 
Regards,
Aron Xu



--- End Message ---
--- Begin Message ---
Control: reassign 630186 lintian
Control: forcemerge 607399 630186

It was a false alarm by fixed lintian bug  (the listed files were not
even shlibs):

--- End Message ---

Reply to: