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/tellico
W
package-relation-with-self
breaks: tellico-trinity (<< 4:14.0.0~)
W
spelling-error-in-description
softwares software
W
unknown-section
tde
C
control-tarball-compression-format
xz
C
ctrl-script
postinst
postrm
C
data-tarball-compression-format
xz
C
debhelper-autoscript-in-maintainer-scripts
dh_installmenu/12.10ubuntu1
C
maintainer-script-interpreter
control/postinst /bin/sh
control/postrm /bin/sh
C
package-is-maintained-by-individual
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.
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.
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
tellico-trinity_14.2.0~pre61-0ubuntu20.04.0+7.dsc
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
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.0)
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.2.0~pre61-0ubuntu20.04.0+7
W
debhelper-but-no-misc-depends
tellico-data-trinity
tellico-scripts-trinity
tellico-trinity
W
debian-source-options-has-custom-compression-settings
compression = "xz" (line 2)
compression-level = 9 (line 3)
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
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
I
testsuite-autopkgtest-missing
This package does not declare a test suite.
Having a test suite aids with automated quality assurance of the archive
outside of your package. For example, if your package has a test suite
it is possible to re-run that test suite when any of your package's
dependencies have a new version and check whether that update causes
problems for your package.
In addition, since May 2018 these tests now influence migration from
unstable to testing:
https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html
Please add a debian/tests/control file to your package to declare a
testsuite, but please make sure to only add autopkgtests if they provide
meaningful coverage of your package.
Refer to https://ci.debian.net/doc/ for details.
Severity: info
Check: testsuite
Lintian did not output a note for this tag
P
file-contains-trailing-whitespace
debian/changelog (line 189)
debian/changelog (line 263)
debian/changelog (line 337)
debian/changelog (line 482)
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
Lintian did not output a note for this tag
P
package-uses-old-debhelper-compat-version
The debhelper compatibility version used by this package is marked as
not recommended by the debhelper developer. You may consider using a
recommended compatibility version.
The compatibility version can be set by specifying debhelper-compat (=
12) in your package's Build-Depends, by the legacy debian/compat file or
even by setting and exporting DH_COMPAT in debian/rules. If it is not
set in either place, debhelper defaults to the deprecated compatibility
version 1.
Refer to the debhelper(7) manual page for details.
Severity: pedantic
Check: debhelper
10
P
rules-requires-root-missing
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
Lintian did not output a note for this tag
X
maybe-not-arch-all-binnmuable
Tag to attempt to measure the number of packages that might have an
issue with arch:all binNMUs.
At this time, please do <not> attempt to "fix" the problem. It is not
clear what the solution is (if any at all), nor is it clear that this is
something that will or should be supported.
Severity: pedantic
Check: debian/version-substvars
This tag is experimental. Please file a bug report if the tag seems
wrong.
tellico-trinity -> tellico-data-trinity
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. Please file a bug report if the tag seems
wrong.
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, debhelper
C
package-is-maintained-by-individual
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: patch-systems
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.