On Wed, Jun 08, 2022 at 09:33:58AM +0800, Paul Wise wrote:
On Tue, 2022-06-07 at 15:16 +0000, Ileana Dumitrescu wrote:golang-github-boltdb-bolt is incompatible with riscvI suggest an approach that will help resolve this in a more gradual manner that will mean this issue becomes less annoying: Add a Debian patch to golang-github-boltdb-bolt fixing the RISC-V incompatibility, probably you can figure out how the forks of the boltdb-bolt project did it and then backport that to boltdb-bolt. Then file Debian bugs and upstream issues for every package in Debian that uses boltdb-bolt asking them to switch to one of the forks. Then file a removal request for golang-github-boltdb-bolt but mark it as blocked by the Debian bug reports about switching away from it. Then start working through all these projects making patches to do the switch. Try to get the patches upstream, but when they don't accept them immediately, then try to get them included in Debian. Once the removal request has no blocking bugs, then the Debian archive admins will see that and remove the package.
I think this is acceptable solution. We have some go-* packages's upstream that has switched to bbolt but we do not upgrade go-* package in Debian currently, see here[0]. I am stuck here also, e,g, to try upgrade consul[1]. Now it is 1.8.7+dfsg1-5in sid, if I want to upgrade to the newest upstream 1.22. It will depend on other go package that was not introduced to Debian. It becomes
complicated. In fact, I found the consul(1.8.7) has both bolt and bbolt in go.sum. I am not sure why because I have poor knowledge about go lanuage until now. PS: consul is key go-package that many go-packages was blocked by it on riscv64 arch. Bo [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010686 [1]: https://buildd.debian.org/status/package.php?p=consul&suite=sid
-- bye, pabs https://wiki.debian.org/PaulWise
-- Best Regards,
Attachment:
signature.asc
Description: PGP signature