#257689: lintian: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7

Result: Failure

Fail on: error

Lintian output

Summary of tags

error: 102
warning: 19
info: 6
pedantic: 8
experimental: 5
overridden: 0
classification: 76

Tags

kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7_amd64.deb

E dir-or-file-in-opt

Lintian did not output a note for this tag [opt/trinity/]
Lintian did not output a note for this tag [opt/trinity/bin/]
Lintian did not output a note for this tag [opt/trinity/bin/kbarcode]
Lintian did not output a note for this tag [opt/trinity/lib/]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/tdefile_kbarcode.la]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/tdefile_kbarcode.so]
Lintian did not output a note for this tag [opt/trinity/share/]
Lintian did not output a note for this tag [opt/trinity/share/applications/]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/kbarcode-batch.desktop]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/kbarcode-editor.desktop]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/kbarcode-single.desktop]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/kbarcode.desktop]
Lintian did not output a note for this tag [opt/trinity/share/apps/]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/barcode.ps]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/barcodes.html]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/exampledata.sql]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/labeldefinitions.sql]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/logo.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/rules.xml]
Lintian did not output a note for this tag [opt/trinity/share/doc/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kbarcode/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kbarcode/common]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kbarcode/index.cache.bz2]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kbarcode/index.docbook]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/]
Lintian did not output a note for this tag [opt/trinity/share/icons/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/actions/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/actions/barcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/actions/kbarcodeellipse.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/actions/kbarcodegrid.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/actions/kbarcodelinetool.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/apps/kbarcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/22x22/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/22x22/actions/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/22x22/actions/barcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/actions/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/actions/barcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/actions/kbarcoderect.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/apps/kbarcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/64x64/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/64x64/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/64x64/apps/kbarcode.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/]
Lintian did not output a note for this tag [opt/trinity/share/locale/]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/]
Lintian did not output a note for this tag [opt/trinity/share/locale/el/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/el/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/el/]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fi/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fi/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/fi/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/]
Lintian did not output a note for this tag [opt/trinity/share/locale/hu/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/hu/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/hu/]
Lintian did not output a note for this tag [opt/trinity/share/locale/it/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/it/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/it/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pt/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pt/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/pt/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/]
Lintian did not output a note for this tag [opt/trinity/share/locale/tr/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/tr/LC_MESSAGES/kbarcode.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/tr/]
Lintian did not output a note for this tag [opt/trinity/share/man/]
Lintian did not output a note for this tag [opt/trinity/share/man/man1/]
Lintian did not output a note for this tag [opt/trinity/share/man/man1/kbarcode.1]
Lintian did not output a note for this tag [opt/trinity/share/mimelnk/]
Lintian did not output a note for this tag [opt/trinity/share/mimelnk/application/]
Lintian did not output a note for this tag [opt/trinity/share/mimelnk/application/kbarcode-label.desktop]
Lintian did not output a note for this tag [opt/trinity/share/services/]
Lintian did not output a note for this tag [opt/trinity/share/services/tdefile_kbarcode.desktop]

W copyright-refers-to-deprecated-bsd-license-file

The copyright file refers to /usr/share/common-licenses/BSD. Due to the
brevity of this license, the specificity of this copy to code whose
copyright is held by the Regents of the University of California, and the
frequency of minor wording changes in the license, its text should be
included in the copyright file directly rather than referencing this file.

This file may be removed from a future version of base-files if references
to it drop sufficiently.

Please refer to Copyright information (Section 12.5) in the Debian Policy
Manual for details.

Visibility: warning
Show-Always: no
Check: debian/copyright

Lintian did not output a note for this tag

W description-contains-homepage

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 19

W extended-description-line-too-long

One or more lines in the extended part of the "Description:" field have
been found to contain more than 80 characters. For the benefit of users of
80x25 terminals, it is recommended that the lines do not exceed 80
characters.

Please refer to The single line synopsis (Section 3.4.1) in the Debian
Policy Manual for details.

Visibility: warning
Show-Always: no
Check: fields/description

line 1

W hardening-no-relro

