The binary or shared library sets RPATH or RUNPATH. This overrides the normal library search path, possibly interfering with local policy and causing problems for multilib, among other issues. The only time a binary or shared library in a Debian package should set RPATH or RUNPATH is if it is linked to private shared libraries in the same package. In that case, place those private shared libraries in /usr/lib/*package*. Libraries used by binaries in other packages should be placed in /lib or /usr/lib as appropriate, with a proper SONAME, in which case RPATH/RUNPATH is unnecessary. To fix this problem, look for link lines like: gcc test.o -o test -Wl,--rpath,/usr/local/lib or gcc test.o -o test -R/usr/local/lib and remove the -Wl,--rpath or -R argument. You can also use the chrpath utility to remove the RPATH. Please refer to https://wiki.debian.org/RpathIssue for details. Visibility: error Show-Always: no Check: binaries/rpath Renamed from: binary-or-shlib-defines-rpath
[opt/trinity/lib/libpythonize.so.0.0.0]
[opt/trinity/]
[opt/trinity/lib/]
[opt/trinity/lib/libpythonize.so.0.0.0]
[opt/trinity/lib/libpythonize.so.0]
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
This package provides an ELF binary that lacks the "bindnow" linker flag. This is needed (together with "relro") to make the "Global Offset Table" (GOT) fully read-only. The bindnow feature trades startup time for improved security. Please consider enabling this feature or consider overriding the tag (possibly with a comment about why). If you use dpkg-buildflags, you may have to add hardening=+bindnow or hardening=+all to DEB_BUILD_MAINT_OPTIONS. The relevant compiler flags are set in LDFLAGS. Please refer to https://wiki.debian.org/Hardening for details. Visibility: info Show-Always: no Check: binaries/hardening
[opt/trinity/lib/libpythonize.so.0.0.0]
This package provides an ELF binary that lacks the use of fortified libc functions. Either there are no potentially unfortified functions called by any routines, all unfortified calls have already been fully validated at compile-time, or the package was not built with the default Debian compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags directly, be sure to import CPPFLAGS. NB: Due to false-positives, Lintian ignores some unprotected functions (e.g. memcpy). Please refer to https://wiki.debian.org/Hardening and Bug#673112 for details. Visibility: info Show-Always: no Check: binaries/hardening
[opt/trinity/lib/libpythonize.so.0.0.0]
The listed ELF binary appears to be (partially) built without "Large File Support" (LFS). If so, it may not be able to handle large files or files with large metadata values, such as inode numbers, correctly. To support large files, code review might be needed to make sure that those files are not slurped into memory or mmap(2)ed, and that correct 64-bit data types are used (ex: off_t instead of ssize_t), etc. Once that has been done ensure _FILE_OFFSET_BITS is defined and set to 64 before any system headers are included (note that on systems were the ABI has LFS enabled by default, setting _FILE_OFFSET_BITS to 64 will be a no-op, and as such optional). This can be done by using the AC_SYS_LARGEFILE macro with autoconf which will set any macro required to enable LFS when necessary, or by enabling the lfs feature from the future dpkg-buildflags feature area which sets the CPPFLAGS variable (since dpkg-dev 1.19.0). Note though, that getconf LFS_CFLAGS must not be used, as it does not support cross-building. Using _FILE_OFFSET_BITS should require no system function renames (eg. from open(2) to open64(2)), and if this tag is still emitted, the most probable cause is because the macro is not seen by the system code being compiled. Take into account that even if this tag is not emitted, that does not mean the binary is LFS-safe (ie. no OOM conditions, file truncation or overwrite will happen). Also note that enabling LFS on a shared library is not always safe as it might break ABI in case some of the exported types change size, in those cases a SOVERSION bump might be required. Or alternatively, on systems with an ABI without LFS, defining _LARGEFILE64_SOURCE and exporting both 32 and 64-bit variants of the interfaces can avoid the SOVERSION bump, at the cost of more complex maintenance. Please refer to http://www.unix.org/version2/whatsnew/lfs20mar.html and https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html for details. Visibility: info Show-Always: no Check: binaries/large-file-support This tag is experimental.
[opt/trinity/lib/libpythonize.so.0.0.0]
[Trinity]
[opt/trinity/]
[opt/trinity/include/]
[opt/trinity/include/pythonize.h]
[opt/trinity/lib/]
[opt/trinity/lib/libpythonize.a]
[opt/trinity/lib/libpythonize.la]
[opt/trinity/lib/libpythonize.so]
The dependency_libs field in the .la file has not been cleared. It has long been a release goal to get rid of unneeded .la files and clearing the dependency_libs field from the rest of them. A non-empty dependency_libs field will also stall the Multi-Arch conversion. The .la file in itself may be useful if the library is loaded dynamically via libltdl. Please refer to https://wiki.debian.org/ReleaseGoals/LAFileRemoval, https://lists.debian.org/debian-devel/2011/05/msg01003.html, and https://lists.debian.org/debian-devel/2011/05/msg01146.html for details. Visibility: error Show-Always: no Check: build-systems/libtool/la-file
[opt/trinity/lib/libpythonize.la:20]
[Trinity]
Lintian run for pytdeextensions-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 |
|
| System tar | system.tar.xz |
|
| Package upload | pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 |
|
| Package upload | pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: libpythonize0-trinity, libpythonize0-trinity-dbgsym, libpythonize0-trinity-dev | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 164371 | 2 weeks, 2 days | Worker | sbuild: pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 (armhf) | Completed | Success |
| 164368 | 2 weeks, 2 days | Worker | sbuild: pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 (all) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-164347
backend: unshare build_architecture: armhf environment: debian/match:codename=raspbian-bookworm exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-armhf source_artifact: 586465@artifacts output: binary_all_analysis: false source_analysis: false target_distribution: debian:raspbian-bookworm
backend: unshare build_architecture: armhf environment: debian/match:codename=raspbian-bookworm exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-armhf source_artifact: 586465@artifacts output: binary_all_analysis: false source_analysis: false target_distribution: debian:raspbian-bookworm task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:pytdeextensions-trinity - task:workspace:debusine:trinity-sb required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: bookworm environment_id: 27494 input_binary_artifacts_ids: - 593599 - 593862 input_source_artifact_id: 586465 parameter_summary: pytdeextensions-trinity_4:14.1.6~pre5-0raspbian12.0.0+2 runtime_context: binary-any:bookworm subject: pytdeextensions-trinity
{ "step": "lintian-armhf", "display_name": "Lintian for armhf" }
{ "on_success": [ { "action": "update-collection-with-artifacts", "variables": null, "collection": "internal@collections", "name_template": "lintian-armhf", "artifact_filters": { "category": "debian:lintian" } } ] }
{ "runtime_statistics": { "memory": 331615232, "cpu_time": 811, "duration": 210, "cpu_count": 24, "disk_space": 1325961216, "available_memory": 67425996800, "available_disk_space": 33713000448 } }