Details about package ipp-crypto
Name: | ipp-crypto |
---|---|
Uploader: | ColinKing <colin.i.king@gmail.com> (Debian QA page) |
Description: | libippcp11 - Intel® Integrated Performance Primitives Cryptography libippcp-dev - Intel® Integrated Performance Primitives Cryptography development files libcrypto-mb11 - Intel® Integrated Performance Primitives Cryptography Multi-buffer libcrypto-mb-dev - Intel® IPP Cryptography Multi-buffer development files |
Package uploads
Upload #2
Information
Version: | 2021.10.0-3 |
---|---|
Uploaded: | 2024-07-15 15:39 |
Source package: | ipp-crypto_2021.10.0-3.dsc |
Distribution: | unstable |
Section: | utils |
Priority: | optional |
Homepage: | https://github.com/intel/ipp-crypto |
Changelog
ipp-crypto (2021.10.0-3) unstable; urgency=medium . * Add debian/libcrypto-mb11.symbols and debian/libippcp11.symbols
QA information
-
–
Package uses debhelper-compatDebhelper compatibility level 13
-
–
Newer upstream version available
Local: 2021.10.0 Upstream: 2021.12.1 Url: https://github.com/intel/ipp-crypto/archive/refs/tags/ippcp_2021.12.1.tar.gz -
–
Package is not native
Format: 3.0 (quilt) -
–
"Maintainer" email is the same as the uploader
-
–
Package has lintian experimental tagsipp-crypto source
-
X
debian-watch-does-not-check-openpgp-signature
- [debian/watch]
-
X
prefer-uscan-symlink
- filenamemangle s%(?:.*?)ippcp_(\d[\d.][\d.]*)\.tar\.gz%@PACKAGE@-$1.tar.gz% [debian/watch:4]
-
X
upstream-metadata-file-is-missing
-
X
very-long-line-length-in-source-file
- 580 > 512 [OVERVIEW.md:96]
- 582 > 512 [DEPRECATION_NOTES.md:65]
-
X
debian-watch-does-not-check-openpgp-signature
-
–
No VCS field present
-
–
Package is not in Debian
-
–
d/copyright is in DEP5 format
Upstream Contact: Andrey Matyukov <andrey.matyukov@intel.com> Licenses: Apache-2.0, MIT
Comments
-
Colin, Preamble... Thank you for taking the time to create this package and your contribution to the Debian project. The review below is for assistance. This review is offered to help package submitters to Debian mentors inorder to improve their packages prior to possible sponsorship into Debian. There is no obligation on behalf of the submitter to make any alterations based upon information provided in the review. Review... 1. Build[1]: Good 2. Lintian[2]: Issue W: libcrypto-mb11-dbgsym: debug-file-with-no-debug-symbols [usr/lib/debug/.build-id/c1/b30ef3d86f970356babdad3f0631a5b684986f.debug] N: N: The binary is installed as a detached "debug symbols" ELF file, but it N: does not appear to have debug information associated with it. N: N: A common cause is not passing -g to GCC when compiling. N: N: Implementation detail: Lintian checks for the ".debug_line" and the N: ".debug_str" sections. If either of these are present, the binary is N: assumed to contain debug information. N: N: Please refer to Bug#668437 for details. N: N: Visibility: warning N: Show-Always: no N: Check: binaries/debug-symbols/detached N: N: W: libcrypto-mb11: symbols-declares-dependency-on-other-package libcrypto11 (libcrypto_mb.so.11) [symbols] N: N: This package declares in its symbols control file a dependency on some N: other package (and not one listed in the Provides of this package). N: N: Packages should normally only list in their symbols control file the N: shared libraries included in that package, and therefore the dependencies N: listed there should normally be satisfied by either the package itself or N: one of its Provides. N: N: In unusual circumstances where it's necessary to declare more complex N: dependencies in the symbols control file, please add a Lintian override N: for this warning. N: N: Please refer to Dependencies between the library and other packages N: (Section 8.6) in the Debian Policy Manual for details. N: N: Visibility: warning N: Show-Always: no N: Check: debian/shlibs N: N: I: libippcp11-dbgsym: file-references-package-build-path [usr/lib/debug/.build-id/34/9146b7195a6578e514a72921b4a19663c85bc1.debug] N: N: The listed file or maintainer script appears to reference the build path N: used to build the package as specified in the Build-Path field of the N: .buildinfo file. N: N: This is likely to cause the package to be unreproducible, but it may also N: indicate that the package will not work correctly outside of the N: maintainer's own system. N: N: Please note that this tag will not appear unless the .buildinfo file N: contains a Build-Path field. That field is optional. You may have to set N: DEB_BUILD_OPTIONS=buildinfo=+path or use N: --buildinfo-option=--always-include-path with dpkg-buildpackage when N: building. N: N: Please refer to https://reproducible-builds.org/, N: https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, and the N: dpkg-genbuildinfo(1) manual page for details. N: N: Visibility: info N: Show-Always: no N: Check: files/contents 3. Licenses (lrc[3]: Good 4. Watch file (uscan --force-download): Gppd 5. Build Twice (sudo pbuilder build --twice <package>.dsc): Good 6. Reproducible builds (reporotest)[3]: Good 7. Install (No previous installs): Good 8. Upgrade (Over previous installs if any): N/A Additional... A. Update 'Standards-Version' in 'debian/control' to 4.7.0 as per Debian policy[5]. B. New packages to Debian need only one changelog entry. You can update the version on your first one and remove the rest. Regards Phil [1] Using: * pbuilder - https://wiki.ubuntu.com/PbuilderHowto. * https://wiki.debian.org/PbuilderTricks and * sbuild - https://wiki.debian.org/sbuild. [2] Command: lintian -v -i -I -E --pedantic --profile debian (*.dsc, *.changes, *.buildinfo). Each can throw up different, so be thorough. [3] 'lrc' from 'licenserecon' is located in Debian testing and newer. [4] https://wiki.debian.org/ReproducibleBuilds/Howto#Newer_method [5] https://www.debian.org/doc/debian-policy/
Needs work Phil Wyett at July 17, 2024, 1:36 a.m. -
Hi, You have not indicated that you wish a review and sponsorship by toggling "Needs a sponsor" on this page and creating and RFS bug[1]. If you have your own sponsor, you need do nothing. If not please do the above and your package will be looked at in a more timely manner. [1] https://mentors.debian.net/sponsors/rfs-howto/ Regards Phil
Phil Wyett at July 31, 2024, 5:53 p.m.
Upload #1
Information
Version: | 2021.10.0-2 |
---|---|
Uploaded: | 2024-07-09 08:24 |
Source package: | ipp-crypto_2021.10.0-2.dsc |
Distribution: | unstable |
Section: | utils |
Priority: | optional |
Homepage: | https://github.com/intel/ipp-crypto |
Changelog
ipp-crypto (2021.10.0-2) unstable; urgency=medium . * debian/rules: Use DEB_BUILD_MAINT_OPTIONS instead of DEB_BUILD_OPTIONS * debian/changelog: Use unstable * debian/copyright: Use expat for MIT licences * debian/control: Expand description for libcrypto-mb-dev
QA information
-
–
Package uses debhelper-compatDebhelper compatibility level 13
-
–
Newer upstream version available
Local: 2021.10.0 Upstream: 2021.12.1 Url: https://github.com/intel/ipp-crypto/archive/refs/tags/ippcp_2021.12.1.tar.gz -
–
Package is not native
Format: 3.0 (quilt) -
–
"Maintainer" email is the same as the uploader
-
–
Package has lintian experimental tagsipp-crypto source
-
X
debian-watch-does-not-check-openpgp-signature
- [debian/watch]
-
X
prefer-uscan-symlink
- filenamemangle s%(?:.*?)ippcp_(\d[\d.][\d.]*)\.tar\.gz%@PACKAGE@-$1.tar.gz% [debian/watch:4]
-
X
upstream-metadata-file-is-missing
-
X
very-long-line-length-in-source-file
- 580 > 512 [OVERVIEW.md:96]
- 582 > 512 [DEPRECATION_NOTES.md:62]
-
X
debian-watch-does-not-check-openpgp-signature
-
–
No VCS field present
-
–
Package is not in Debian
-
–
d/copyright is in DEP5 format
Upstream Contact: Andrey Matyukov <andrey.matyukov@intel.com> Licenses: Apache-2.0, MIT
Comments
No comments