Lintian v2.116.3 Options: -i -I -E --pedantic --profile debian N: E: kbuild source: source-is-missing [kBuild/doc/QuickReference-kmk.html] N: N: The source of the following file is missing. Lintian checked a few N: possible paths to find the source, and did not find it. N: N: Please repack your package to include the source or add it to N: "debian/missing-sources" directory. N: N: Please note, that very-long-line-length-in-source-file tagged files are N: likely tagged source-is-missing. It is a feature not a bug. N: N: Visibility: error N: Show-Always: no N: Check: files/source-missing N: N: W: kbuild: no-manual-page [usr/bin/bld_signames] 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: kbuild: no-manual-page [usr/bin/kmk_touch] N: W: kbuild source: source-contains-prebuilt-windows-binary [src/lib/kStuff/kLdr/testcase/bin/tst-3.dll.win.x86] N: N: The source tarball contains a prebuilt binary for Microsoft Windows. They N: are usually provided for the convenience of users. These files usually N: just take up space in the tarball. N: N: However, they may be a DFSG violation in that the corresponding source and N: build system are not available. N: N: Check if upstream also provides source-only tarballs that you can use as N: the upstream distribution instead. If not, you may want to ask upstream to N: provide source-only tarballs. N: N: Visibility: warning N: Show-Always: no N: Check: files/source-missing N: N: I: kbuild 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: kbuild: file-references-package-build-path [usr/bin/kmk] N: N: The listed file or maintainer script appears to reference the build path N: used to build the package as specified in the Build-Path field of the N: .buildinfo file. N: N: This is likely to cause the package to be unreproducible, but it may also N: indicate that the package will not work correctly outside of the N: maintainer's own system. N: N: Please note that this tag will not appear unless the .buildinfo file N: contains a Build-Path field. That field is optional. You may have to set N: DEB_BUILD_OPTIONS=buildinfo=+path or use N: --buildinfo-option=--always-include-path with dpkg-buildpackage when N: building. N: N: Please refer to https://reproducible-builds.org/, N: https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, and the N: dpkg-genbuildinfo(1) manual page for details. N: N: Visibility: info N: Show-Always: no N: Check: files/contents N: N: I: kbuild: file-references-package-build-path [usr/bin/kmk_gmake] N: I: kbuild: hardening-no-bindnow [usr/bin/bld_signames] 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: kbuild: hardening-no-bindnow [usr/bin/kDepIDB] N: I: kbuild: hardening-no-bindnow [usr/bin/kDepObj] N: I: kbuild: hardening-no-bindnow [usr/bin/kDepPre] N: I: kbuild: hardening-no-bindnow [usr/bin/kObjCache] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_append] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_ash] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_cat] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_chmod] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_cmp] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_cp] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_echo] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_expr] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_gmake] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_install] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_ln] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_md5sum] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_mkdir] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_mv] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_printf] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_redirect] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_rm] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_rmdir] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_sed] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_sleep] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_test] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_time] N: I: kbuild: hardening-no-bindnow [usr/bin/kmk_touch] N: I: kbuild: hardening-no-fortify-functions [usr/bin/bld_signames] 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 by N: any routines, all unfortified calls have already been fully validated at N: compile-time, or the package was not built with the default Debian N: compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags N: directly, be sure to import CPPFLAGS. N: N: NB: Due to false-positives, Lintian ignores some unprotected functions N: (e.g. memcpy). N: N: Please refer to https://wiki.debian.org/Hardening and Bug#673112 for N: details. N: N: Visibility: info N: Show-Always: no N: Check: binaries/hardening N: N: I: kbuild: hardening-no-fortify-functions [usr/bin/kDepIDB] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kDepObj] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kDepPre] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kObjCache] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_append] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_ash] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_cat] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_chmod] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_cmp] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_cp] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_echo] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_expr] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_gmake] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_install] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_ln] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_md5sum] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_mkdir] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_mv] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_printf] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_redirect] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_rm] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_rmdir] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_sed] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_sleep] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_test] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_time] N: I: kbuild: hardening-no-fortify-functions [usr/bin/kmk_touch] N: I: kbuild source: missing-explanation-for-repacked-upstream-tarball [debian/copyright:1] N: N: The version of this package contains dfsg, ds, or debian which normally N: indicates that the upstream source has been repackaged, but there is no N: "Comment" or "Files-Excluded" field in its copyright file which explains N: the reason why. N: N: Please add a comment why this tarball was repacked or add a suitable N: "Files-Excluded" field. N: N: Visibility: info N: Show-Always: no N: Check: debian/copyright/dep5 N: N: I: kbuild source: out-of-date-standards-version 4.6.0 (released 2021-08-18) (current is 4.6.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: kbuild: possible-documentation-but-no-doc-base-registration N: N: The package ships a .html or .pdf file under /usr/share/doc/. Those files N: are usually documentation, but no files are registered in doc-base. N: N: Files in folders named examples are exempt from this tag. N: N: Please refer to Registering Documents using doc-base (Section 9.10) in the N: Debian Policy Manual for details. N: N: Visibility: info N: Show-Always: no N: Check: menus N: N: I: kbuild source: quilt-patch-missing-description [debian/patches/string.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: kbuild: spelling-error-in-binary compatbility compatibility [usr/bin/kmk] 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 N: N: This tag may produce false positives for words that contain non-ASCII N: characters due to limitations in strings. N: N: Visibility: info N: Show-Always: no N: Check: binaries/spelling N: N: I: kbuild: spelling-error-in-binary compatbility compatibility [usr/bin/kmk_touch] N: I: kbuild: spelling-error-in-binary diretory directory [usr/bin/kObjCache] N: I: kbuild: spelling-error-in-binary enviornment environment [usr/bin/kmk] N: I: kbuild: spelling-error-in-binary enviornment environment [usr/bin/kmk_redirect] N: I: kbuild: spelling-error-in-binary hierachy hierarchy [usr/bin/kmk] N: I: kbuild: spelling-error-in-binary hierachy hierarchy [usr/bin/kmk_rm] N: I: kbuild: spelling-error-in-binary minium minimum [usr/bin/kmk_time] N: I: kbuild: spelling-error-in-binary occure occur [usr/bin/kmk] N: I: kbuild: spelling-error-in-binary occured occurred [usr/bin/kObjCache] N: I: kbuild: spelling-error-in-binary recursivly recursively [usr/bin/kmk] N: I: kbuild: spelling-error-in-binary wTH with [usr/bin/kmk] N: I: kbuild: spelling-error-in-binary wTH with [usr/bin/kmk_md5sum] N: P: kbuild source: license-problem-gfdl-non-official-text invariant part is: with no invariant sections, with no front-cover texts, and with no back-cover texts [src/grep/doc/grep.info] N: N: The given source file is licensed under GFDL, but using a non-official N: text for the "no invariant sections" part. N: N: Please ask upstream to always use (case insensitive): with no Invariant N: Sections, no Front-Cover Texts, and no Back-Cover Texts. N: N: Visibility: pedantic N: Show-Always: no N: Check: cruft N: N: P: kbuild source: license-problem-gfdl-non-official-text invariant part is: with no invariant sections, with no front-cover texts, and with no back-cover texts [src/grep/doc/grep.texi] N: P: kbuild source: maintainer-manual-page [debian/manpages/kmk.1] N: N: The maintainer keeps a manual page in ./debian. Please forward the manual N: page upstream and ask them to include in their version control system, and N: in their next release. N: N: If the manual page was already forwarded or rejected, or the upstream is N: gone, please override the tag and annotate it with a suitable comment. N: N: Please refer to social contract item 2, Coordination with upstream N: developers (Section 3.1.4) in the Debian Developer's Reference, and N: Changes to the upstream sources (Section 4.3) in the Debian Policy Manual N: for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/manual-pages N: Renamed from: maintainer-manpage N: N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-aix.h] N: N: The following file is autogenerated by gperf N: N: They are usually provided for the convenience of users. These files N: usually just take up space in the tarball. N: N: Check if upstream also provides source-only tarballs that you can use as N: the upstream distribution instead. If not, you may want to ask upstream to N: provide source-only tarballs. N: N: Visibility: pedantic N: Show-Always: no N: Check: cruft N: N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-hpux.h] N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-irix.h] N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-osf.h] N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-solaris.h] N: P: kbuild source: source-contains-autogenerated-gperf-data [src/grep/lib/iconv_open-zos.h] N: X: kbuild source: update-debian-copyright 2022 vs 2024 [debian/copyright:49] N: N: The most recent copyright year mentioned for files in ./debian lags behind N: the year in the timestamp for the most recent changelog entry. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/copyright/dep5 N: This tag is experimental. N: N: X: kbuild 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: N: X: kbuild source: very-long-line-length-in-source-file 1040 > 512 [src/lib/kStuff/kLdr/testcase/bin/tst-3.rel.darwin.x86:3] N: N: The source file includes a line length that is well beyond the normally N: human made code line length. N: N: This very long line length does not allow Lintian to do correctly some N: source file checks. N: N: This line could also be the result of some text injected by a computer N: program, and thus could lead to FTBFS bugs. N: N: Last but not least, long line in source code could be used to obfuscate N: the source code and to hide stuff like backdoors or security problems. N: N: It could be due to jslint source comments or other build tool comments. N: N: You may report this issue upstream. N: N: Visibility: pedantic N: Show-Always: no N: Check: files/contents/line-length N: Renamed from: insane-line-length-in-source-file N: This tag is experimental. N: N: Screen: autotools/long-lines N: Advocates: "Russ Allbery" N: Reason: N: Upstream sources using autoconf have traditionally been N: distributed with generated ./configure scripts as well as N: other third-party m4 macro files such as libtool. N: N: When paired with automake, there may also be some intermediate N: Makefile.in files. N: N: A lot of sources potentially contain such files, but they are N: not actionable by either the Debian distributor or by the N: upstream maintainer. N: N: As a side note, modern Debian build protocols will re-create N: many of those files via dh_autoreconf. They are present merely N: to aid in bootstrapping systems where the GNU suite may not yet N: be available. N: N: Read more in Bug#996740. N: N: X: kbuild source: very-long-line-length-in-source-file 10903 > 512 [src/sed/testsuite/madding.sed:8] N: X: kbuild source: very-long-line-length-in-source-file 1283 > 512 [src/kWorker/kWorker.c:14097] N: X: kbuild source: very-long-line-length-in-source-file 1299 > 512 [src/sed/configure:314] N: X: kbuild source: very-long-line-length-in-source-file 1916 > 512 [src/lib/kStuff/kLdr/testcase/bin/tst-3.dll.win.x86:9] N: X: kbuild source: very-long-line-length-in-source-file 3615 > 512 [kBuild/doc/QuickReference-kmk.html:1484] N: X: kbuild source: very-long-line-length-in-source-file 517 > 512 [src/lib/kStuff/kProfiler2/kPrf2WinApiWrappers-kernel32.h:5393] N: X: kbuild source: very-long-line-length-in-source-file 5447 > 512 [src/sed/testsuite/madding.inp:1] N: X: kbuild source: very-long-line-length-in-source-file 5453 > 512 [src/sed/testsuite/madding.good:1] N: X: kbuild source: very-long-line-length-in-source-file 584 > 512 [SlickEdit/user.vlx:8] N: X: kbuild source: very-long-line-length-in-source-file 604 > 512 [src/grep/m4/po.m4:409] N: X: kbuild source: very-long-line-length-in-source-file 958 > 512 [src/kmk/build_w32.bat:178]