Lintian did not output a note for this tag[opt/trinity/lib/trinity/libkontact_basket.so]
W
national-encoding
A file is not valid UTF-8.
Debian has used UTF-8 for many years. Support for national encodings is
being phased out. This file probably appears to users in mangled
characters (also called mojibake).
Packaging control files must be encoded in valid UTF-8.
Please convert the file to UTF-8 using iconv or a similar tool.
Visibility: warning
Show-Always: no
Check: files/encoding
Renamed from: national-encoding-in-text-file
debian-changelog-file-uses-obsolete-national-encoding
debian-control-file-uses-obsolete-national-encoding
debian-copyright-file-uses-obsolete-national-encoding
debian-news-file-uses-obsolete-national-encoding
debian-tests-control-uses-national-encoding
doc-base-file-uses-obsolete-national-encoding
national-encoding-in-debconf-template national-encoding-in-manpage
The package has a very long filename. This may complicate shipping the
package on some media that put restrictions on the length of the filenames
(such as CDs).
For architecture dependent packages, the tag is emitted based on the
length of the longest architecture name rather than the name of the
current architecture.
Please refer to
https://lists.debian.org/debian-devel/2011/03/msg00943.html for details.
Visibility: warning
Show-Always: no
Check: archive/file/name/length
Lintian did not output a note for this tag[opt/trinity/lib/trinity/libkontact_basket.so]
I
spelling-error-in-description-synopsis
Lintian found a spelling error in the package synopsis. Lintian has a list
of common misspellings that it looks for. It does not have a dictionary
like a spelling checker does. It is particularly picky about spelling and
capitalization in package descriptions since they're very visible to end
users.
Visibility: info
Show-Always: no
Check: fields/description
The package does not rely on any maintainer scripts (or other executable
control files).
Visibility: classification
Show-Always: no
Check: control-files
This tag is a classification. There is no issue in your package.
The extended description contains a "Homepage" pseudo-field following the
old Developer's Reference recommendation. As of 1.14.6, dpkg now supports
Homepage as a regular field in debian/control. This pseudo-field should be
moved from the extended description to the fields for the relevant source
or binary packages.
Visibility: warning
Show-Always: no
Check: fields/description
line 8
W
description-synopsis-starts-with-article
Lintian did not output a note for this tag
W
hardening-no-relro
Lintian did not output a note for this tag[opt/trinity/bin/basket]
Lintian did not output a note for this tag[opt/trinity/lib/libbasketcommon.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/basketthumbcreator.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/kcm_basket.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/libbasketpart.so]
W
menu-item-creates-new-section
The menu item has a line that specifies an unknown section or uses a
section that is intended only as a menu root, not as a section that
applications should use directly. Check the spelling of the section and
check the section against the list in the menu policy. (The menu sections
changed as of June of 2007.)
Please refer to The Debian Menu sub-policy section 2.1 for details.
Visibility: warning
Show-Always: no
Check: menu-format
Apps/Tools usr/share/menu/basket-trinity:2
W
menu-item-uses-apps-section
The menu item has a line that specifies a section under "Apps". This
section has been moved to "Applications".
Please refer to The Debian Menu sub-policy section 2.1 for details.
Visibility: warning
Show-Always: no
Check: menu-format
usr/share/menu/basket-trinity:2
W
national-encoding
A file is not valid UTF-8.
Debian has used UTF-8 for many years. Support for national encodings is
being phased out. This file probably appears to users in mangled
characters (also called mojibake).
Packaging control files must be encoded in valid UTF-8.
Please convert the file to UTF-8 using iconv or a similar tool.
Visibility: warning
Show-Always: no
Check: files/encoding
Renamed from: national-encoding-in-text-file
debian-changelog-file-uses-obsolete-national-encoding
debian-control-file-uses-obsolete-national-encoding
debian-copyright-file-uses-obsolete-national-encoding
debian-news-file-uses-obsolete-national-encoding
debian-tests-control-uses-national-encoding
doc-base-file-uses-obsolete-national-encoding
national-encoding-in-debconf-template national-encoding-in-manpage
usr/share/doc/basket-trinity/AUTHORS
usr/share/doc/basket-trinity/copyright
W
package-has-unnecessary-activation-of-ldconfig-trigger
Lintian did not output a note for this tag
W
package-relation-with-self
Breaks: basket-trinity (<< 4:14.0.0~)
W
unknown-section
tde
I
hardening-no-bindnow
Lintian did not output a note for this tag[opt/trinity/lib/libbasketcommon.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/basketthumbcreator.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/kcm_basket.so]
Lintian did not output a note for this tag[opt/trinity/lib/trinity/libbasketpart.so]
I
spelling-error-in-binary
opt/trinity/lib/libbasketcommon.so "allows to" "allows one to"
The listed shared library calls the C library exit() or _exit() functions.
In the case of an error, the library should instead return an appropriate
error code to the calling program which can then determine how to handle
the error, including performing any required clean-up.
In most cases, removing the call should be discussed with upstream,
particularly as it may produce an ABI change.
Visibility: info
Show-Always: no
Check: libraries/shared/exit
Renamed from: shlib-calls-exit
This tag is experimental.
opt/trinity/lib/libbasketcommon.so
C
control-tarball-compression-format
zst
C
ctrl-script
postinst
postrm
C
data-tarball-compression-format
zst
C
debhelper-autoscript-in-maintainer-scripts
The maintainer scripts of the package contain one or more auto-generated
shell snippets inserted by the listed debhelper tool.
Visibility: classification
Show-Always: no
Check: maintainer-scripts/generated
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
1.0.2-0ubuntu4 -> 4:14.1.6~pre12-0ubuntu22.04.0+1
E
rules-require-build-prerequisite
(does not satisfy cdbs)
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.)
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~pre12-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
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
1.0.2-0ubuntu4 -> 4:14.1.6~pre12-0ubuntu22.04.0+1
W
national-encoding
A file is not valid UTF-8.
Debian has used UTF-8 for many years. Support for national encodings is
being phased out. This file probably appears to users in mangled
characters (also called mojibake).
Packaging control files must be encoded in valid UTF-8.
Please convert the file to UTF-8 using iconv or a similar tool.
Visibility: warning
Show-Always: no
Check: files/encoding
Renamed from: national-encoding-in-text-file
debian-changelog-file-uses-obsolete-national-encoding
debian-control-file-uses-obsolete-national-encoding
debian-copyright-file-uses-obsolete-national-encoding
debian-news-file-uses-obsolete-national-encoding
debian-tests-control-uses-national-encoding
doc-base-file-uses-obsolete-national-encoding
national-encoding-in-debconf-template national-encoding-in-manpage
debian/copyright
I
adopted-extended-field
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
co-maintained-package-with-no-vcs-fields
Based on the content of the maintainer and uploader fields this package is
co-maintained but there are no Vcs-* fields.
It is recommended that shared maintenance of packages are co-ordinated via
a revision control system.
Visibility: pedantic
Show-Always: no
Check: fields/vcs
Renamed from: co-maintained-package-with-no-vcs-headers
Lintian did not output a note for this tag
P
no-homepage-field
This non-native package lacks a Homepage field. If the package has an
upstream home page that contains useful information or resources for the
end user, consider adding a Homepage control field to debian/control.
Please refer to Debian Policy Manual section 5.6.23 for details.
Visibility: pedantic
Show-Always: no
Check: fields/homepage
Lintian did not output a note for this tag
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 119)
debian/changelog (line 125)
debian/changelog (line 200)
debian/changelog (line 70)
debian/changelog (line 96)
debian/control (line 18)
debian/control (line 21)
P
very-long-line-length-in-source-file
src/kicondialogui.ui line 223 is 2298 characters long (>512)
src/notecontent.h line 121 is 554 characters long (>512)
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.
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-co-maintained
The package is co-maintained but not team-maintained 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.
(with 2 uploaders)
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.