As an update on this, I've gotten acmetool 0.2 to build on buster. The following packages need backporting:
- golang-github-gofrs-uuid - golang-golang-x-xerrors - golang-github-google-go-cmp - golang-gopkg-square-go-jose.v2 - golang-gopkg-hlandau-acmeapi.v2 - acmetool The 5 golang-* packages are source-only libraries, which shouldn't affect users of buster. They're just necessary to build the newer version entirely from packaged software. Of these packages, two require minor changes: - acmetool packaging fails because dwz can't find any debug tables to remove in the binary built by buster's golang 1.11. I suggest just skipping this step. - golang-gopkg-square-go-jose.v2 depends on dephelper-compat 13, but buster has 12. Downgrading the requirement seems to work fine. On IRC I got push-back from the go-team about reviewing changes, so I'm unsure how to proceed. Can someone from the letsencrypt team please comment on the proposed changes, either here, or on the salsa repositories? I've been recording the current state of my backport effort, including patches, at https://gitlab.xiph.org/rillian/acmetool-backport if anyone wants to reproduce. Thanks, Ralph
signature.asc
Description: This is a digitally signed message part
