This package provides an ELF binary that lacks the "read-only
relocation" link flag. This package was likely not built with the
default Debian compiler flags defined by dpkg-buildflags. If built
using dpkg-buildflags directly, be sure to import LDFLAGS.
Refer to https://wiki.debian.org/Hardening for details.
Severity: warning
Check: binaries
opt/trinity/bin/kdirstat
W
package-relation-with-self
The package declares a relationship with itself. This is not very
useful except in the case of a package Conflicting with itself if its
package name doubles as a virtual package.
Severity: warning
Check: fields/package-relations
Breaks: kdirstat-trinity (<< 4:14.0.0~)
I
hardening-no-bindnow
This package provides an ELF binary that lacks the "bindnow" linker
flag.
This is needed (together with "relro") to make the "Global Offset
Table" (GOT) fully read-only. The bindnow feature trades startup time
for improved security. Please consider enabling this feature or
consider overriding the tag (possibly with a comment about why).
If you use dpkg-buildflags, you may have to add hardening=+bindnow or
hardening=+all to DEB_BUILD_MAINT_OPTIONS.
The relevant compiler flags are set in LDFLAGS.
Refer to https://wiki.debian.org/Hardening for details.
Severity: info
Check: binaries
opt/trinity/bin/kdirstat
C
control-tarball-compression-format
xz
C
data-tarball-compression-format
xz
C
mail-contact
This person is a contact in the named group for this package.
Severity: classification
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.
The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.
Severity: classification
Check: fields/vcs
This tag is a classification. There is no issue in your package.
This person is a contact in the named group for this package.
Severity: classification
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.
The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.
Severity: classification
Check: fields/vcs
This tag is a classification. There is no issue in your package.
E
epoch-changed-but-upstream-version-did-not-go-backwards
The previous version of this package had a different version epoch to
the current version but the upstream version did not go "backwards".
For example, the previous package version was "1:1.0-1" and the
current version is "2:2.0-1".
This was likely an accidental bump or addition of an epoch.
Epochs exist to cope with changes to the upstream version numbering
scheme. Whilst they are a powerful tool, increasing or adding an epoch
has many downsides including causing issues with versioned
dependencies, being misleading to users and being aesthetically
unappealing. Whilst they should be avoided, valid reasons to add or
increment the epoch include:
- Upstream changed their versioning scheme in a way that makes the
latest version lower than the previous one.
- You need to permanently revert to a lower upstream version.
Temporary revertions (eg. after an NMU) should use not modify or
introduce an epoch - please use the CURRENT+reallyFORMER until you can
upload the latest version again.
If you are unsure whether you need to increase the epoch for a
package, please consult the debian-devel mailing list.
Severity: error
Check: debian/changelog
2.4.4-1ubuntu0 -> 4:14.1.6~pre2-0raspbian11.0.0+2
E
missing-build-dependency
The package doesn't specify a build dependency on a package that is
used in debian/rules.
Lintian intentionally does not take into account transitive
dependencies. Even if the package build-depends on some package that
in turn depends on the needed package, an explicit build dependency
should be added. Otherwise, a latent bug is created that will appear
without warning if the other package is ever updated to change its
dependencies. Even if this seems unlikely, please always add explicit
build dependencies on every non-essential, non-build-essential package
that is used directly during the build.
Refer to Debian Policy Manual section 4.2 (Package relationships) for
details.
Severity: error
Check: debian/rules
cdbs
W
ancient-standards-version
The source package refers to a Standards-Version that has been
obsolete for more than two years. Please update your package to latest
Policy and set this control field appropriately.
If the package is already compliant with the current standards, you
don't have to re-upload the package just to adjust the
Standards-Version control field. However, please remember to update
this field next time you upload the package.
See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
debian-policy package for a summary of changes in newer versions of
Policy.
Refer to
https://www.debian.org/doc/debian-policy/upgrading-checklist.html for
details.
Severity: warning
Check: fields/standards-version
3.8.4 (released 2010-01-27) (current is 4.5.1)
W
binary-nmu-debian-revision-in-source
The version number of your source package ends in +b and a number or
has a Debian revision containing three parts. These version numbers
are used by binary NMUs and should not be used as the source version.
(The +b form is the current standard; the three-part version number
now obsolete.)
Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation
or binary-only NMU) for details.
Severity: warning
Check: fields/version
4:14.1.6~pre2-0raspbian11.0.0+2
W
custom-compression-in-debian-source-options
compression = "xz" (line 2)
compression-level = 9 (line 3)
W
debhelper-but-no-misc-depends
The source package uses debhelper, but it does not include
${misc:Depends} in the given binary package's debian/control entry.
Any debhelper command may add dependencies to ${misc:Depends} that are
required for the work that it does, so recommended best practice is to
always add ${misc:Depends} to the dependencies of each binary package
if debhelper is in use.
Refer to the debhelper(7) manual page for details.
Severity: warning
Check: debhelper
kdirstat-trinity
W
epoch-change-without-comment
The previous version of this package had a different version epoch
(eg. 2:1.0-1) to the current version but there's no reference to this
in the changelog entry.
Epochs exist to cope with changes to the upstream version numbering
scheme. Whilst they are a powerful tool, increasing or adding an epoch
has many downsides including causing issues with versioned
dependencies, being misleading to users and being aesthetically
unappealing. Whilst they should be avoided, valid reasons to add or
increment the epoch include:
- Upstream changed their versioning scheme in a way that makes the
latest version lower than the previous one.
- You need to permanently revert to a lower upstream version.
Temporary revertions (eg. after an NMU) should use not modify or
introduce an epoch - please use the CURRENT+reallyFORMER until you can
upload the latest version again.
If you are unsure whether you need to increase the epoch for a
package, please consult the debian-devel mailing list.
Lintian looks in this version's changelog entry for the phrase
"epoch".
Severity: warning
Check: debian/changelog
2.4.4-1ubuntu0 -> 4:14.1.6~pre2-0raspbian11.0.0+2
W
no-nmu-in-changelog
When you NMU a package, that fact should be mentioned on the first
line in the changelog entry. Use the words "NMU" or "Non-maintainer
upload" (case insensitive).
Maybe you didn't intend this upload to be a NMU, in that case, please
double-check that the most recent entry in the changelog is
byte-for-byte identical to the maintainer or one of the uploaders. If
this is a local package (not intended for Debian), you can suppress
this warning by putting "local" in the version number or "local
package" on the first line of the changelog entry.
Refer to Debian Developer's Reference section 5.11.3 (Using the
DELAYED/ queue) for details.
Severity: warning
Check: nmu
Renamed from: changelog-should-mention-nmu
Lintian did not output a note for this tag
W
source-nmu-has-incorrect-version-number
A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a
native package). This is to prevent stealing version numbers from the
maintainer.
Maybe you didn't intend this upload to be a NMU, in that case, please
double-check that the most recent entry in the changelog is
byte-for-byte identical to the maintainer or one of the uploaders. If
this is a local package (not intended for Debian), you can suppress
this warning by putting "local" in the version number or "local
package" on the first line of the changelog entry.
Refer to Debian Developer's Reference section 5.11.2 (NMUs and
debian/changelog) for details.
Severity: warning
Check: nmu
4:14.1.6~pre2-0raspbian11.0.0+2
I
debian-watch-file-is-missing
This source package is not Debian-native but it does not have a
debian/watch file. This file is used for automatic detection of new
upstream versions by the Debian External Health Status project and
other project infrastructure. If this package is maintained upstream,
please consider adding a debian/watch file to detect new releases.
If the package is not maintained upstream or if upstream uses a
distribution mechanism that cannot be meaningfully monitored by uscan
and the Debian External Health Status project, please consider adding
a debian/watch file containing only comments documenting the
situation.
Refer to Debian Policy Manual section 4.11 (Optional upstream source
location: debian/watch) and the uscan(1) manual page for details.
Severity: info
Check: debian/watch
Lintian did not output a note for this tag
I
no-dh-sequencer
This package does not use the dh sequencer in debian/rules.
While maintainers may use a variety of build systems, this one is by
far the most popular.
Maintainers are strongly encouraged to use the dh sequencer in new
packages and convert existing ones when appropriate.
Severity: info
Check: debian/rules/dh-sequencer
Lintian did not output a note for this tag
P
no-dep5-copyright
This package does not use a machine-readable debian/copyright file.
This format makes it easier to review licenses and can be easily
parsed by Lintian.
Refer to
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
details.
Severity: pedantic
Check: debian/copyright/dep5
debian/copyright
P
package-uses-old-debhelper-compat-version
This package uses a debhelper compatibility level that is no longer
recommended. Please consider using the recommended level.
For most packages, the best way to set the compatibility level is to
specify debhelper-compat (= X) as a Build-Depends in debian/control.
You can also use the debian/compat file or export DH_COMPAT in
debian/rules.
If no level is selected debhelper defaults to level 1, which is
deprecated.
Refer to the debhelper(7) manual page for details.
Severity: pedantic
Check: debhelper
10
P
silent-on-rules-requiring-root
The debian/control file is missing an explicit Rules-Requires-Root
field.
Traditionally, Debian packages have required root privileges for some
debian/rules target requiring a split between build and binary
targets. This makes the builds slower due to the increased amount of
invocations as well as the overhead of fakeroot itself.
Please specify (eg.) Rules-Requires-Root: no in the debian/control
source stanza, but packagers should verify using diffoscope(1) that
the binaries built with this field present are identical.
Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy
Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and
Debian Policy Manual section 5.6.31 (Rules-Requires-Root) for details.
Severity: pedantic
Check: debian/control
Renamed from: rules-requires-root-missing
Lintian did not output a note for this tag
P
trailing-whitespace
debian/changelog (line 125)
debian/changelog (line 71)
debian/control (line 22)
X
upstream-metadata-file-is-missing
This source package is not Debian-native but it does not have a
debian/upstream/metadata file.
The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an
effort to collect meta-information about upstream projects from any
source package. This file is in YAML format and it is used in to feed
the data in the UltimateDebianDatabase. For example, it can contains
the way the authors want their software be cited in publications and
some bibliographic references about the software.
Please add a debian/upstream/metadata file.
Refer to https://dep-team.pages.debian.net/deps/dep12/ and
https://wiki.debian.org/UpstreamMetadata for details.
Severity: pedantic
Check: debian/upstream/metadata
This tag is experimental.
Lintian did not output a note for this tag
C
debhelper-compat-level
This is the debhelper compat level used specified by this package.
Severity: classification
Check: debhelper
This tag is a classification. There is no issue in your package.
10
C
debian-build-system
This is the build system that Lintian believes the package is using.
Severity: classification
Check: debhelper
This tag is a classification. There is no issue in your package.
cdbs-with-debhelper.mk
C
mail-contact
This person is a contact in the named group for this package.
Severity: classification
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.
The number of patches according to the debian/patches/series file.
Severity: classification
Check: debian/patches/count
This tag is a classification. There is no issue in your package.
The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.
Severity: classification
Check: fields/vcs
This tag is a classification. There is no issue in your package.
Lintian did not output a note for this tag
C
patch-system
This package uses the specified patch system (eg. "quilt" or
"dpatch").
Severity: classification
Check: debian/patches
This tag is a classification. There is no issue in your package.
quilt
C
source-format
This is the source format declared in the package.
Severity: classification
Check: debian/source-dir
This tag is a classification. There is no issue in your package.
3.0 (quilt)
C
standards-version
The standards version of the package according to Standards-Version
field in the debian/control file.
Severity: classification
Check: fields/standards-version
This tag is a classification. There is no issue in your package.