Hi folks,
I would like to adopt p11-kit orphaned security package.
I built an NMU test upgrade to the latest release in playground and in GH
Scallywag CI, and it passes most tests.
An intermediate release changed the build system from autotools to
meson/ninja/cmake which made the upgrade interesting. ;^>
The meson build created interface .DLLs instead of .SOs, except for the library
.so, which was symlinked as ...bin/cygp11-kit-0.dll as before, although there is
now a $S/$NAME/meson_post_install.sh to do so in the DESTDIR $D.
That script takes a libdir arg, so is there any reason or some way to handle
that as a postinstall script for libp11-kit0
Another difference I noticed was that the build dir was
$S/_build.$ARCH-pc-cygwin
from which I did a lndirs into $B after meson-install, just in case it affected
cygport processing.
It would be good if we could persuade meson/ninja/cmake to use $B as usual.
Any advice or feedback from experience with meson builds would be useful.
The .cygport will need some cleanup before promotion from playground to main.
I have installed the test packages and checked some of the gnutls dependencies'
security operations and they appear to be working properly.
I do not really know how to do a smoke test of the PKCS #11 module certificate
operations to be sure, so will wait until I hear others' suggestions for smoke
tests, issues or not, trying the test package with their package builds and checks.
So I have uploaded and announced the upgraded test package.
On 2026-02-08 11:47, [email protected] wrote:
INFO: adding 7 package(s)
INFO: move from Brian Inglis's upload area to release area:
INFO: deploying x86_64/release/p11-kit/p11-kit-0.26.2-1-src.hint
INFO: deploying x86_64/release/p11-kit/p11-kit-0.26.2-1-src.tar.xz
INFO: deploying x86_64/release/p11-kit/p11-kit-0.26.2-1-x86_64.hint
INFO: deploying x86_64/release/p11-kit/p11-kit-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/libp11-kit-devel/libp11-kit-devel-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/libp11-kit-devel/libp11-kit-devel-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/libp11-kit-doc/libp11-kit-doc-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/libp11-kit-doc/libp11-kit-doc-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/libp11-kit0/libp11-kit0-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/libp11-kit0/libp11-kit0-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/p11-kit-debuginfo/p11-kit-debuginfo-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/p11-kit-debuginfo/p11-kit-debuginfo-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/p11-kit-server/p11-kit-server-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/p11-kit-server/p11-kit-server-0.26.2-1-x86_64.tar.xz
INFO: deploying
x86_64/release/p11-kit/p11-kit-trust/p11-kit-trust-0.26.2-1-x86_64.hint
INFO: deploying
x86_64/release/p11-kit/p11-kit-trust/p11-kit-trust-0.26.2-1-x86_64.tar.xz
SUMMARY: 18 INFO(s)
Updates:
https://cygwin.com/cgit/cygwin-packages/p11-kit/?h=playground
Cygport NMU:
https://cygwin.com/cgit/cygwin-packages/p11-kit/tree/p11-kit.cygport?h=playground
Scallywag:
https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=p11-kit
Log:
https://github.com/cygwin/scallywag/actions/runs/21803104546/job/62902066494
...
Summary of Failures:
3/67 test-compat FAIL 0.23s exit status 2
22/67 test-conf FAIL 0.34s exit status 1
59/67 test-enumerate FAIL 0.06s killed by signal 11
SIGSEGV
65/67 test-server FAIL 10.61s exit status 1
Ok: 63
Expected Fail: 0
Fail: 4
...
Note:
- test-enumerate passes locally, fails with SIGSEGV in CI: test bug?
- test-compat fails as no Linux getauxval(3) or secure_getenv(3)
- test-conf fails as setuid(3p) returns 18 not 33
- test-server fails as module from ".../p11-kit-client"->C_GetSlotList(...)
passes count 32, but rpc i/f changes to 0, passes and returns that not 1: test bug?
Dependencies:
$ cygcheck-dep -cqSn libp11-kit{0,-devel} p11-kit{-server,-trust,}
libp11-kit0: is needed for ( libgck1_0 libgcr-base3_1 libgnutls28 libgnutls30
libp11-kit-devel p11-kit p11-kit-server p11-kit-trust )
libp11-kit-devel: is needed for ( libgck1-devel libgcr-base3-devel
libgcr-ui3-devel libgnutls-devel )
p11-kit-server: is needed for ( )
p11-kit-trust: is needed for ( ca-certificates libnss3 )
p11-kit: is needed for ( ca-certificates )
$ cygcheck-dep -cqSN libp11-kit{0,-devel} p11-kit{-server,-trust,} | ...
libp11-kit0: is recursively needed for 5300 ( ... )
libp11-kit-devel: is recursively needed for 15 ( infinoted0.6-devel
infinoted0.7-devel libgadu-devel libgck1-devel libgcr-base3-devel
libgcr-ui3-devel libgdata-devel libgnutls-devel libinfgtk3_0.6-devel
libinfgtk3_0.7-devel libinfinity0.6-devel libinfinity0.7-devel libqpdf-devel
libvte2.91-devel libxmlsec1-gnutls-devel )
p11-kit-server: is recursively needed for 0 ( )
p11-kit-trust: is recursively needed for 5052 ( ... )
p11-kit: is recursively needed for 4660 ( ... )
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
