[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1100967: golang-step-crypto-dev and golang-github-smallstep-crypto-dev have undeclared file conflicts





Le lun. 7 avr. 2025 à 02:00, Jérémy Lal <kapouer@melix.org> a écrit :


Le mer. 2 avr. 2025 à 10:39, Simon Josefsson <simon@josefsson.org> a écrit :
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.

Now that that patch passes the test suite by borrowing from upstream fixes,
and that "caddy" also builds fine with them, I'm going to do as advertised.

Reply to: