Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtcanvas.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtnetwork.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtsql.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqttable.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtui.cpython-310-x86_64-linux-gnu.so]
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtxml.cpython-310-x86_64-linux-gnu.so]
I
hardening-no-fortify-functions
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-310-x86_64-linux-gnu.so]
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Description TQt bindings for Python 3 Python binding module that allows use of TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . At this moment PyTQt offers a vast subset of TQt API. There are some minor issues related to the differences between C++ and Python (types, etc), but usually you'll be able to write code pretty much the same way in both languages (with syntax differences, of course)
Installed-Size 12451
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Description TQt bindings for Python 3 (debug extension) Python binding module that allows use of TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . This package contains the extension built for the Python debug interpreter.
Installed-Size 38313
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-310-x86_64-linux-gnu.so]
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Description TQt OpenGL bindings for Python 3 Python binding module that allows use of the OpenGL facilities offered by the TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X).
Installed-Size 246
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-310d-x86_64-linux-gnu.so]
I
spelling-error-in-binary
usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-310d-x86_64-linux-gnu.so autor author
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Description TQt OpenGL bindings for Python 3 (debug extension) Python binding module that allows use of the OpenGL facilities offered by the TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . This package contains the extension built for the Python debug interpreter.
Installed-Size 1007
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-310-x86_64-linux-gnu.so]
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Lintian did not output a note for this tag[usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-310d-x86_64-linux-gnu.so]
I
spelling-error-in-binary
usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-310d-x86_64-linux-gnu.so autor author
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
unknown-field Original-Maintainer
P
copyright-refers-to-symlink-license
usr/share/common-licenses/GPL
X
application-in-library-section
This package contains a binary in $PATH but is in a section just thought
for libraries. It likely should be in another section like e.g. utils,
text, devel, misc, etc., but not in e.g. perl, ruby or python.
People tend to skip these package sections when looking for applications
in the package list and hence wouldn't notice this package.
In case the program in $PATH is only a helper tool and the package is
primarily a library, please add a Lintian override for this tag.
Visibility: info
Show-Always: no
Check: application-not-library
This tag is experimental.
Description pyuic and pylupdate for TQt pyuic is the PyTQt counterpart for TQt's uic. It takes an XML user interface file and generates Python code. . pylupdate is the counterpart for TQt's lupdate. It updates TQt Linguist translation files from Python code.
Installed-Size 481
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Package pytqt-tools
Priority optional
Section python
Source pytqt
Version 4:14.1.6~pre2-0ubuntu22.04.0+3
pytqt-dev_14.1.6~pre2-0ubuntu22.04.0+3_all.deb
I
extra-license-file
usr/share/sip-tqt/tqt/tqt/copying.sip
usr/share/sip-tqt/tqt/tqtaxcontainer/copying.sip
usr/share/sip-tqt/tqt/tqtcanvas/copying.sip
usr/share/sip-tqt/tqt/tqtext/copying.sip
usr/share/sip-tqt/tqt/tqtgl/copying.sip
usr/share/sip-tqt/tqt/tqtnetwork/copying.sip
usr/share/sip-tqt/tqt/tqtpe/copying.sip
usr/share/sip-tqt/tqt/tqtsql/copying.sip
usr/share/sip-tqt/tqt/tqttable/copying.sip
usr/share/sip-tqt/tqt/tqtui/copying.sip
usr/share/sip-tqt/tqt/tqtxml/copying.sip
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
python-module-in-wrong-location
unknown-field Original-Maintainer
P
copyright-refers-to-symlink-license
usr/share/common-licenses/GPL
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
Description TQt bindings for Python - Development files Development .sip files with definitions of PyTQt classes. They are needed to build PyTQt, but also as building blocks of other packages based on them, like PyTDE.
Installed-Size 1218
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Package pytqt-dev
Priority optional
Replaces python-tqt-dev
Section python
Source pytqt
Suggests python3-sip-tqt-dev, sip-tqt-dev
Version 4:14.1.6~pre2-0ubuntu22.04.0+3
pytqt-doc_14.1.6~pre2-0ubuntu22.04.0+3_all.deb
I
possible-documentation-but-no-doc-base-registration
The package ships a .html or .pdf file under /usr/share/doc/, which are
usually documentation, but it does not register anything in doc-base.
(Files under an examples directory are excluded.)
Please refer to Debian Policy Manual section 9.10 for details.
Visibility: info
Show-Always: no
Check: menus
Lintian did not output a note for this tag
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
Description TQt bindings for Python - Documentation and examples Documentation and examples for the PyTQt (bindings that allow the use of TQt library from within a Python script).
Installed-Size 919
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Package pytqt-doc
Priority optional
Replaces python-tqt-doc
Section doc
Source pytqt
Suggests python3-pytqt
Version 4:14.1.6~pre2-0ubuntu22.04.0+3
pytqt_14.1.6~pre2-0ubuntu22.04.0+3.dsc
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
installable-field-mirrors-source
(in section for python3-pytqt-dbg) Priority
[debian/control:29]
(in section for python3-pytqt-gl-dbg) Priority
[debian/control:55]
(in section for python3-pytqtext-dbg) Priority
[debian/control:82]
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)
I
unused-override
Your package specifies the named override but there were no tags that
could have been silenced by it.
Maybe you fixed an underlying condition but forgot to remove the override.
It is also possible that the Lintian maintainers fixed a false positive.
If the override is now unused, please remove it.
This tag is similar to mismatched-override except there a tag could have
been silenced if the context had matched.
Sometimes, overrides end up not being used because a tag appears only on
some architectures. In that case, overrides can be equipped with an
architecture qualifier.
Please refer to Lintian User's Manual section 2.4.3 for details.
Visibility: info
Show-Always: yes
Check: lintian
unknown-field Original-Maintainer
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
maintainer-manual-page
debian/manpages/pytqlupdate.1
debian/manpages/pytquic.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
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 21)
debian/rules (line 146)
P
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: cruft
Renamed from: insane-line-length-in-source-file
examples/webbrowser/mainwindow.ui line 272 is 3565 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
overridden
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
The package is for the debug variant of the python interpreter, not like dbgsym.
compression = "xz" (line 2)
Comment:
We want XZ regardless of the default compression.
compression-level = 9 (line 3)
Comment:
We want XZ regardless of the default compression.
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 3 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.
debian/control §1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
debian/control §1 Priority optional
debian/control §1 Section python
debian/control §1 Source pytqt
debian/control §1 Standards-Version 3.8.4
debian/control §1 Uploaders Torsten Marek <shlomme@debian.org>, Bernd Zeimetz <bzed@debian.org>, Michael Casadevall <mcasadevall@debian.org>
debian/control §1 XSBC-Original-Maintainer Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
debian/control §10 Architecture all
debian/control §10 Breaks python-tqt-doc
debian/control §10 Depends ${misc:Depends}
debian/control §10 Description TQt bindings for Python - Documentation and examples Documentation and examples for the PyTQt (bindings that allow the use of TQt library from within a Python script).
debian/control §2 Description TQt bindings for Python 3 Python binding module that allows use of TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . At this moment PyTQt offers a vast subset of TQt API. There are some minor issues related to the differences between C++ and Python (types, etc), but usually you'll be able to write code pretty much the same way in both languages (with syntax differences, of course)
debian/control §3 Description TQt bindings for Python 3 (debug extension) Python binding module that allows use of TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . This package contains the extension built for the Python debug interpreter.
debian/control §4 Description TQt OpenGL bindings for Python 3 Python binding module that allows use of the OpenGL facilities offered by the TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X).
debian/control §5 Description TQt OpenGL bindings for Python 3 (debug extension) Python binding module that allows use of the OpenGL facilities offered by the TQt X Window toolkit v3. You can use it to create portable graphics-capable scripts (there are PyTQt versions for Linux, Windows and MacOS X). . This package contains the extension built for the Python debug interpreter.
debian/control §8 Description pyuic and pylupdate for TQt pyuic is the PyTQt counterpart for TQt's uic. It takes an XML user interface file and generates Python code. . pylupdate is the counterpart for TQt's lupdate. It updates TQt Linguist translation files from Python code.
debian/control §9 Description TQt bindings for Python - Development files Development .sip files with definitions of PyTQt classes. They are needed to build PyTQt, but also as building blocks of other packages based on them, like PyTDE.