Open Beta v7.5 | Please help testing and hardening the upcoming release

[MichaIng]

RC version	v7.5.2
v7.5.0 PR	#4640
v7.5.1 PR	#4662
v7.5.2 PR	#4667
Raw changelog	https://github.com/MichaIng/DietPi/blob/beta/CHANGELOG.txt
Code changes	https://github.com/MichaIng/DietPi/compare/master...beta
Release date	2021-08-21

How to apply: https://github.com/MichaIng/DietPi/blob/master/BRANCH_SYSTEM.md

Related/solved issues: https://github.com/MichaIng/DietPi/issues?q=is%3Aissue+milestone%3Av7.5

---

Beta v7.5.2

(2021-08-21)

Changes

• DietPi-Globals | A new global function G_GET_WAN_IP has been added to print the public IP and location info. This function is now used by DietPi-Banner and DietPi-VPN to show the public IP. It makes use of the public API at freegeoip.app, which may also be used by malware, like all public APIs, and may hence be present in public blocklists. The function checks, whether this is the case, via curl's exit code, and in case prints a meaningful error message. Many thanks to @cocoflan for reporting the a related case: https://github.com/MichaIng/DietPi/issues/4445
• DietPi-FirstBoot | On our x86_64 BIOS images, the GRUB bootloader is configured to install itself on upgrade to the "/dev/sda" drive, which is the most commonly used system drive path and there is no way to configure a unique identifier that is assured to match the later actual system drive. When GRUB is upgraded, and the configured drive path does not exist, or GRUB has doubts that it is the correct system drive, the upgrade will fail. If GRUB installs itself to the wrong drive, the actually booted GRUB version won't match the GRUB files on the root filesystem, which can make the system unbootable. To enhance the situation, on first boot, DietPi detects the apparent system drive and changes the GRUB configuration accordingly. This will work on all our images, but note that on custom images it might be wrong: Generally it is possible to have the bootloader installed on one drive, but the root filesystem stored on a different physical drive, and we have no possibility to reliable detect this case. Many thanks to @brianbloom for reporting the issue: https://github.com/MichaIng/DietPi/issues/4542
• DietPi-Software | Java: This install option has now been split into the JRE (Java Runtime Environment) and the JDK (Java Development Kit). As our Java-written software options require the JRE only, this saves over 200 MiB of additional JDK-related disk space. For developers, however, the JDK stays with the same software ID.
• DietPi-Software | Cuberite: Re-applied the official binary on ARMv6 systems (Raspberry Pi 1 and Zero). Since those did not support ARMv6 in the past, we installed an old self-hosted binary, but now the latest official one can be used. Many thanks to @tigerw for letting us know about the change: https://github.com/MichaIng/DietPi/issues/3664#issuecomment-901261614
• DietPi-Software | Lidarr: Where supported (on all platforms but Raspberry Pi 1/Zero), the .NET core build build is now installed, which makes the dedicated Mono runtime obsolete and should generally perform better. This migration is applied automatically during the DietPi update, your settings and data remain untouched. Many thanks for informing us about this possible enhancement: https://github.com/MichaIng/DietPi/issues/4607
• DietPi-Software | PaperMC: Since Minecraft 1.17 requires Java 16 or newer, it does not work anymore on Debian versions below Bullseye and not on ARMv6, with the Java builds we ship, and has hence been disabled for those systems. AdoptOpenJDK is currently in the process of becoming "Adoptium" and creating a new APT repository, after which we can migrate to re-enable support on older Debian versions. On ARMv6 however I most likely won't work and the newest found Java build above version 8, running on ARMv6, is a single Zulu Java 11 build.

New Software

• Java JRE | The OpenJDK Java Runtime Environment has been made available as dedicated software option with ID 196 (see changes above).

Fixes

• DietPi-Software | Blynk Server: Resolved an issue where the install failed as the previous official repository has been removed by Blynk Inc. We switched to a fork, created hours before the repository removal, to preserve the install option and save users from being forced to use the commercial cloud servers. But note that there is no guarantee that the official apps will keep supporting it for long. In case older versions of the apps might need to be used.
• DietPi-Software | Roon Extension Manager: Resolved an issue where the installer failed when dietpi-software was executed with sudo as unprivileged user. The installer internally uses the SUDO_USER variable to perform some tasks, which fails to download the container startup shell script, as only root can write to the download location. Many thanks to @Esad-np for reporting this issue: https://github.com/MichaIng/DietPi/issues/4462
• DietPi-Software | Java JRE: Resolved an issue where the install failed on ARMv6: https://github.com/MichaIng/DietPi/issues/4509#issuecomment-876413815
• DietPi-Software | VSCodium: Added the missing dependency on ALSA for cases where no desktop is installed and VSCodium is started as standalone X server session. Many thanks to @Gill-Bates for reporting this issue: https://github.com/MichaIng/DietPi/issues/4610
• DietPi-Software | Bazarr: Resolved an issue where the install failed, as assets have been moved into an own repository, bundled with now release downloads. Many thanks to @psi5asp for reporting this issue: https://github.com/MichaIng/DietPi/issues/4615
• DietPi-Software | phpSysInfo: Resolved an issue where the install failed because of a changed download URL. Many thanks to @robex for reporting this issue: https://dietpi.com/phpbb/viewtopic.php?t=9278
• DietPi-Software | LXDE: Resolved an issue on Raspberry Pi Bullseye systems, where the install failed. Many thanks to @ravenclaw900 for reporting this issue: https://github.com/MichaIng/DietPi/issues/4555#issuecomment-898780672
• DietPi-Software | PiJuice: Resolved an issue where the install failed on Bullseye systems. Many thanks for reporting this issue: https://github.com/MichaIng/DietPi/issues/4643
• DietPi-Software | LXQt: Resolved an issue where the install failed on Bullseye systems. Many thanks to @LieDanG for reporting this issue: https://github.com/MichaIng/DietPi/issues/4656
• DietPi-Software | PaperMC: Resolved an issue where the install failed due to missing build dependencies.
• DietPi-Software | Java JRE: Resolved an issue where the install failed on Raspbian Bullseye systems, since Raspbian has no compiled Java 17 packages yet.
• DietPi-Software | ProFTPD: Resolved an issue where the service start failed on Bullseye systems due to an invalid config entry. Many thanks to @twikedk for reporting this issue: https://github.com/MichaIng/DietPi/issues/4666
• DietPi-Software | Kodi: Resolved an issue where the install failed on ARMv6 Bullseye images, as neither Raspbian nor the Raspberry Pi repository contain a Kodi package yet. We ship now an own package. Many thanks to @sibofax for reporting this issue: https://github.com/MichaIng/DietPi/issues/4650

[MichaIng]

The release has just been done. Many thanks for all testers and bug reporters, you are legend! 🙂