[Pkg-ime-devel] Bug#712883: libchewing3: packaging shortcomings

[Osamu Aoki]

Package: libchewing3
Version: 0.3.4-2
Severity: normal

This package does not run test script since it breaks.

This package has following problems too:

I: libchewing source: debug-package-for-multi-arch-same-pkg-not-coinstallable libchewing3-dbg => libchewing3
N: 
N:    The debug package appear to be containing debug symbols for a
N:    "Multi-Arch: same" package, but the debug package itself is not
N:    "Multi-Arch: same". If so, it is not possible to have the debug symbols
N:    for all architecture variants of the binaries available at the same
N:    time.
N:    
N:    Making a debug package co-installable with itself is very trival, when
N:    installing the debug symbols beneath:
N:      /usr/lib/debug/.build-id/<XX>/<rest-id>.debug
N:    
N:    dh_strip does this in debhelper compat 9. Otherwise, the expected
N:    location of the debug symbols of a given ELF binary can be determined by
N:    using:
N:    
N:     readelf -n <binary-elf> | \
N:         perl -ne 'print if s,^\s*Build ID:\s*(\S\S)(\S+),/usr/lib/debug/.build-id/$1/$2.debug,'
N:    
N:    Severity: minor, Certainty: possible
N:    
N:    Check: group-checks, Type: source

I: libchewing3: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libchewing.so.3.0.1
N: 
N:    This package provides an ELF binary that lacks the use of fortified libc
N:    functions. Either there are no potentially unfortified functions called
N:    by any routines, all unfortified calls have already been fully validated
N:    at compile-time, or the package was not built with the default Debian
N:    compiler flags defined by dpkg-buildflags. If built using
N:    dpkg-buildflags directly, be sure to import CPPFLAGS.
N:    
N:    NB: Due to false-positives, Lintian ignores some unprotected functions
N:    (e.g. memcpy).
N:    
N:    Refer to http://wiki.debian.org/Hardening and
N:    http://bugs.debian.org/673112 for details.
N:    
N:    Severity: normal, Certainty: wild-guess
N:    
N:    Check: binaries, Type: binary, udeb

I skipped these for this RC bug fix only upload.  Next time :-)  (But maybe
uploaded by some one understanding Chinese.)