-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v9.2 #6955
Merged
Release v9.2 #6955
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Init v9.2 - CHANGELOG | Fix v9.1 release date - DietPi-Software | PaperMC: Resolved an issue where installing the Geyser and Floodgate plugins failed due to changed download URLs, and a false syntax in the Geyser config file. Many thanks to @boterocamilo for reporting this issue: #6898
- DietPi-Installer | Since Bookworm, Dropbear ships with a systemd service and the NO_START env var is hence obsolete. The stop we do is a noop if the setting is not present, hence we do not need to patch anything, but this conditional serves as well as marker for removal, once we remove Bullseye support from DietPi-Installer.
- DietPi-Build | Raise rootfs size of Orange Pi Zero 3, required on Bookworm images, and merge all the Bookworm-only image size increments into base sizes. It doesn't really make a difference whether images for Bullseye are larger at first, as DietPi-Imager minimises their size afterwards anyway.
- DietPi-Software | Nextcloud: Resolved an issue with the updated Nginx config, where assets were served with the wrong MIME type. This fix was backported to v9.1 and a live patch offered. Many thanks to @howardroark for reporting this issue: https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372
- NanoPi R5C | Add wlan0 interface trigger for WLAN ("WL" labelled) LED. It has no onbaord WiFi, but an M.2 E key slot which supports WiFi modules. And the LED is obviously intended for this. - NanoPi R6C | Fix LED udev rules to prevent Ethernet LEDs from staying lit from boot on, if the interfaces are not configured afterwards. Also add a WiFi trigger for the "LED1" labelled LED. The R6C has an M.2 M key slot, intended for NVMe SSDs, but there are also adapters to attack M.2 WiFi modules, or a USB module can be used. Making use of this LED for WiFi, if any WiFi adapter is attached, seems a good default. With own udev rules or via dietpi-led_control, the trigger can be easily changed.
- DietPi-Software | LXQt: Add config archive for Trixie and remove the one for Buster. Remove all packages from being explicitly installed, which are dependencies of the "lxqt" package anyway. Keep only xarchiver, as we set it explicitly in our PCManFM config, and the default dependency on Trixie has changed to lxqt-archiver. Do not add SpeedCrunch on Trixie, as it does not exist there at time of writing. Remove nuoveXT2 icon theme, as we do not use it.
- DietPi-Installer | From Bookworm on, gcc-*-base packages are not "Priority: required" anymore, but "optional" instead, hence are autoremoved. So we we need to purge the obsolete ones on Bullseye only. - DietPi-Build | Leave obsolete gcc-*-base package removals to DietPi-Installer, which are only installed on Bullseye. - DietPi-Build | Remove --rpi-new flag. Instead use hardware models 1/2/4/5 as indicator that the new firmware is needed. Remove an obsolete Raspbian Trixie workaround and add new RPi firmware models to "all" workflow.
- DietPi-Software | Home Assistant: Resolved an issue on x86_64 and ARMv8 systems where some core integrations did not work if no C++ compiler was installed. If you are affected by this, "apt install g++ && systemctl restart home-assistant" will fix it. Many thanks to @pdsakurai for fixing this issue in our install code: #6931
- DietPi-Software | It is now possible to run "dietpi-software list" concurrent to other dietpi-software instances, and as non-root user. This avoids an issue in DietPi-Dashboard, where opening dietpi-software in the Terminal and switching to the Software page, caused an infinite hang. - DietPi-Globals | Resolved an issue where a concurrent DietPi script detection could have prevented the start of a script, if a previous instance was killed via SIGKILL. - DietPi-Config | Resolved an issue where a WiFi connection, configured for the first time via dietpi-config from a local terminal session, was automatically stopped when exiting or logging out from the terminal session.
- CI | Squeezelite: Temporarily allow lib*t64 packages, while the 64-bit time_t transition is ongoing on Sid: https://bugs.debian.org/1065394
- CI | Amiberry: Temporarily allow lib*t64 packages, while the 64-bit time_t transition is ongoing on Sid: https://bugs.debian.org/1065394
- CI | Squeezelite: Use again latest commit, with a fix for upstream libFLAC: ralph-irving/squeezelite@fd89d67 - Coding | Mute new shellcheck annotation SC2324
- CI | vaultwarden: Temporarily allow lib*t64 packages, while the 64-bit time_t transition is ongoing on Sid: https://bugs.debian.org/1065394
- DietPi-Config | Fix and simplify journalctl handling when restarting network connections: Job control messages are not printed within scripts, hence no need to wrap everything in command blocks and mute STDERR. SIGINT somehow does not work in this script to kill journalctl, while it does work from console. Hence use SIGTERM, which does work.
- DietPi-Patches | Bump Amiberry to v5.6.8 - DietPi-Software | Gogs/Gitea: Using repositories via SSH should now work OOTB with new installs and reinstalls. If pull or push operations via SSH fail in your case, try to give the respective user a default shell: "sudo usermod -s /bin/dash gogs" respectively "sudo usermod -s /bin/dash gitea". This is now included in our default setup. Many thanks to @din14970 for reporting this missing feature: #6964 (reply in thread) - DietPi-Config | Resolved an issue on RPi systems, where HDMI audio did not work if full KMS was enabled. The firmware/bcm2835 HDMI audio driver conflicts with the full KMS display driver, hence the VC4 HDMI driver needs to be used instead. That one however only supports the IEC958 audio format, which requires a complex ALSA config. This config is shipped with the "libasound2-data" package of the RPi APT repository, but it was overwritten by our /etc/asound.conf. For HDMI audio to work with KMS, the "default" or "sysdefault" ALSA PCM needs to be used by players. This is usually the case, but some allow to select a specific sound card, in which case the ALSA config and plugin for IEC958 conversion is bypassed, breaking HDMI audio. Many thanks to `@Lollly2997` for reporting this issue. We are working with Amiberry on a solution for Amiberry in particular. This fix is for the underlying system level: https://dietpi.com/forum/t/19568
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v9.2
(2024-03-16)
Enhancements
dietpi-software list
concurrent to otherdietpi-software
instances, and as non-root user. This avoids an issue in DietPi-Dashboard, where openingdietpi-software
in the Terminal and switching to the Software page, caused an infinite hang.sudo usermod -s /bin/dash gogs
respectivelysudo usermod -s /bin/dash gitea
. This is now included in our default setup. Many thanks to @din14970 for reporting this missing feature: Easy updating of software titles & update notifications #6964 (reply in thread)Bug fixes
dietpi-config
from a local terminal session, was automatically stopped when exiting or logging out from the terminal session.libasound2-data
package of the RPi APT repository, but it was overwritten by our/etc/asound.conf
. For HDMI audio to work with KMS, the "default" or "sysdefault" ALSA PCM needs to be used by players. This is usually the case, but some allow to select a specific sound card, in which case the ALSA config and plugin for IEC958 conversion is bypassed, breaking HDMI audio. Many thanks to@Lollly2997
for reporting this issue. We are working with Amiberry on a solution for Amiberry in particular. This fix is for the underlying system level: https://dietpi.com/forum/t/19568@howardroark
for reporting this issue: https://dietpi.com/forum/t/nextcloud-theme-broken-after-upgrade-v9-1-1/19372apt install g++ && systemctl restart home-assistant
will fix it. Many thanks to @pdsakurai for fixing this issue in our install code: Fixed: Cannot build pip dependency 'webrtc-noise-gain' required for HA's integrations #6931