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

N:
E: libblis4-openmp: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis.so.4) [symbols]
N: 
N:   Debian revisions should be stripped from versions in symbols files. Not
N:   doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo <<
N:   1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't be stripped
N:   because the symbol really appeared between two specific Debian revisions,
N:   you should postfix the version with a single "~" (example: 1.0-3~ if the
N:   symbol appeared in 1.0-3).
N:   
N:   This problem normally means that the symbols were added automatically by
N:   dpkg-gensymbols. dpkg-gensymbols uses the full version number for the
N:   dependency associated to any new symbol that it detects. The maintainer
N:   must update the debian/<package>.symbols file by adding the new symbols
N:   with the corresponding upstream version.
N: 
N:   Visibility: error
N:   Show-Always: no
N:   Check: debian/shlibs
N: 
N:
E: libblis4-pthread: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis.so.4) [symbols]
N:
E: libblis4-serial: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis.so.4) [symbols]
N:
E: libblis64-4-openmp: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis64.so.4) [symbols]
N:
E: libblis64-4-pthread: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis64.so.4) [symbols]
N:
E: libblis64-4-serial: symbols-file-contains-current-version-with-debian-revision on symbol bli_rntm_factorize@Base and 4 others (libblis64.so.4) [symbols]
N:
I: libblis-dev: arch-dep-package-has-big-usr-share 13628kB 100%
N: 
N:   The package has a significant amount of architecture-independent data
N:   (over 4MB, or over 2MB and more than 50% of the package) in /usr/share but
N:   is an architecture-dependent package. This is wasteful of mirror space and
N:   bandwidth since it means distributing multiple copies of this data, one
N:   for each architecture.
N:   
N:   If the data in /usr/share is not architecture-independent, this is a
N:   Policy violation that should be fixed by moving the data elsewhere
N:   (usually /usr/lib).
N: 
N:   Please refer to Section 6.7.5 of the Debian Developer's Reference for
N:   details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: huge-usr-share
N: 
N:
I: libblis64-dev: arch-dep-package-has-big-usr-share 13628kB 100%
N:
I: libblis-openmp-dev: file-references-package-build-path [usr/share/blis-openmp-powerpc64le-linux-gnu/config.mk]
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: libblis-pthread-dev: file-references-package-build-path [usr/share/blis-pthread-powerpc64le-linux-gnu/config.mk]
N:
I: libblis-serial-dev: file-references-package-build-path [usr/share/blis-serial-powerpc64le-linux-gnu/config.mk]
N:
I: libblis64-openmp-dev: file-references-package-build-path [usr/share/blis64-openmp-powerpc64le-linux-gnu/config.mk]
N:
I: libblis64-pthread-dev: file-references-package-build-path [usr/share/blis64-pthread-powerpc64le-linux-gnu/config.mk]
N:
I: libblis64-serial-dev: file-references-package-build-path [usr/share/blis64-serial-powerpc64le-linux-gnu/config.mk]
N:
I: libblis4-openmp: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-openmp/libblas.so.3]
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: libblis4-openmp: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-openmp/libblis.so.4]
N:
I: libblis4-pthread: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-pthread/libblas.so.3]
N:
I: libblis4-pthread: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-pthread/libblis.so.4]
N:
I: libblis4-serial: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-serial/libblas.so.3]
N:
I: libblis4-serial: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis-serial/libblis.so.4]
N:
I: libblis64-4-openmp: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-openmp/libblas64.so.3]
N:
I: libblis64-4-openmp: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-openmp/libblis64.so.4]
N:
I: libblis64-4-pthread: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-pthread/libblas64.so.3]
N:
I: libblis64-4-pthread: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-pthread/libblis64.so.4]
N:
I: libblis64-4-serial: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-serial/libblas64.so.3]
N:
I: libblis64-4-serial: hardening-no-fortify-functions [usr/lib/powerpc64le-linux-gnu/blis64-serial/libblis64.so.4]
N:
I: blis source: out-of-date-standards-version 4.4.1 (released 2019-09-29) (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:
P: libblis-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N: 
N:   A punction mark was placed oddly in the description.
N:   
N:   This tag is currently only issued for a comma that is not followed by a
N:   whitespace character or a number (eg. for "300,000").
N: 
N:   Please refer to Bug#591665 and Bug#591664 for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: fields/description
N: 
N:
P: libblis-openmp-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis-pthread-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis-serial-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis4: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis4-openmp: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis4-pthread: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis4-serial: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-4: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-4-openmp: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-4-pthread: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-4-serial: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-openmp-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-pthread-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
P: libblis64-serial-dev: odd-mark-in-description comma not followed by whitespace (synopsis)
N:
X: blis 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: libblis4-openmp: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-openmp/libblas.so.3]
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: libblis4-openmp: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-openmp/libblis.so.4]
N:
X: libblis4-pthread: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-pthread/libblas.so.3]
N:
X: libblis4-pthread: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-pthread/libblis.so.4]
N:
X: libblis4-serial: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-serial/libblas.so.3]
N:
X: libblis4-serial: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis-serial/libblis.so.4]
N:
X: libblis64-4-openmp: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-openmp/libblas64.so.3]
N:
X: libblis64-4-openmp: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-openmp/libblis64.so.4]
N:
X: libblis64-4-pthread: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-pthread/libblas64.so.3]
N:
X: libblis64-4-pthread: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-pthread/libblis64.so.4]
N:
X: libblis64-4-serial: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-serial/libblas64.so.3]
N:
X: libblis64-4-serial: exit-in-shared-library [usr/lib/powerpc64le-linux-gnu/blis64-serial/libblis64.so.4]
N:
X: libblis-dev: package-contains-no-arch-dependent-files
N: 
N:   All files in this package are architecture-independent, but the package is
N:   not marked Architecture: all.
N:   
N:   The package should probably be marked Architecture: all.
N: 
N:   Please refer to Architecture (Section 5.6.8) in the Debian Policy Manual
N:   for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: files/architecture
N:   This tag is experimental.
N: 
N:
X: libblis64-dev: package-contains-no-arch-dependent-files
N:
X: blis source: prefer-uscan-symlink filenamemangle s/.+\/v?(\d\S+)\.tar\.gz/blis-$1\.tar\.gz/ [debian/watch:3]
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: blis source: update-debian-copyright 2020 vs 2026 [debian/copyright:12]
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: blis source: very-long-line-length-in-source-file 1039 > 512 [docs/PluginHowTo.md:172]
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" <rra@debian.org>
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: blis source: very-long-line-length-in-source-file 1053 > 512 [docs/Multithreading.md:366]
N:
X: blis source: very-long-line-length-in-source-file 1267 > 512 [docs/KernelsHowTo.md:337]
N:
X: blis source: very-long-line-length-in-source-file 1533 > 512 [docs/ConfigurationHowTo.md:531]
N:
X: blis source: very-long-line-length-in-source-file 576 > 512 [test/sup/octave/runthese.m:23]
N:
X: blis source: very-long-line-length-in-source-file 579 > 512 [docs/Performance.md:430]
N:
X: blis source: very-long-line-length-in-source-file 614 > 512 [docs/CodingConventions.md:147]
N:
X: blis source: very-long-line-length-in-source-file 720 > 512 [config/altra/QuickStart/blis_setenv.sh:87]
N:
X: blis source: very-long-line-length-in-source-file 781 > 512 [docs/FAQ.md:70]
N:
X: blis source: very-long-line-length-in-source-file 786 > 512 [docs/ReleaseNotes.md:988]
N:
X: blis source: very-long-line-length-in-source-file 823 > 512 [docs/Testsuite.md:169]
N:
X: blis source: very-long-line-length-in-source-file 866 > 512 [docs/BLISTypedAPI.md:51]
N:
X: blis source: very-long-line-length-in-source-file 873 > 512 [CHANGELOG:678]
N:
X: blis source: very-long-line-length-in-source-file 892 > 512 [docs/BLISObjectAPI.md:56]
N:
X: blis source: very-long-line-length-in-source-file 922 > 512 [docs/BuildSystem.md:186]
N:
X: blis source: very-long-line-length-in-source-file 945 > 512 [config/altramax/QuickStart/blis_setenv.sh:72]
N:
X: blis source: very-long-line-length-in-source-file 961 > 512 [docs/HardwareSupport.md:18]