Why would you have a leading / for some of the link targets and not others?
Probably the first line of this diff should be reverted. It does match what was in the .s390x file before which is probably where this came from. But since the leading / is optional in dh_link syntax, I think it's better to leave the line as it was and consistent with the rest of the file.
The upload in the queue for jammy has some surprising changes:
--- opencryptoki- 3.17.0+ dfsg+20220202. b40982e/ debian/ libopencryptoki 0.links 2022-02-15 08:02:48.000000000 +0000 3.17.0+ dfsg+20220202. b40982e/ debian/ libopencryptoki 0.links 2022-02-15 08:02:48.000000000 +0000 ${DEB_HOST_ MULTIARCH} /libpkcs11_ sw.so.0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ sw.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ sw.so.0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ sw.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ tpm.so. 0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ tpm.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ cca.so. 0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ cca.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ ep11.so. 0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ ep11.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ ica.so. 0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ ica.so ${DEB_HOST_ MULTIARCH} /libpkcs11_ icsf.so. 0 usr/lib/ ${DEB_HOST_ MULTIARCH} /libpkcs11_ icsf.so
+++ opencryptoki-
@@ -1,4 +1,7 @@
#! /usr/bin/dh-exec
-usr/lib/
+/usr/lib/
usr/lib/
usr/lib/
+usr/lib/
+usr/lib/
+usr/lib/
Why would you have a leading / for some of the link targets and not others?
Probably the first line of this diff should be reverted. It does match what was in the .s390x file before which is probably where this came from. But since the leading / is optional in dh_link syntax, I think it's better to leave the line as it was and consistent with the rest of the file.