Lintian v2.127.0
Options: -i -I -E --pedantic --profile debian

N:
W: tvm-ffi source: changelog-file-missing-explicit-entry 0.1.12-2 -> 0.1.12-3 (missing) -> 0.1.12-3.1 [debian/changelog:1]
N: 
N:   The latest changelog file for this package specifies a version in the form
N:   of 1.2-3+deb8u1, 1.2-3+nmu4 (or similar) but this does not follow from a
N:   corresponding 1.2-3 changelog stanza.
N:   
N:   This suggests that changes were merged into a single entry. This is
N:   suboptimal as it makes it more difficult for users to determine which
N:   upload fixed a particular bug.
N: 
N:   Please refer to Preparing packages to address security issues (Section
N:   5.8.5.4) in the Debian Developer's Reference, NMUs and debian/changelog
N:   (Section 5.11.2) in the Debian Developer's Reference, Direct updates to
N:   testing (Section 5.14.3) in the Debian Developer's Reference, and
N:   Bug#916877 for details.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: debian/changelog
N: 
N:
W: tvm-ffi source: maintainer-upload-has-incorrect-version-number 0.1.12-3.1 [debian/changelog:1]
N: 
N:   A maintainer upload should have a Debian revision without dots. Revisions
N:   with dots are reserved for Non-Maintainer Uploads (NMUs). If you do a
N:   maintainer-upload with dots a potential NMU'er has problems choosing a
N:   correct version number.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: nmu
N: 
N:
W: python3-tvm-ffi: no-manual-page [usr/bin/tvm-ffi-config]
N: 
N:   Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should have
N:   a manual page
N:   
N:   Note that though the man program has the capability to check for several
N:   program names in the NAMES section, each of these programs should have its
N:   own manual page (a symbolic link to the appropriate manual page is
N:   sufficient) because other manual page viewers such as xman or tkman don't
N:   support this.
N:   
N:   If the name of the manual page differs from the binary by case, man may be
N:   able to find it anyway; however, it is still best practice to match the
N:   exact capitalization of the executable in the manual page.
N:   
N:   If the manual pages are provided by another package on which this package
N:   depends, Lintian may not be able to determine that manual pages are
N:   available. In this case, after confirming that all binaries do have manual
N:   pages after this package and its dependencies are installed, please add a
N:   Lintian override.
N: 
N:   Please refer to Manual pages (Section 12.1) in the Debian Policy Manual
N:   for details.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: documentation/manual
N:   Renamed from: binary-without-manpage
N: 
N:
W: python3-tvm-ffi: no-manual-page [usr/bin/tvm-ffi-stubgen]
N:
W: python3-tvm-ffi: package-contains-vcs-control-file [usr/lib/python3/dist-packages/tvm_ffi/.gitignore]
N: 
N:   The package contains a VCS control file such as .(cvs|git|hg)ignore. Files
N:   such as these are used by revision control systems to, for example,
N:   specify untracked files it should ignore or inventory files. This file is
N:   generally useless in an installed package and was probably installed by
N:   accident.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: files/vcs
N: 
N:
W: libtvm-ffi-dev: possible-unindented-list-in-extended-description line 9
N: 
N:   The package "Description:" contains an unindented line which starts with a
N:   dash (-) or asterisk (*). If this was meant to be a list of items these
N:   lines need to be indented (dselect would word-wrap these lines otherwise).
N: 
N:   Please refer to Description (Section 5.6.13) in the Debian Policy Manual
N:   for details.
N: 
N:   Visibility: warning
N:   Show-Always: no
N:   Check: fields/description
N: 
N:
W: libtvm-ffi0: possible-unindented-list-in-extended-description line 9
N:
W: python3-tvm-ffi: possible-unindented-list-in-extended-description line 9
N:
I: python3-tvm-ffi: capitalization-error-in-description-synopsis python Python
N: 
N:   Lintian found a possible capitalization error in the package synopsis.
N:   Lintian has a list of common capitalization errors, primarily of upstream
N:   projects, that it looks for. It does not have a dictionary like a spelling
N:   checker does.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/description
N: 
N:
I: tvm-ffi 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 and
N:   the Debian External Health Status project, please consider adding a
N:   debian/watch file containing only comments documenting the situation.
N: 
N:   Please refer to Upstream source location: debian/watch (Section 4.11) in
N:   the Debian Policy Manual and the uscan(1) manual page for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/watch
N: 
N:
I: libtvm-ffi0: hardening-no-bindnow [usr/lib/libtvm_ffi.so.0]
N: 
N:   This package provides an ELF binary that lacks the "bindnow" linker flag.
N:   
N:   This is needed (together with "relro") to make the "Global Offset Table"
N:   (GOT) fully read-only. The bindnow feature trades startup time for
N:   improved security. Please consider enabling this feature or consider
N:   overriding the tag (possibly with a comment about why).
N:   
N:   If you use dpkg-buildflags, you may have to add hardening=+bindnow or
N:   hardening=+all to DEB_BUILD_MAINT_OPTIONS.
N:   
N:   The relevant compiler flags are set in LDFLAGS.
N: 
N:   Please refer to https://wiki.debian.org/Hardening for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: binaries/hardening
N: 
N:
I: libtvm-ffi0: hardening-no-bindnow [usr/lib/libtvm_ffi_testing.so.0]
N:
I: python3-tvm-ffi: hardening-no-bindnow [usr/lib/python3/dist-packages/tvm_ffi/core.abi3-x86_64-linux-gnu.so]
N:
I: libtvm-ffi0: no-symbols-control-file usr/lib/libtvm_ffi.so.0
N: 
N:   Although the package includes a shared library, the package does not have
N:   a symbols control file.
N:   
N:   dpkg can use symbols files in order to generate more accurate library
N:   dependencies for applications, based on the symbols from the library that
N:   are actually used by the application.
N: 
N:   Please refer to the dpkg-gensymbols(1) manual page and
N:   https://wiki.debian.org/UsingSymbolsFiles for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/shlibs
N: 
N:
I: libtvm-ffi0: no-symbols-control-file usr/lib/libtvm_ffi_testing.so.0
N:
I: tvm-ffi source: out-of-date-standards-version 4.6.2 (released 2022-12-17) (current is 4.7.2)
N: 
N:   The source package refers to a Standards-Version older than the one that
N:   was current at the time the package was created (according to the
N:   timestamp of the latest debian/changelog entry). Please consider updating
N:   the package to current Policy and setting this control field
N:   appropriately.
N:   
N:   If the package is already compliant with the current standards, you don't
N:   have to re-upload the package just to adjust the Standards-Version control
N:   field. However, please remember to update this field next time you upload
N:   the package.
N:   
N:   See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
N:   debian-policy package for a summary of changes in newer versions of
N:   Policy.
N: 
N:   Please refer to
N:   https://www.debian.org/doc/debian-policy/upgrading-checklist.html for
N:   details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/standards-version
N: 
N:
I: python3-tvm-ffi: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/tvm_ffi/CMakeLists.txt]
N: 
N:   This package ships a documentation file outside /usr/share/doc
N:   Documentation files are normally installed inside /usr/share/doc.
N:   
N:   If this file doesn't describe the contents or purpose of the directory it
N:   is in, please consider moving this file to /usr/share/doc/ or maybe even
N:   removing it. If this file does describe the contents or purpose of the
N:   directory it is in, please add a lintian override.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: documentation
N: 
N:   Screen: python/egg/metadata
N:     Advocates: "Scott Kitterman" <debian@kitterman.com>
N:     Reason: The folders XXX.dist-info/ and XXX.egg-info/ hold metadata for
N:             Python modules. Those files are not documentation even though
N:             some of their names carry the .txt file extension.
N:             
N:             Python modules can be both public and private.
N:             
N:             Read more in
N:             https://www.python.org/dev/peps/pep-0427/#the-dist-info-directory,
N:             https://www.python.org/dev/peps/pep-0376/#id16,
N:             https://www.python.org/dev/peps/pep-0610/,
N:             https://www.python.org/dev/peps/pep-0639/,
N:             https://setuptools.pypa.io/en/latest/deprecated/python_eggs.html,
N:             and Bug#1003913.
N: 
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/add-soversion.patch]
N: 
N:   quilt patch files should start with a description of patch. All lines
N:   before the start of the patch itself are considered part of the
N:   description. You can edit the description with quilt header -e when the
N:   patch is at the top of the stack.
N:   
N:   As well as a description of the purpose and function of the patch, the
N:   description should ideally contain author information, a URL for the bug
N:   report (if any), Debian or upstream bugs fixed by it, upstream status, the
N:   Debian version and date the patch was first included, and any other
N:   information that would be useful if someone were investigating the patch
N:   and underlying problem. Please consider using the DEP 3 format for this
N:   information.
N: 
N:   Please refer to https://dep-team.pages.debian.net/deps/dep3/ for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/patches/quilt
N: 
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/remove-3rdparty-from-sdist.patch]
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/remove-libbacktrace-install.patch]
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/search-system-lib.patch]
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/use-debian-dlpack.patch]
N:
I: tvm-ffi source: quilt-patch-missing-description [debian/patches/use-system-libbacktrace.patch]
N:
P: tvm-ffi source: package-does-not-install-examples [addons/tvm_ffi_orcjit/examples/]
N: 
N:   The original source tarball contains the specified examples directory.
N:   However, no examples are installed in any binary packages.
N:   
N:   Please use dh_installexamples to install these to the most relevant
N:   package, for example by adding the directory name followed by a wildcard
N:   to a debian/pkgname.examples file.
N:   
N:   Lintian looks for any directory called examples under /usr/share/doc in
N:   all binary packages.
N: 
N:   Please refer to the dh_installexamples(1) manual page for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: examples
N: 
N:   Screen: examples/in-tests
N:     Advocates: "Scott Kitterman" <debian@kitterman.com>
N:     Reason: 
N:             Some sources like python-tomlkit trigger this tag for tests because of files
N:             in ./tests/examples/. They are not examples for tomlkit, however. They are
N:             examples of TOML files used in the tests.
N:             
N:             Overall, the check is probably better off not looking in test
N:             directories.
N:             
N:             Read more in Bug#1005184.
N: 
N:
P: tvm-ffi source: package-does-not-install-examples [examples/]
N:
P: tvm-ffi source: package-does-not-install-examples [rust/tvm-ffi/examples/]
N:
P: python3-tvm-ffi: repeated-path-segment tvm_ffi [usr/lib/python3/dist-packages/tvm_ffi/share/cmake/tvm_ffi/]
N: 
N:   The file is installed into a location that repeats the given path segment.
N:   An example would be /usr/lib/lib or /usr/share/myprogram/share.
N:   
N:   More often than not this is unintended.
N: 
N:   Please refer to Bug#950052 and Bug#950027 for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/hierarchy/path-segments
N: 
N:
X: python3-tvm-ffi: application-in-library-section python [usr/bin/tvm-ffi-config]
N: 
N:   This package contains a binary in $PATH but is in a section just thought
N:   for libraries. It likely should be in another section like e.g. utils,
N:   text, devel, misc, etc., but not in e.g. perl, ruby or python.
N:   
N:   People tend to skip these package sections when looking for applications
N:   in the package list and hence wouldn't notice this package.
N:   
N:   In case the program in $PATH is only a helper tool and the package is
N:   primarily a library, please add a Lintian override for this tag.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: application-not-library
N:   This tag is experimental.
N: 
N:
X: python3-tvm-ffi: application-in-library-section python [usr/bin/tvm-ffi-stubgen]
N:
X: libtvm-ffi0: exit-in-shared-library [usr/lib/libtvm_ffi.so.0]
N: 
N:   The listed shared library calls the C library exit() or _exit() functions.
N:   
N:   In the case of an error, the library should instead return an appropriate
N:   error code to the calling program which can then determine how to handle
N:   the error, including performing any required clean-up.
N:   
N:   In most cases, removing the call should be discussed with upstream,
N:   particularly as it may produce an ABI change.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: libraries/shared/exit
N:   Renamed from: shlib-calls-exit
N:   This tag is experimental.
N: 
N:
X: python3-tvm-ffi: library-package-name-for-application [usr/bin/tvm-ffi-config]
N: 
N:   This package contains a program in $PATH but is named like a library. E.g.
N:   instead of libfoo-bar-perl it should be named just foo-bar.
N:   
N:   People tend to skip library-like named packages when looking for
N:   applications in the package list and hence wouldn't notice this package.
N:   See the reference for some (not perl-specific) reasoning.
N:   
N:   In case the program in $PATH is only a helper tool and the package is
N:   primarily a library, please add a Lintian override for this tag.
N: 
N:   Please refer to
N:   https://perl-team.pages.debian.net/policy.html#Package_Naming_Policy for
N:   details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: application-not-library
N:   This tag is experimental.
N: 
N:
X: python3-tvm-ffi: library-package-name-for-application [usr/bin/tvm-ffi-stubgen]
N:
X: libtvm-ffi0: spelling-error-in-binary overriden overridden [usr/lib/libtvm_ffi.so.0]
N: 
N:   Lintian found a spelling error in the given binary. Lintian has a list of
N:   common misspellings that it looks for. It does not have a dictionary like
N:   a spelling checker does.
N:   
N:   If the string containing the spelling error is translated with the help of
N:   gettext or a similar tool, please fix the error in the translations as
N:   well as the English text to avoid making the translations fuzzy. With
N:   gettext, for example, this means you should also fix the spelling mistake
N:   in the corresponding msgids in the *.po files.
N:   
N:   You can often find the word in the source code by running:
N:   
N:    grep -rw <word> <source-tree>
N:   
N:   This tag may produce false positives for words that contain non-ASCII
N:   characters due to limitations in strings.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: binaries/spelling
N:   This tag is experimental.
N: 
N:
X: tvm-ffi source: upstream-metadata-file-is-missing
N: 
N:   This source package is not Debian-native but it does not have a
N:   debian/upstream/metadata file.
N:   
N:   The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to
N:   collect meta-information about upstream projects from any source package.
N:   This file is in YAML format and it is used in to feed the data in the
N:   UltimateDebianDatabase. For example, it can contains the way the authors
N:   want their software be cited in publications and some bibliographic
N:   references about the software.
N:   
N:   Please add a debian/upstream/metadata file.
N: 
N:   Please refer to https://dep-team.pages.debian.net/deps/dep12/ and
N:   https://wiki.debian.org/UpstreamMetadata for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/upstream/metadata
N:   This tag is experimental.
N: