Date: Wed, 24 Aug 2022 16:24:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 266023] net-p2p/go-ethereum upgrade to 1.10.23 Message-ID: <bug-266023-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266023 Bug ID: 266023 Summary: net-p2p/go-ethereum upgrade to 1.10.23 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: me@enriquefynn.com Attachment #236098 maintainer-approval+ Flags: Created attachment 236098 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D236098&action= =3Dedit go-ethereum-1.10.23.patch Geth v1.10.22 shipped with a serious bug that makes the database unusable. As stated in the release notes: To ensure that your node has all the data, please rewind your local chain t= o a block before you updated (if unsure, just pick a block before the release t= ime) with debug.setHead("0xblock-number-in-hex") via the Geth console (on IPC), = or debug_setHead via JSON RPC (you might need to temporarilly expose the debug namespace to do that). The brute force alternative of course is to resync a= fter an update, which you can do by deleting your chaindata folder (but please l= eave the ancient folder within to keep the blocks). Geth v1.10.23 is a hotfix release for a pruning regression that was introdu= ced in v1.10.22. For technical details on the bug. More information about the release at https://github.com/ethereum/go-ethereum/releases/tag/v1.10.23. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266023-7788>