Repository navigation
A fix release for upgrades. If you are on 1.0.0 already, sudo apt update && sudo apt full-upgrade (or sudo dnf upgrade on EL9) is all you need.
Fixes
- Armbian and DietPi installs now move to the new repository. 1.0.0 only recommended the
alejandro-md-keyringpackage, and Armbian and DietPi turn recommended packages off system-wide. Those machines upgraded to 1.0.0 but kept pointing at the oldamd989.github.io/marinerrepository, which gets no further updates. mariner3d now depends on the keyring (and onalejandro-md-releasefor the rpm), so every install moves over. 1.0.1 is published to the old repository too, so machines stuck there pick it up on their next upgrade. - Upgrades no longer disconnect the printer's USB drive. Since 0.5.2, every deb upgrade stopped
mariner-usb-gadgetand never started it again, so the printer lost its files until the Pi rebooted, and an upgrade during a print would end the print. The rpm restarted it, which dropped the drive briefly. Upgrades now leave the gadget running. - A config file in your home directory is read again.
~/.mariner/config.tomlwas ignored because the~was never expanded (#532).
Also in this release
- The license file once again carries Luiz Ribeiro's original MIT notice, and it now ships with the deb, rpm and Docker image.
- The Docker docs point at
ghcr.io/mariner3d/mariner.
Installing a downloaded package by hand
Packages now depend on the repository package, so apt install ./mariner3d_*.deb on a machine without the repository configured needs the keyring too. The simplest path is the setup script:
curl -fsSL https://packages.alejandro.md/setup.sh | sudo sh
sudo apt install mariner3dFull changelog: v1.0.0...v1.0.1