Lintian did not output a note for this tag [opt/trinity/bin/kbarcode]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/tdefile_kbarcode.so]

W icon-size-and-directory-name-mismatch

22x22 [opt/trinity/share/icons/hicolor/16x16/actions/kbarcodelinetool.png]
30x30 [opt/trinity/share/icons/hicolor/16x16/actions/kbarcodeellipse.png]

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

Lintian did not output a note for this tag [usr/share/doc/kbarcode-trinity/README.Debian]

W old-fsf-address-in-copyright-file

The /usr/share/doc/*pkg*/copyright file refers to the old postal address
of the Free Software Foundation (FSF). You should refer to
https://www.gnu.org/licenses/ instead of a physical address, for example:

You should have received a copy of the GNU General Public License
along with this program.  If not, see https://www.gnu.org/licenses/.

Visibility: warning
Show-Always: no
Check: debian/copyright

Lintian did not output a note for this tag

W package-has-unnecessary-activation-of-ldconfig-trigger

The package activates the ldconfig trigger even though no shared libraries
are installed in a directory controlled by the dynamic library loader.

Note this may be triggered by a bug in debhelper, that causes it to
auto-generate an ldconfig trigger for packages that do not need it.

Please refer to ldconfig (Section 8.1.1) in the Debian Policy Manual and
Bug#204975 for details.

Visibility: warning
Show-Always: no
Check: libraries/shared/trigger/ldconfig

Lintian did not output a note for this tag

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.

Visibility: warning
Show-Always: no
Check: fields/package-relations

Breaks: kbarcode-trinity (<< 4:14.0.0~)

W unknown-section

The "Section:" field in this package's control file is not one of the
sections in use on the ftp archive. Valid sections are currently admin,
comm, cli-mono, database, debug, devel, doc, editors, electronics,
embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio,
haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, lisp,
localization, kernel, mail, math, misc, net, news, ocaml, oldlibs,
otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex,
text, utils, vcs, video, web, x11, xfce, zope.

The section name should be preceded by either "contrib/", "non-free/" or
"non-free-firmware/" if the package is in the according archive area.

Please refer to Sections (Section 2.4) in the Debian Policy Manual for
details.

Visibility: warning
Show-Always: no
Check: fields/section

I hardening-no-bindnow

Lintian did not output a note for this tag [opt/trinity/bin/kbarcode]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/tdefile_kbarcode.so]

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

Screen: python/egg/metadata
Advocates: "Scott Kitterman" <debian@kitterman.com>
Reason: The folders XXX.dist-info/ and XXX.egg-info/ hold metadata for
Python modules. Those files are not documentation even though
some of their names carry the .txt file extension.

Python modules can be both public and private.

Read more in
https://www.python.org/dev/peps/pep-0427/#the-dist-info-directory,
https://www.python.org/dev/peps/pep-0376/#id16,
https://www.python.org/dev/peps/pep-0610/,
https://www.python.org/dev/peps/pep-0639/,
https://setuptools.pypa.io/en/latest/deprecated/python_eggs.html,
and Bug#1003913.

Lintian did not output a note for this tag [opt/trinity/share/apps/kbarcode/barcodes.html]

P copyright-with-old-dh-make-debian-copyright

The copyright file contains the incomplete Debian packaging copyright
boilerplate from older versions of dh_make. (C) alone is not considered a
valid copyright notice in some countries. The word Copyright or the ©
symbol should be used instead or in addition to (C).

Copyright notices like this are, in any country that's a signatory to the
Berne Convention, not required to claim copyright on a work, but their
presence may allow claiming additional damages should a copyright case go
to court. If you provide a notice, you may as well provide one that's
legally recognized in a broader range of countries.

Visibility: pedantic
Show-Always: no
Check: debian/copyright

Lintian did not output a note for this tag

P repeated-path-segment

The file is installed into a location that repeats the given path segment.
An example would be /usr/lib/lib or /usr/share/myprogram/share.

More often than not this is unintended.

Please refer to Bug#950052 and Bug#950027 for details.

Visibility: pedantic
Show-Always: no
Check: files/hierarchy/path-segments

