You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
If I am wrong please correct me.
Is there we have plan to switch github.com/etcd-io/bbolt? because the bolt repo is a public archive and the bblot is active.
Backgroup: I am fix Debian ftbfs issue on riscv64 arch, and there are many package build fails on riscv64 arch due to the dependence of
github.com/boltdb/bolt. I am going to fix the bolt build issue on riscv64 but Debian Go-Lang people tell me it would be better ask for help from upstream: https://lists.debian.org/debian-riscv/2022/05/msg00007.html
I am not familiar with go program but if that is true i can try to send PR.
Thank you.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up! Yeah! I'm open to looking at a PR to move to etcd-io/bbolt. However, ideally, I'd like it to happen in tandem for both the scep project and MicroMDM, if that's possible. :)
Hi,
If I am wrong please correct me.
Is there we have plan to switch github.com/etcd-io/bbolt? because the bolt repo is a public archive and the bblot is active.
Backgroup: I am fix Debian ftbfs issue on riscv64 arch, and there are many package build fails on riscv64 arch due to the dependence of
github.com/boltdb/bolt. I am going to fix the bolt build issue on riscv64 but Debian Go-Lang people tell me it would be better ask for help from upstream:
https://lists.debian.org/debian-riscv/2022/05/msg00007.html
I am not familiar with go program but if that is true i can try to send PR.
Thank you.
The text was updated successfully, but these errors were encountered: