[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtcanvas.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtnetwork.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtsql.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqttable.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtui.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtxml.cpython-313-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqt:2]
[postinst]
[prerm]
[postinst]
[prerm]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtcanvas.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtnetwork.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtsql.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqttable.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtui.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtxml.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313d-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqt-dbg:5]
[usr/share/lintian/overrides/python3-pytqt-dbg:1]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqt.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtcanvas.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqtsql.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/python3/dist-packages/PyTQt/tqttable.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/debug/.build-id/00/576a0aeebe9c55e7ed8ffe863dec11b1d0ec5d.debug]
[usr/lib/debug/.build-id/05/c5aea32d98abd58afee8a202265249ac809d28.debug]
The package is for the debug variant of the python interpreter, not like dbgsym.
[usr/lib/debug/.build-id/79/9a6d4295b728dfbc72415f0c9c993f91845e80.debug]
[usr/lib/debug/.build-id/7e/e68251f94e8f54b6dd066bf924255c7292c9df.debug]
[usr/lib/debug/.build-id/b6/991dcef35f42d3266ad680c8e282cfc93e5925.debug]
[usr/lib/debug/.build-id/de/3d0417a21b361a12aa6178a8962d8786a44ac5.debug]
[usr/lib/debug/.build-id/f6/3ad8401dc469d405b826df2029c80a9e8f63ab.debug]
[usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-313-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqt-gl:2]
[usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-313d-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqt-gl-dbg:5]
[usr/share/lintian/overrides/python3-pytqt-gl-dbg:1]
[usr/lib/python3/dist-packages/PyTQt/tqtgl.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/debug/.build-id/e9/972b70fc051e5786221aa0858e1ffb1fa3c106.debug]
[usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-313-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqtext:2]
[usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-313d-x86_64-linux-gnu.so]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/python3-pytqtext-dbg:5]
[usr/share/lintian/overrides/python3-pytqtext-dbg:1]
[usr/lib/python3/dist-packages/PyTQt/tqtext.cpython-313d-x86_64-linux-gnu.so]
[usr/lib/debug/.build-id/22/e938a27e0823a56b833b739750e12b72cdb77d.debug]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/pytqt-tools:2]
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.
[usr/bin/pytquic]
[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]
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/pytqt-dev:2]
[usr/share/lintian/overrides/pytqt-dev:5]
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
[usr/share/sip-tqt/tqt/tqt/]
[postinst]
[prerm]
[postinst]
[prerm]
The package ships a .html or .pdf file under /usr/share/doc/. Those files are usually documentation, but no files are registered in doc-base. Files in folders named examples are exempt from this tag. Please refer to Registering Documents using doc-base (Section 9.10) in the Debian Policy Manual for details. Visibility: info Show-Always: no Check: menus
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[usr/share/lintian/overrides/pytqt-doc:2]
[usr/share/doc/pytqt-doc/examples/SQL/dbconnect.py]
[usr/share/doc/pytqt-doc/examples/SQL/runform1.py]
[usr/share/doc/pytqt-doc/examples/SQL/runform2.py]
[usr/share/doc/pytqt-doc/examples/SQL/runsqlex.py]
[usr/share/doc/pytqt-doc/examples/SQL/sqlcustom1.py]
[usr/share/doc/pytqt-doc/examples/SQL/sqlsubclass5.py]
[usr/share/doc/pytqt-doc/examples/SQL/sqltable4.py]
[usr/share/doc/pytqt-doc/examples/aclock.py]
[usr/share/doc/pytqt-doc/examples/addressbook.py]
[usr/share/doc/pytqt-doc/examples/application.py]
[usr/share/doc/pytqt-doc/examples/biff.py]
[usr/share/doc/pytqt-doc/examples/bigtable.py]
[usr/share/doc/pytqt-doc/examples/buttongroups.py]
[usr/share/doc/pytqt-doc/examples/canvas/canvas.py]
[usr/share/doc/pytqt-doc/examples/checklists.py]
[usr/share/doc/pytqt-doc/examples/cursor.py]
[usr/share/doc/pytqt-doc/examples/dclock.py]
[usr/share/doc/pytqt-doc/examples/desktop.py]
[usr/share/doc/pytqt-doc/examples/dirview.py]
[usr/share/doc/pytqt-doc/examples/dragdrop.py]
[usr/share/doc/pytqt-doc/examples/drawlines.py]
[usr/share/doc/pytqt-doc/examples/fontdisplayer.py]
[usr/share/doc/pytqt-doc/examples/fonts.py]
[usr/share/doc/pytqt-doc/examples/gears.py]
[usr/share/doc/pytqt-doc/examples/i18n/i18n.py]
[usr/share/doc/pytqt-doc/examples/lineedits.py]
[usr/share/doc/pytqt-doc/examples/listbox.py]
[usr/share/doc/pytqt-doc/examples/listboxcombo.py]
[usr/share/doc/pytqt-doc/examples/mdi.py]
[usr/share/doc/pytqt-doc/examples/menu.py]
[usr/share/doc/pytqt-doc/examples/progress.py]
[usr/share/doc/pytqt-doc/examples/progressbar.py]
[usr/share/doc/pytqt-doc/examples/rangecontrols.py]
[usr/share/doc/pytqt-doc/examples/richtext.py]
[usr/share/doc/pytqt-doc/examples/semaphore.py]
[usr/share/doc/pytqt-doc/examples/smalltable.py]
[usr/share/doc/pytqt-doc/examples/splitter.py]
[usr/share/doc/pytqt-doc/examples/tabdialog.py]
[usr/share/doc/pytqt-doc/examples/tablestatistics.py]
[usr/share/doc/pytqt-doc/examples/tooltip.py]
[usr/share/doc/pytqt-doc/examples/tqdir.py]
[usr/share/doc/pytqt-doc/examples/tqmag.py]
[usr/share/doc/pytqt-doc/examples/tut1.py]
[usr/share/doc/pytqt-doc/examples/tut10.py]
[usr/share/doc/pytqt-doc/examples/tut11.py]
[usr/share/doc/pytqt-doc/examples/tut12.py]
[usr/share/doc/pytqt-doc/examples/tut13.py]
[usr/share/doc/pytqt-doc/examples/tut14.py]
[usr/share/doc/pytqt-doc/examples/tut2.py]
[usr/share/doc/pytqt-doc/examples/tut3.py]
[usr/share/doc/pytqt-doc/examples/tut4.py]
[usr/share/doc/pytqt-doc/examples/tut5.py]
[usr/share/doc/pytqt-doc/examples/tut6.py]
[usr/share/doc/pytqt-doc/examples/tut7.py]
[usr/share/doc/pytqt-doc/examples/tut8.py]
[usr/share/doc/pytqt-doc/examples/tut9.py]
[usr/share/doc/pytqt-doc/examples/widgets.py]
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
[debian/control:5]
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
[debian/control:29]
[debian/control:55]
[debian/control:82]
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
[debian/rules]
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
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 Architecture specific overrides (Section 2.4.3) in the Lintian User's Manual for details. Visibility: info Show-Always: yes Check: lintian
[debian/source/lintian-overrides:12]
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
[debian/manpages/pytqlupdate.1]
[debian/manpages/pytquic.1]
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
[debian/copyright]
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
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
[debian/changelog:21]
[debian/rules:146]
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.
[examples/webbrowser/mainwindow.ui:272]
[examples/i18n/mywidget_el.qm:3]
[examples/i18n/mywidget_it.qm:4]
[examples/i18n/mywidget_ru.qm:2]
[examples/i18n/mywidget_ko.qm:1]
[examples/i18n/mywidget_eo.qm:1]
[examples/i18n/mywidget_fr.qm:1]
[examples/i18n/mywidget_de.qm:1]
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
The package is for the debug variant of the python interpreter, not like dbgsym.
[debian/source/options:2]
We want XZ regardless of the default compression.
[debian/source/options:3]
We want XZ regardless of the default compression.
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.
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.
[debian/rules]
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.
[debian/patches/series]
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.
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.
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.
[debian/control]
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.
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:7]
[debian/control:4]
[debian/control:3]
[debian/control:2]
[debian/control:1]
[debian/control:8]
[debian/control:6]
[debian/control:5]
[debian/control:117]
[debian/control:119]
[debian/control:118]
[debian/control:122]
[debian/control:115]
[debian/control:120]
[debian/control:116]
[debian/control:121]
[debian/control:11]
[debian/control:13]
[debian/control:12]
[debian/control:17]
[debian/control:10]
[debian/control:14]
[debian/control:15]
[debian/control:16]
[debian/control:28]
[debian/control:32]
[debian/control:31]
[debian/control:34]
[debian/control:27]
[debian/control:29]
[debian/control:33]
[debian/control:30]
[debian/control:42]
[debian/control:44]
[debian/control:43]
[debian/control:48]
[debian/control:41]
[debian/control:45]
[debian/control:46]
[debian/control:47]
[debian/control:57]
[debian/control:60]
[debian/control:58]
[debian/control:61]
[debian/control:54]
[debian/control:55]
[debian/control:59]
[debian/control:56]
[debian/control:70]
[debian/control:72]
[debian/control:71]
[debian/control:75]
[debian/control:69]
[debian/control:73]
[debian/control:74]
[debian/control:84]
[debian/control:86]
[debian/control:85]
[debian/control:88]
[debian/control:81]
[debian/control:82]
[debian/control:87]
[debian/control:83]
[debian/control:95]
[debian/control:96]
[debian/control:97]
[debian/control:94]
[debian/control:105]
[debian/control:107]
[debian/control:106]
[debian/control:110]
[debian/control:104]
[debian/control:108]
[debian/control:109]
Lintian run for pytqt package.
|
Name
|
|
|
|---|---|---|
| Source package | pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 |
|
| System tar | system.tar.xz |
|
| Package upload | pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 |
|
| Package upload | pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: python3-pytqt, python3-pytqt-dbg, python3-pytqt-gl, python3-pytqt-gl-dbg, python3-pytqtext, python3-pytqtext-dbg, pytqt-tools | |
| Lintian report | lintian: pytqt-dev, pytqt-doc | |
| Lintian report | lintian: pytqt | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 152929 | 3 weeks | Worker | sbuild: pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 (amd64) | Completed | Success |
| 152924 | 3 weeks | Worker | sbuild: pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 (all) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-152889
backend: unshare build_architecture: amd64 environment: debian/match:codename=questing exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-amd64 source_artifact: 531144@artifacts output: {} target_distribution: debian:questing
backend: unshare build_architecture: amd64 environment: debian/match:codename=questing exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-amd64 source_artifact: 531144@artifacts output: {} target_distribution: debian:questing task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:pytqt - task:workspace:debusine:trinity-sb required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: questing environment_id: 27702 input_binary_artifacts_ids: - 532307 - 532412 input_source_artifact_id: 531144 parameter_summary: pytqt_4:14.1.6~pre2-0ubuntu25.10.0+3 runtime_context: binary-all+binary-any+source:questing subject: pytqt
{ "step": "lintian-amd64", "display_name": "Lintian for amd64+all+source" }
{ "on_success": [ { "action": "update-collection-with-artifacts", "variables": null, "collection": "internal@collections", "name_template": "lintian-amd64", "artifact_filters": { "category": "debian:lintian" } } ] }
{ "runtime_statistics": { "memory": 5169963008, "cpu_time": 143, "duration": 48, "cpu_count": 24, "disk_space": 1040654336, "available_memory": 67425996800, "available_disk_space": 33713000448 } }