Bitcoin Core/Knots 0.21.1 includes changes to Bitcoin's consensus protocol that should only be deployed with *active* opt-in consent from the user, never automatically. The solution to prevent this agreed on when it was added to the tree, was to package.mask them until some undefined future time. At this time, it remains inappropriate for any automatic upgrade to occur. Yet candrews secretly unmasked it back in October (ae7251a476e1ea18a429bf012dcdf45ec59662a6) with no discussion, triggering an unethical upgrade for users who had not opted in. This should be reverted immediately, or replaced with a comparable safeguard against automatic upgrades.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=deab2f8501132b2c6c6af1ab3dacf9abda75febf commit deab2f8501132b2c6c6af1ab3dacf9abda75febf Author: Luke Dashjr <luke-jr+git@utopios.org> AuthorDate: 2021-11-04 20:10:27 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2021-11-05 00:14:41 +0000 package.mask: re-mask bitcoin >=0.21.1 Without a mask, automatic upgrades would trigger, which is unethical (at least at this time). This reverts commit ae7251a476e1ea18a429bf012dcdf45ec59662a6. Closes: https://bugs.gentoo.org/821709 Signed-off-by: Luke Dashjr <luke-jr+git@utopios.org> Closes: https://github.com/gentoo/gentoo/pull/22818 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> profiles/package.mask | 12 ++++++++++++ 1 file changed, 12 insertions(+)
