-
-
Notifications
You must be signed in to change notification settings - Fork 499
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
Beta v7.2.1 #4415
Merged
Beta v7.2.1 #4415
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
+ DietPi-Software | WiringPi: Remove NanoPi support, as FriendlyARM's WiringNP works (reliable) with their kernel only, while we use Armbian or Debian kernel + DietPi-Software | phpBB: Install v3.3.4 + DietPi-Software | HAProxy: Install v2.4.0 + DietPi-Software | Grafana: On ARMv6 install v7.5.7 + DietPi-Software | Unbound: Remove cache files on uninstall + DietPi-Software | PiJuice: Remove variable files on uninstall
+ DietPi-Software | Amiberry: Disable for ARMv8 since we don't have aarch64 builds yet + DietPi-Software | Amiberry: WHDLoad database updates do not use "route" anymore, but wget instead, to check for network connectivity. It was used before as well for the downloads. While wget is pre-installed on DietPi, we don't use it anymore in our scripts, so there might be a day coming when we do not pre-install it anymore. Hence add it to Amiberry dependencies as precaution. + DietPi-Software | GPU: Do not install RockChip Mali drivers for RK3399 and ASUS Tinker board (RK3288) anymore. Without matching development libraries compiled binaries are not assured to function and the RockChip packages were meant for their Stretch images. From Bullseye on, the Mesa packages by Debian work very well and while they might be slower on Buster, at least it is assured that it works with all binaries compiled against the Debian Mesa development packages. + DietPi-Software | LXDE: Do not install xcompmgr automatically. While it is a lightweight composite manager, especially when invoked with "-a" flag, it does not add great visual enhancements either and still slows down X rendering. When LXDE is installed, a fast lightweight desktop is expected, so let's do not install this optional overhead. Any composite manager can be installed and configured later on, depending on personal beauty vs performance needs. We might add a note to our docs instead about X compositing in general.
+ DietPi-Drive_Manager | Use "-M" options instead of "-T". The first defines the exact mount point while the second would search for any parent directory to be the mount point, if the given path is none. With "-M" we are hence a bit more explicit, which was the goal to avoid handling/parsing unintended drive/filesystem information.
This was referenced May 25, 2021
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.
Beta v7.2.1
(2021-05-25)
Changes since v7.2.0
-a
option, which is limited server-side composition. But that is still slower than no composition. And on faster SBCs or desktop PCs, users might want to have full composition, so installing a default autostartxcompmgr -a
entry creates extra work for users which see their composition manager failing to start.Fixes since v7.2.0
Since all are either minor invisible changes or v7.2.0 regression fixes, no additional CHANGELOG.txt entries are required IMO.