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

N:
P: bleachbit source: maintainer-manual-page [debian/bleachbit.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:
X: bleachbit source: update-debian-copyright 2019 vs 2024 [debian/copyright:60]
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: bleachbit 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: bleachbit source: very-long-line-length-in-source-file 634 > 512 [tests/TestSpecial.py:142]
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: