P: jai-core source: source-contains-prebuilt-binary src/share/mediaLib/linux/amd64/libmlib_jai.so
N: 
N:    The source tarball contains a prebuilt ELF object. They are usually left
N:    by mistake when generating the tarball by not cleaning the source
N:    directory first. You may want to report this as an upstream bug, in case
N:    there is no sign that this was intended.
N:    
N:    Severity: pedantic, Certainty: certain
N:    
N:    Check: cruft, Type: source
N: 
P: jai-core source: source-contains-prebuilt-binary src/share/mediaLib/linux/i386/libmlib_jai.so
I: jai-core source: debian-watch-file-is-missing
N: 
N:    This source package is not Debian-native but it does not have a
N:    debian/watch file. This file is used for automatic detection of new
N:    upstream versions by the Debian External Health Status project and other
N:    project infrastructure. If this package is maintained upstream, please
N:    consider adding a debian/watch file to detect new releases.
N:    
N:    If the package is not maintained upstream or if upstream uses a
N:    distribution mechanism that cannot be meaningfully monitored by uscan
N:    and the Debian External Health Status project, please consider adding a
N:    debian/watch file containing only comments documenting the situation.
N:    
N:    Refer to Debian Policy Manual section 4.11 (Optional upstream source
N:    location: debian/watch) and the uscan(1) manual page for details.
N:    
N:    Severity: wishlist, Certainty: certain
N:    
N:    Check: watch-file, Type: source
N: 
P: libjai-core-java-doc: no-upstream-changelog
N: 
N:    The package does not install an upstream changelog file. If upstream
N:    provides a changelog, it should be accessible as
N:    /usr/share/doc/<pkg>/changelog.gz.
N:    
N:    It's currently unclear how best to handle multiple binary packages from
N:    the same source. Some maintainers put a copy of the upstream changelog
N:    in each package, but it can be quite long. Some include it in one
N:    package and add symlinks to the other packages, but this requires there
N:    be dependencies between the packages. Some only include it in a
N:    "central" binary package and omit it from more ancillary packages.
N:    
N:    Refer to Debian Policy Manual section 12.7 (Changelog files) for
N:    details.
N:    
N:    Severity: pedantic, Certainty: wild-guess
N:    
N:    Check: changelog-file, Type: binary
N: 
W: libjai-core-java: hardening-no-relro usr/lib/jni/libmlib_jai.so
N: 
N:    This package provides an ELF binary that lacks the "read-only
N:    relocation" link flag. This package was likely not built with the
N:    default Debian compiler flags defined by dpkg-buildflags. If built using
N:    dpkg-buildflags directly, be sure to import LDFLAGS.
N:    
N:    Refer to http://wiki.debian.org/Hardening for details.
N:    
N:    Severity: normal, Certainty: certain
N:    
N:    Check: binaries, Type: binary, udeb
N: 
W: libjai-core-java: hardening-no-fortify-functions usr/lib/jni/libmlib_jai.so
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: possible
N:    
N:    Check: binaries, Type: binary, udeb
N: 
P: libjai-core-java: no-upstream-changelog