A short-term fix to resolve the RC bug may be to simply add a
'Conflicts: golang-step-crypto-dev' to
golang-github-smallstep-crypto-dev? Or is there a need to be able to
co-install these two packages?
Meanwhile I looked into updating golang-github-smallstep-certificates to
latest version and ran into what I think is a build dependency issue
with golang-step-linkedca which would needs a package rename/reupload to
get the latest version. The name name ought to be
golang-github-smallstep-linkedca instead which is the new namespace. It
seems most if not all of go.step.sm moved to github.com/smallstep
namespace. I doubt we can finish that transition before trixie though.
I had a look at another approach, just upgrading the dependency to golang-github-smallstep-crypto-dev
for these two packages:
- golang-step-cli-utils: all fine, level1
- golang-github-smallstep-certificates: level 2, needs the previous one rebuilt first, and the attached patch.
There are probably mistakes in that patch.