Upgrade and uninstall
Upgrade
Download the newer package and install it with the same command used for the first install:
sudo apt install "./recond_${VERSION}_${ARCH}.deb"sudo dnf install "./recond-${VERSION}-1.${ARCH}.rpm"sudo zypper install --allow-unsigned-rpm "./recond-${VERSION}-1.${ARCH}.rpm"If the service is running, the package restarts it on the new binary. If it is stopped, it stays stopped, and whether it starts on boot does not change. Your config and state are left untouched.
recond -version
sudo systemctl status recondIf the restart after an upgrade fails, check journalctl -u recond, fix the cause, and run sudo systemctl restart recond.
Read the changelog before upgrading across a release with breaking changes. v0.5.0, for example, moved the default config and state paths.
Downgrade
Download the older package and install it as a downgrade. The service is restarted the same way as on an upgrade:
sudo apt install --allow-downgrades "./recond_${VERSION}_${ARCH}.deb"sudo dnf downgrade "./recond-${VERSION}-1.${ARCH}.rpm"sudo zypper install --oldpackage --allow-unsigned-rpm "./recond-${VERSION}-1.${ARCH}.rpm"Uninstall
sudo apt remove recond # keeps your config and deployment state
sudo apt purge recond # removes everything, including /etc/recond and /var/lib/recondsudo dnf remove recondsudo zypper remove recondUninstalling stops and disables the service.
apt purge deletes your config and state
On Debian and Ubuntu, apt purge also deletes /etc/recond (including your config.yaml) and /var/lib/recond (including deployment state). Back them up first if you may reinstall later. apt remove, dnf remove, and zypper remove keep them.
RPM has no purge, so remove the config and state yourself if you no longer need them:
sudo rm -rf /etc/recond /var/lib/recondReinstall after uninstall
Reinstalling reuses the kept config and state, but the service stays disabled and stopped, because uninstalling disabled it. Start it again with:
sudo systemctl enable --now recond