trinity [opt/trinity/lib/trinity/]

X spelling-error-in-binary

Normaly Normally [opt/trinity/bin/kbarcode]
avaible available [opt/trinity/bin/kbarcode]
formated formatted [opt/trinity/bin/kbarcode]

C control-tarball-compression-format

C ctrl-script

Lintian did not output a note for this tag [postinst]
Lintian did not output a note for this tag [postrm]

C data-tarball-compression-format

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.

dh_installmenu/13.24.2

C mail-contact

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>

C maintainer-script-interpreter

/bin/sh [postinst]
/bin/sh [postrm]

C package-is-maintained-by-individual

Lintian did not output a note for this tag

C trimmed-field

Architecture amd64
Breaks kbarcode-trinity (<< 4:14.0.0~)
Depends libc6 (>= 2.38), libgcc-s1 (>= 3.0), libpcre2-8-0 (>= 10.22), libstdc++6 (>= 11), libtqt3-mt (>= 4:14.2.0~pre279), tdelibs14-trinity (>= 4:14.2.0~pre294), barcode, imagemagick
Description barcode and label printing application for Trinity
KBarcode is a barcode and label printing application for Trinity. It can be used
to print everything from simple business cards up to complex labels with
several barcodes (e.g. article descriptions).
.
KBarcode comes with an easy to use WYSIWYG label designer, a setup wizard,
batch import of data for batch printing labels (directly from the delivery
note), thousands of predefined labels, database management tools and
translations in many languages. Even printing more than 10.000 labels in one
go is no problem for KBarcode. Data for printing can be imported from several
different data sources, including SQL databases, CSV files and the TDE address
book.
.
Additionally it is a simple barcode generator (similar to the old xbarcode you
might know). All major types of barcodes like EAN, UPC, CODE39 and ISBN are
supported. Even complex 2D barcodes are supported using third party tools. The
generated barcodes can be directly printed or you can export them into images
to use them in another application.
.
Homepage: http://www.kbarcode.net
Installed-Size 2437
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package kbarcode-trinity
Priority optional
Recommends libtqt3-mt-mysql | libtqt3-mt-psql | libtqt3-mt-odbc | libtqt3-mt-sqlite | libtqt3-mt-ibase
Replaces kbarcode-trinity (<< 4:14.0.0~)
Section tde
Version 4:14.2.0~pre47-0raspbian13.0.0+7

kbarcode-trinity-dbgsym_14.2.0~pre47-0raspbian13.0.0+7_amd64.deb

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>

C no-ctrl-scripts

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.

Lintian did not output a note for this tag

C package-is-maintained-by-individual

Lintian did not output a note for this tag

C trimmed-field

Architecture amd64
Auto-Built-Package debug-symbols
Build-Ids 11e0b235568f512fdb7982c339c4c8dae7bbce91 2ce9d773d994c11cdad8512aeaa07a076047a1a3
Depends kbarcode-trinity (= 4:14.2.0~pre47-0raspbian13.0.0+7)
Description debug symbols for kbarcode-trinity
Installed-Size 4272
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package kbarcode-trinity-dbgsym
Priority optional
Section debug
Source kbarcode-trinity
Version 4:14.2.0~pre47-0raspbian13.0.0+7

kbarcode-trinity_14.2.0~pre47-0raspbian13.0.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.

Visibility: error
Show-Always: no
Check: debian/changelog

2.0.6-0ubuntu3 -> 4:14.2.0~pre47-0raspbian13.0.0+7 [debian/changelog:1]

E rules-require-build-prerequisite

(does not satisfy cdbs:any) [debian/rules]

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 Recompilation or binary-only NMU (Section 5.10.2.1) in the
Debian Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: fields/version

4:14.2.0~pre47-0raspbian13.0.0+7
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
qualifier, if you see one.

