Comment 17 for bug 2022088

@vorlon, a new upload should have been there and the one that you had a look at should be in 'reject' (I asked for that in IRC).
So the libopencryptoki0.links modification is mentioned in this upload (still in unapproved):
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=opencryptoki
since I was not happy with the changelog myself and updated it quite a bit to:
"
   * Add d/p/lp-2022088-fix-p11sak-failure-to-find-libopencryptoki.so.patch
     to fix the failure that p11sak is not able to find libopencryptoki as
     plugin, by adjusting 'default_pkcs11lib'. (LP: #2022088)
   * d/opencryptoki.install: install full set of etc/opencryptoki build
     folder to esp. catch all generated conf files and on top make the arch-
     specific file 'opencryptoki.install.s390x' obsolete. (LP: #2018911)
   * d/libopencryptoki0.links{.s390x} Merge files, since the content of the
     s390x version of this file applies in all cases.
   * Assign pkcs11 group to p11sak_defined_attrs.conf and strength.conf
     in debian/opencryptoki.postinst rather than in Makefile.am and add
     d/p/lp-1982842-move-pkcs11-group-assigment-from-makefile-to-postinst.patch
     to solve "invalid group ‘pkcs11’" issues during build.
   * d/opencryptoki.postinst: change strength.conf file permissions to 640
     which is checked/forced by the opencryptoki code. (LP: #2018908)
"

And yes I've noticed that one of the lines in the links file starts with an obsolete slash,
but it was already in (in the s390x version - I haven't checked when it came in though, guess it was a typo or c&p issue).
I indeed copied the universally valid libopencryptoki0.links.s390x over to libopencryptoki0.links, hence it stayed.
(Having it all consistent and w/o slashes would be indeed nicer.)

If we want it consistent, please reject an I will re-upload with this little change ...