Octez version 23.2 has just been released!
Octez v23.2 fixes an issue affecting systemd services of Debian and Ubuntu packages that could lead to having two baking binaries running at the same time.
In some cases, this issue could cause bakers to lose consensus rewards or, in certain conditions, could result in double-signing. Consequently, v23.0 and v23.1 Ubuntu and Debian packages were made unavailable via apt and dnf. The release of v23.2 restores the availability of these distribution packages.
For all other distributions, this version is the same as Octez v23.1
Octez v23.1 addressed an issue with Ubuntu and Debian packages distribution, where an expired PGP key prevented users from updating to v23.0 using apt.
v23.1 also fixed a potential resource leak, preventing the creation of zombie processes.
A full changelog and update instructions are available in the version 23 release page.
The Git tag is octez-v23.2 and the corresponding commit hash is 13afca5d.
Updating Debian and Ubuntu packages using apt
As the PGP keys have been rotated, users updating a pre-existing Debian or Ubuntu packages Octez deployment need to overwrite the previously installed octez.gpg key.
For example, in order to update to v23.2 from a pre-existing Ubuntu Noble deployment, a user should first update the keys with:
curl -s "https://packages.nomadic-labs.com/ubuntu/octez.asc" |
sudo gpg --yes --dearmor -o /etc/apt/keyrings/octez.gpg
Then, Octez packages users are advised to stop systemd services before updating to v23.2:
sudo apt-get update
sudo apt-get upgrade octez-baker
Please see the dedicated entry on the Octez docs for complete install instructions for Ubuntu and Debian packages.
Migrating deployments to octez-baker and octez-accuser
Octez v23 introduces unified, protocol-independent baker and accuser binaries: octez-baker and octez-accuser. These new binaries are intended to allow for simplified deployments across protocol upgrades, eliminating the need to deploy protocol-specific baking and accuser clients.
Note that v23 octez-baker and octez-accuser binaries provide support for both the current protocol on mainnet (Rio) and its elected successor (Seoul).
Bakers adopting the new binaries should make sure that the protocol-dependent binaries like octez-baker-PsRiotum and octez-baker-PtSeouLo are never deployed alongside octez-baker, as this could potentially lead to double signing scenarios.
