Lintian v2.116.3 Options: -i -I -E --pedantic --profile debian N: W: libcleri source: debhelper-but-no-misc-depends libcleri-dev N: N: The source package uses debhelper, but it does not include ${misc:Depends} N: in the given binary package's debian/control entry. Any debhelper command N: may add dependencies to ${misc:Depends} that are required for the work N: that it does, so recommended best practice is to always add N: ${misc:Depends} to the dependencies of each binary package if debhelper is N: in use. N: N: Please refer to the debhelper(7) manual page for details. N: N: Visibility: warning N: Show-Always: no N: Check: debhelper N: N: W: libcleri source: debhelper-but-no-misc-depends libcleri1 N: I: libcleri source: debug-package-for-multi-arch-same-pkg-not-coinstallable libcleri1-dbgsym => libcleri1 N: N: The debug package appear to be containing debug symbols for a "Multi-Arch: N: same" package, but the debug package itself is not "Multi-Arch: same". If N: so, it is not possible to have the debug symbols for all architecture N: variants of the binaries available at the same time. N: N: Making a debug package co-installable with itself is very trivial, when N: installing the debug symbols beneath: N: /usr/lib/debug/.build-id//.debug N: N: dh_strip does this in debhelper compat 9. Otherwise, the expected location N: of the debug symbols of a given ELF binary can be determined by using: N: N: readelf -n | \ N: perl -ne 'print if s,^\s*Build ID:\s*(\S\S)(\S+),/usr/lib/debug/.build-id/$1/$2.debug,' N: N: Visibility: info N: Show-Always: no N: Check: group-checks N: N: I: libcleri source: out-of-date-standards-version 4.5.0 (released 2020-01-20) (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: X: libcleri source: debian-watch-does-not-check-openpgp-signature [debian/watch] N: N: This watch file does not specify a means to verify the upstream tarball N: using a cryptographic signature. N: N: If upstream distributions provides such signatures, please use the N: pgpsigurlmangle options in this watch file's opts= to generate the URL of N: an upstream OpenPGP signature. This signature is automatically downloaded N: and verified against a keyring stored in debian/upstream/signing-key.asc N: N: Of course, not all upstreams provide such signatures but you could request N: them as a way of verifying that no third party has modified the code after N: its release (projects such as phpmyadmin, unrealircd, and proftpd have N: suffered from this kind of attack). N: N: Please refer to the uscan(1) manual page for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/watch N: Renamed from: debian-watch-does-not-check-gpg-signature N: debian-watch-may-check-gpg-signature N: This tag is experimental. N: N: X: libcleri source: prefer-uscan-symlink filenamemangle s%v?@ANY_VERSION@%@PACKAGE@-$1.tar.xz% [debian/watch:5] N: N: Please consider setting USCAN_SYMLINK=rename in your ~/.devscripts N: configuration file instead of using the option filenamemangle in N: debian/watch. N: N: Please check with your team before making changes to sources you maintain N: together. There are circumstances when the filenamemangle option is N: better. N: N: Please refer to the uscan(1) manual page for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: debian/watch N: This tag is experimental. N: N: X: libcleri source: update-debian-copyright 2017 vs 2024 [debian/copyright:8] 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: libcleri source: very-long-line-length-in-source-file 522 > 512 [README.md:273] 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: