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.
Please refer to https://wiki.debian.org/Hardening for details.
Visibility: warning
Show-Always: no
Check: binaries/hardening
Lintian did not output a note for this tag[opt/trinity/bin/tellico]
W
package-relation-with-self
Breaks: tellico-trinity (<< 4:14.0.0~)
W
unknown-section
tde
I
spelling-error-in-description
softwares software
C
control-tarball-compression-format
zst
C
ctrl-script
postinst
postrm
C
data-tarball-compression-format
zst
C
debhelper-autoscript-in-maintainer-scripts
dh_installmenu/13.6ubuntu1
C
mail-contact
This person is a contact in the named group for this package.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
Check: fields/vcs
This tag is a classification. There is no issue in your package.
I
package-contains-documentation-outside-usr-share-doc
This package ships a documentation file outside /usr/share/doc
Documentation files are normally installed inside /usr/share/doc.
If this file doesn't describe the contents or purpose of the directory it
is in, please consider moving this file to /usr/share/doc/ or maybe even
removing it. If this file does describe the contents or purpose of the
directory it is in, please add a lintian override.
Visibility: info
Show-Always: no
Check: documentation
opt/trinity/share/apps/tellico/welcome.html
I
spelling-error-in-description
softwares software
C
control-tarball-compression-format
zst
C
ctrl-script
postinst
prerm
C
data-tarball-compression-format
zst
C
debhelper-autoscript-in-maintainer-scripts
dh_python3
C
mail-contact
This person is a contact in the named group for this package.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
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.
Visibility: error
Show-Always: no
Check: debian/changelog
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.)
Please refer to Debian Developer's Reference section 5.10.2.1 for details.
Visibility: warning
Show-Always: no
Check: fields/version
4:14.1.6~pre8-0ubuntu22.04.0+1
Comment:
The code in debian/rules requires a prerequisite
that is not presently listed in the package's Build-Depends.
In the special case of Python, affected packages should Build-Depend on
one of python3, python3-all, python3-dev, or python3-all-dev. Which one
depends on whether a package supports multiple Python versions, and also
whether the package builds Python modules or uses Python only as part of
the build process.
Packages that depend on a specific Python version may build-depend on any
appropriate pythonX.Y or pythonX.Y-dev package instead.
The condition you see in the context is not a recommendation on what to
add. If you see a list, more than likely only one member is needed to make
this tag go away. You probably also do not need the :any multiarch
acceptor, if you see one.
Please refer to Debian Policy Manual section 4.2 for details.
Visibility: error
Show-Always: no
Check: debian/rules
Renamed from: missing-build-dependency missing-python-build-dependency
W
custom-compression-in-debian-source-options
compression = "xz" (line 2)
compression-level = 9 (line 3)
W
debhelper-but-no-misc-depends
tellico-data-trinity
tellico-scripts-trinity
tellico-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".
Visibility: warning
Show-Always: no
Check: debian/changelog
A field in debian/control has an extension prefix but is also known
without it.
Extension prefixes like XS-* or XC-* allow experimental fields to
propagate to the right place when packages are built with dpkg. In this
case, however, the field is also known without the prefix. In all
likelihood the field was permanently adopted, and dpkg learned how to deal
with it.
Please consider removing the extension prefix for the field name.
Visibility: info
Show-Always: no
Check: debian/control/field/adopted
Renamed from: xc-package-type-in-debian-control
xs-testsuite-field-in-debian-control xs-vcs-field-in-debian-control
(in section for source) XSBC-Original-Maintainer
[debian/control:5]
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.
Please refer to Debian Policy Manual section 4.11 and the uscan(1) manual
page for details.
Visibility: info
Show-Always: no
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.
Visibility: info
Show-Always: no
Check: debian/rules/dh-sequencer
Lintian did not output a note for this tag
I
out-of-date-standards-version
The source package refers to a Standards-Version older than the one that
was current at the time the package was created (according to the
timestamp of the latest debian/changelog entry). Please consider updating
the package to current Policy and setting 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.
Please refer to
https://www.debian.org/doc/debian-policy/upgrading-checklist.html for
details.
Visibility: info
Show-Always: no
Check: fields/standards-version
3.8.4 (released 2010-01-27) (current is 4.6.0.1)
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.
Please refer to
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
details.
Visibility: pedantic
Show-Always: no
Check: debian/copyright/dep5
Lintian did not output a note for this tag[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.
Please refer to the debhelper(7) manual page for details.
Visibility: pedantic
Show-Always: no
Check: debhelper
10
P
silent-on-rules-requiring-root
The field Rules-Requires-Root is missing from the file debian/control.
Over time, Debian has sucessively narrowed the steps for which elevated
privileges are required. It speeds up the building of installation
packages in the archive. Eventually, Debian will switch the default
archive-wide behaviour to expedite the build process further.
Please declare explicitly that the sources do not require root privileges.
You can use the setting Rules-Requires-Root: no in the source stanza of
debian/control, but please verify with diffoscope(1) that the installation
packages produced are in fact identical.
Please refer to /usr/share/doc/dpkg/rootless-builds.txt.gz, Debian Policy
Manual section 4.9.2, and Debian Policy Manual section 5.6.31 for details.
Visibility: pedantic
Show-Always: no
Check: debian/control/field/rules-requires-root
Renamed from: rules-requires-root-missing
Lintian did not output a note for this tag[debian/control]
P
trailing-whitespace
debian/changelog (line 189)
debian/changelog (line 263)
debian/changelog (line 337)
debian/changelog (line 482)
P
very-long-line-length-in-source-file
doc/en/configuration.docbook line 352 is 794 characters long (>512)
doc/en/details.docbook line 188 is 749 characters long (>512)
doc/en/fundamentals.docbook line 12 is 869 characters long (>512)
doc/en/hacking.docbook line 43 is 555 characters long (>512)
doc/en/importing-exporting.docbook line 46 is 960 characters long (>512)
doc/en/index.docbook line 317 is 615 characters long (>512)
doc/fr/index.docbook line 339 is 615 characters long (>512)
src/rtf2html/rtf_keyword.h line 1 is 4190 characters long (>512)
xslt/MARC21slim2MODS3.xsl line 2515 is 1654 characters long (>512)
xslt/UNIMARC2MODS3.xsl line 2918 is 1654 characters long (>512)
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.
Visibility: classification
Show-Always: no
Check: debian/version-substvars
This tag is experimental.
This tag is a classification. There is no issue in your package.
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.
Please refer to https://dep-team.pages.debian.net/deps/dep12/ and
https://wiki.debian.org/UpstreamMetadata for details.
Visibility: pedantic
Show-Always: no
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.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
Check: debhelper
This tag is a classification. There is no issue in your package.
cdbs-with-debhelper.mk, debhelper
[debian/rules]
C
mail-contact
This person is a contact in the named group for this package.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
Check: debian/patches/count
This tag is a classification. There is no issue in your package.
0
C
package-is-maintained-by-individual
The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.
Visibility: classification
Show-Always: no
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").
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
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.
Visibility: classification
Show-Always: no
Check: fields/standards-version
This tag is a classification. There is no issue in your package.