MichaIng/DietPi v9.19

on GitHub

New software

• BirdNET-Go | This continuous avian monitoring and identification system has been added to our software catalogue. Many thanks to @mtekman for implementing this software option: #7770

Enhancement

• DietPi-Banner | An option to wrap the banner output for smaller terminals/screens has been added. Run dietpi-banner from console to configure its output, and find the new option at the bottom of the list. Many thanks to @mtekman for implementing this feature: #7779
• DietPi-Software | UrBackup: Packages are now installed via official APT repository: https://download.opensuse.org/repositories/home:/uroni/. Aside of the benefit of updates via apt upgrade, this allowed us to unlock support for Debian Trixie and above. Also support for ARMv6 has been added, but only until Debian Bookworm for now. A Raspbian Trixie suite does not exist yet
• DietPi-Software | NAA Daemon: Support for Debian Trixie and above on ARMv6/7 systems has been unlocked.
• DietPi-Software | Moonlight (GUI): Support for Debian Trixie and above on ARMv7 systems has been unlocked.
• DietPi-Software | Medusa: Support for Debian Trixie has been unlocked thanks to Python 3.13 support with v1.0.25: https://github.com/pymedusa/Medusa/releases/tag/v1.0.25
• DietPi-Software | Mosquitto: The official https://repo.mosquitto.org/debian/ APT repository is now used as well on Debian Trixie.

Bug fixes

• Raspberry Pi | We updated our raspberrypi-sys-mods package to be compatible with the new kernel stack and Raspberry Pi 5. This solves several issues like missing serial console access on first boot, missing device nodes or permissions to access them with gpio/i2c/spi/video system groups.
• Allwinner H3/H5 SBCs | Resolved an issue where using an RTC with Allwinner H3 and H5 SoC SBCs was difficult, since the the SoC-embedded one was enabled and assigned /dev/rtc0 node. However, only the NanoPi R1 has an actual RTC battery socket, in all other cases that embedded RTC is unusable. An external RTC, e.g. attached via I2C, was assigned to /dev/rtc1. The kernel however reads and assigns to system clock only /dev/rtc0, and worse, that factory timestamp is synced back to /dev/rtc1 (if present) at a very early boot stage, making even manual hwclock --hctosys --rtc /dev/rtc1 calls from userland a race condition. The SoC-embedded RTC is now disabled for all Allwinner H3/H5 boards but the NanoPi R1. If you were fiddling with this, for I2C RTCs, the device usually still needs to be created manually, or via device tree overlay. We can add such our kernel builds, just let us know which I2C RTC you use. Many thanks to @kevinds for reporting this issue: https://dietpi.com/forum/t/5116/12
• DietPi-Update | Resolved an issue on Debian Trixie systems with ZeroTier installed, where the update from DietPi v9.17 to v9.18 updated the ZeroTier APT repo falsely, leading to an apt update error. Many thanks to @randell1993 for reporting this issue: https://dietpi.com/forum/t/24580
• DietPi-Software | Jellyfin: Resolved an issue where the service start failed due to new strict space requirements for logging (512 MiB) and temporary directories (2 GiB). To support low RAM devices, we use /mnt/dietpi_userdata/jellyfin/log for log files, and a subdirectory in /mnt/dietpi_userdata/jellyfin/cache for temporary files, restoring behaviour from Jellyfin before v10.10. This can be adjusted in /etc/default/jellyfin.
• DietPi-Software | Node.js: Resolved an issue where usage could have failed, including Node-RED, Blynk Server, and MineOS installation, since it requires libatomic now for all architectures. Many thanks to @devifast for reporting this issue: https://dietpi.com/forum/t/24574
• DietPi-Software | Lidarr/Prowlarr: Resolved an issue on Bullseye systems where the service fails due to an incompatible embedded SQLite library: https://wiki.servarr.com/lidarr/faq#lidarr-wont-start-on-debian-11-or-older-systems-due-to-sqlite-version, https://wiki.servarr.com/prowlarr/faq#prowlarr-wont-start-on-debian-11-or-older-systems-due-to-sqlite-version
• DietPi-Software | SABnzbd: Resolved an issue where the installation could have finished with an incomplete config file. Many thanks to @DealsBeam for resolving this issue: #7797
• DietPi-Software | Bazarr: Resolved an issue where configuring Sonarr and Radarr usage automatically if installed did not work, because Bazarr switched from bazarr.ini to bazarr.yaml as its config file. Many thanks to @Joulinar for reporting this issue: #7185
• DietPi-Software | Medusa: Resolved an issue where the service failed to start because it tries to lift sandboxing for a directory that does not exist. We create our own systemd service from now on, instead of using and altering the template, which implies tailored sandboxing, better startup ordering, and a meaningful system log identifier.