Hi. I have uploaded 7ff5b54618a566b450d18023fce48cb649fb691b to NEW using the 'sbctl' and 'sbctl-bin' naming, to get the NEW processing started. I have not dared to test the postinst/prerm 'sbctl' scripts on my machine, but I also don't think that is critical: we can sort out bugs in those scripts later on. Having this in experimental will allow more people to test it.
https://salsa.debian.org/go-team/packages/sbctl/ https://salsa.debian.org/jas/sbctl/-/pipelines/961822 We can work out how to migrate golang-github-go-piv-piv-go (and then sbctl) to unstable eventually, the blocker for this is the 'yubikey-agent' package which is stuck on v1.x but sbctl requires v2.x. If the following upstream bug report doesn't see action, I suppose we could introduce a golang-github-go-piv-piv-go-v1-dev package to keep yubikey-agent happy, and let the golang-github-go-piv-piv-go package move forward and use v2 for upstream source. https://github.com/FiloSottile/yubikey-agent/issues/161 /Simon
signature.asc
Description: PGP signature