Please refer to Package relationships (Section 4.2) in the Debian Policy
Manual 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" [debian/source/options:2]
compression-level = 9 [debian/source/options: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

2.0.6-0ubuntu3 -> 4:14.2.0~pre47-0raspbian13.0.0+7 [debian/changelog: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

Lintian did not output a note for this tag [debian/README.Debian]

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.

Please refer to Using the DELAYED/ queue (Section 5.11.3) in the Debian
Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: nmu
Renamed from: changelog-should-mention-nmu

Lintian did not output a note for this tag [debian/changelog:1]

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.

Please refer to NMUs and debian/changelog (Section 5.11.2) in the Debian
Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: nmu

4:14.2.0~pre47-0raspbian13.0.0+7 [debian/changelog:1]

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 Upstream source location: debian/watch (Section 4.11) in
the Debian Policy Manual 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 [debian/rules]

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.7.2)

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-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 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 Homepage (Section 5.6.23) in the Debian Policy Manual 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

P trailing-whitespace

Lintian did not output a note for this tag [debian/changelog:148]
Lintian did not output a note for this tag [debian/changelog:170]

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

X very-long-line-length-in-source-file

The source file includes a line length that is well beyond the normally
human made code line length.

This very long line length does not allow Lintian to do correctly some
source file checks.

This line could also be the result of some text injected by a computer
program, and thus could lead to FTBFS bugs.

Last but not least, long line in source code could be used to obfuscate
the source code and to hide stuff like backdoors or security problems.

It could be due to jslint source comments or other build tool comments.

You may report this issue upstream.

Visibility: pedantic
Show-Always: no
Check: files/contents/line-length
Renamed from: insane-line-length-in-source-file
This tag is experimental.

Screen: autotools/long-lines
Advocates: "Russ Allbery" <rra@debian.org>
Reason:
Upstream sources using autoconf have traditionally been
distributed with generated ./configure scripts as well as
other third-party m4 macro files such as libtool.

When paired with automake, there may also be some intermediate
Makefile.in files.

A lot of sources potentially contain such files, but they are
not actionable by either the Debian distributor or by the
upstream maintainer.

As a side note, modern Debian build protocols will re-create
many of those files via dh_autoreconf. They are present merely
to aid in bootstrapping systems where the GNU suite may not yet
be available.

Read more in Bug#996740.

656 > 512 [kbarcode/tec.cpp:121]

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.

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 [debian/rules]

C mail-contact

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>
Uploaders "Fathi Boudra" <fboudra@free.fr>
Uploaders "Mark Purcell" <msp@debian.org>

C number-of-patches

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 [debian/patches/series]

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 silent-on-rules-requiring-root

The field Rules-Requires-Root is not declared in the file debian/control.

Please refer to usr/share/doc/dpkg/spec/rootless-builds.txt, debian/rules
and Rules-Requires-Root (Section 4.9.2) in the Debian Policy Manual, and
Rules-Requires-Root (Section 5.6.31) in the Debian Policy Manual for
details.

Visibility: classification
Show-Always: no
Check: debian/control/field/rules-requires-root
Renamed from: rules-requires-root-missing
This tag is a classification. There is no issue in your package.

Lintian did not output a note for this tag [debian/control]

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.

3.8.4

C trimmed-deb822-field

§1 Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs14-trinity-dev [debian/control:6]
§1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org> [debian/control:4]
§1 Priority optional [debian/control:3]
§1 Section tde [debian/control:2]
§1 Source kbarcode-trinity [debian/control:1]
§1 Standards-Version 3.8.4 [debian/control:7]
§1 Uploaders Fathi Boudra <fboudra@free.fr>, Mark Purcell <msp@debian.org> [debian/control:5]
§2 Architecture any [debian/control:10]
§2 Breaks kbarcode-trinity (<< 4:14.0.0~) [debian/control:13]
§2 Depends ${shlibs:Depends}, ${misc:Depends}, barcode, imagemagick [debian/control:11]
§2 Description barcode and label printing application for Trinity
KBarcode is a barcode and label printing application for Trinity. It can be used
to print everything from simple business cards up to complex labels with
several barcodes (e.g. article descriptions).
.
KBarcode comes with an easy to use WYSIWYG label designer, a setup wizard,
batch import of data for batch printing labels (directly from the delivery
note), thousands of predefined labels, database management tools and
translations in many languages. Even printing more than 10.000 labels in one
go is no problem for KBarcode. Data for printing can be imported from several
different data sources, including SQL databases, CSV files and the TDE address
book.
.
Additionally it is a simple barcode generator (similar to the old xbarcode you
might know). All major types of barcodes like EAN, UPC, CODE39 and ISBN are
supported. Even complex 2D barcodes are supported using third party tools. The
generated barcodes can be directly printed or you can export them into images
to use them in another application.
.
Homepage: http://www.kbarcode.net [debian/control:16]
§2 Package kbarcode-trinity [debian/control:9]
§2 Recommends libtqt3-mt-mysql | libtqt3-mt-psql | libtqt3-mt-odbc | libtqt3-mt-sqlite |
libtqt3-mt-ibase [debian/control:14]
§2 Replaces kbarcode-trinity (<< 4:14.0.0~) [debian/control:12]

C trimmed-field

Architecture any
Binary kbarcode-trinity
Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs14-trinity-dev
Checksums-Sha1 fdafcf8e6726da169fdd5c643817ae0b1184c556 283104 kbarcode-trinity_14.2.0~pre47.orig.tar.xz
d65de2f794808e0de42daeb8c1623d25ce9f1fa1 5868 kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7.debian.tar.xz
Checksums-Sha256 bbef6bbf05c8fec67f4666c360efc9cf40a74e25f786c1aecbcf5473bf8f6518 283104 kbarcode-trinity_14.2.0~pre47.orig.tar.xz
d825e51b58511d0fac45b1c27d4b08c26528b6b70df3699e1aad02783286dd60 5868 kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7.debian.tar.xz
Files 7a68880262936c7af07898c3bfd9c8ee 283104 kbarcode-trinity_14.2.0~pre47.orig.tar.xz
953a56ba458d681375b47c50ebcb6193 5868 kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7.debian.tar.xz
Format 3.0 (quilt)
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package-List kbarcode-trinity deb tde optional arch=any
Source kbarcode-trinity
Standards-Version 3.8.4
Uploaders Fathi Boudra <fboudra@free.fr>, Mark Purcell <msp@debian.org>
Version 4:14.2.0~pre47-0raspbian13.0.0+7

Description

Lintian run for kbarcode-trinity package.

Additional details:

Source packages: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7
Binary packages: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7
Executed in environment system.tar.xz
Fail on severity: error
Build architecture: amd64
Target distribution: debian:raspbian-trixie
Include tags: none
Exclude tags: none

Input artifacts

Type Alphabetical order Reverse alphabetical order	Name
Source package	kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7
System tar	system.tar.xz
Package upload	kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7

Workflow information

⬆️ debian_pipeline ( Aborted )
⬆️ QA ( Aborted )
⬆️ lintian ( Completed Failure )

Output artifacts

Type Alphabetical order Reverse alphabetical order	Name
Lintian report	lintian: kbarcode-trinity, kbarcode-trinity-dbgsym
Lintian report	lintian: kbarcode-trinity
Debug log	debusine:work-request-debug-logs

Output data

Runtime statistics:
- Duration: 00:00:45
- CPU time: 00:01:49
- Disk space: 1.2 GB
- Memory: 177.2 MB
- Available disk space: 31.4 GB
- Available memory: 62.8 GB
- CPU count: 12
Errors:

Dependencies

Work requests that must be completed before this one can run.

ID Lowest first Highest first	Created Oldest first Newest first	Task type Alphabetical order Reverse alphabetical order	Task Alphabetical order Reverse alphabetical order	Status Alphabetical order Reverse alphabetical order	Result Alphabetical order Reverse alphabetical order
257677	2 days, 8 hours	Worker	sbuild: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7 (amd64)	Completed	Success

Reverse dependencies

This work request is not required by any other one.

Internal collection: workflow-257598

Task data

backend: unshare
build_architecture: amd64
environment: debian/match:codename=raspbian-trixie
exclude_tags: []
fail_on_severity: error
include_tags: []
input:
  binary_artifacts:
  - internal@collections/name:build-amd64
  source_artifact: 818504@artifacts
output: {}
target_distribution: debian:raspbian-trixie

Task data after applying task configuration

backend: unshare
build_architecture: amd64
environment: debian/match:codename=raspbian-trixie
exclude_tags: []
fail_on_severity: error
include_tags: []
input:
  binary_artifacts:
  - internal@collections/name:build-amd64
  source_artifact: 818504@artifacts
output: {}
target_distribution: debian:raspbian-trixie
task_configuration: 1021

Scheduler tags

provided:
- task:group:debusine::Admins
- task:group:debusine::TDE-Owners
- task:scope:debusine
- task:source-package:kbarcode-trinity
- task:workspace:debusine:trinity-testing
required:
- worker:executor:unshare
- worker:task:worker:lintian:version:1
- worker:type:external

Dynamic data

configuration_context: trixie
environment_id: 27472
input_binary_artifacts_ids:
- 821206
input_source_artifact_id: 818504
parameter_summary: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7
runtime_context: binary-all+binary-any+source:trixie
subject: kbarcode-trinity

Workflow data

{
  "step": "lintian-amd64",
  "display_name": "Lintian for amd64+all+source"
}

Event reactions

{
  "on_success": [
    {
      "action": "update-collection-with-artifacts",
      "variables": null,
      "collection": "internal@collections",
      "name_template": "lintian-amd64",
      "artifact_filters": {
        "category": "debian:lintian"
      }
    }
  ]
}

Output data

{
  "runtime_statistics": {
    "memory": 185853952,
    "cpu_time": 109,
    "duration": 45,
    "cpu_count": 12,
    "disk_space": 1305837568,
    "available_memory": 67425996800,
    "available_disk_space": 33713000448
  }
}

lintian: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7… 257598… Completed Failure trinity-testing… SlavekB 2 days, 8 hours ago fenrir-01… 2 hours, 11 minutes 0 minutes 3 weeks, 6 days

#257689: lintian: kbarcode-trinity_4:14.2.0~pre47-0raspbian13.0.0+7

Summary of tags

Tags

kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7_amd64.deb

E dir-or-file-in-opt

W copyright-refers-to-deprecated-bsd-license-file

Explanation

W description-contains-homepage

Explanation

W extended-description-line-too-long

Explanation

W hardening-no-relro

W icon-size-and-directory-name-mismatch

W national-encoding

Explanation

W old-fsf-address-in-copyright-file

Explanation

W package-has-unnecessary-activation-of-ldconfig-trigger

Explanation

W package-relation-with-self

Explanation

W unknown-section

Explanation

I hardening-no-bindnow

I package-contains-documentation-outside-usr-share-doc

Explanation

P copyright-with-old-dh-make-debian-copyright

Explanation

P repeated-path-segment

Explanation

X spelling-error-in-binary

C control-tarball-compression-format

C ctrl-script

C data-tarball-compression-format

C debhelper-autoscript-in-maintainer-scripts

Explanation

C mail-contact

C maintainer-script-interpreter

C package-is-maintained-by-individual

C trimmed-field

kbarcode-trinity-dbgsym_14.2.0~pre47-0raspbian13.0.0+7_amd64.deb

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

C no-ctrl-scripts

Explanation

C package-is-maintained-by-individual

C trimmed-field

kbarcode-trinity_14.2.0~pre47-0raspbian13.0.0+7.dsc

E epoch-changed-but-upstream-version-did-not-go-backwards

Explanation

E rules-require-build-prerequisite

W binary-nmu-debian-revision-in-source

Explanation

W custom-compression-in-debian-source-options

W epoch-change-without-comment

Explanation

W national-encoding

Explanation

W no-nmu-in-changelog

Explanation

W source-nmu-has-incorrect-version-number

Explanation

I debian-watch-file-is-missing

Explanation

I no-dh-sequencer

Explanation

I out-of-date-standards-version

Explanation

P co-maintained-package-with-no-vcs-fields

Explanation

P no-dep5-copyright

Explanation

P no-homepage-field

Explanation

P package-uses-old-debhelper-compat-version

Explanation

P trailing-whitespace

X upstream-metadata-file-is-missing

Explanation