-
-
Notifications
You must be signed in to change notification settings - Fork 503
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 v6.27.0 #3226
Merged
Beta v6.27.0 #3226
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
+ Replace fdisk and gdisk commands by their command-line counterparts sfdisk and sgdisk, which are more suitable for a script
+ DietPi-Set_CPU | Exit script immediately (before loading DietPi-Globals) based on "scaling_available_governors" file existence, which, besides VMs, includes chroot and container environments as well + DietPi-Set_CPU | Consequently print which settings are about to be applied and which are not supported, in case + DietPi-Set_CPU | Since when we handle "GPU" governors? :) + DietPi-Set_CPU | Further coding and output/wording consistency
+ Do not add version string to image file to easier scripting and since this still confuses users. The image file version should be generally irrelevant since it updates to current DietPi on first boot automatically. If for some reason this information is wanted, it can be derived from the creation date and contained .version file. + Do not offer backup or try to rename image file, if source image matches output image already, which is high likely in case of scripting. + Minor coding: Use a single variable for .img and .7z file.
+ DietPi-Globals | G_WHIP: Never increase whiptail y size to max, since this looks always strange, e.g. in case of short log files, filling only the upper part of the whiptail text box. Always use auto y size estimation instead. + DietPi-Globals | G_WHIP: Make input mode "0" the default for G_WHIP_INIT, which is required in most cases.
+ DietPi-PREP | When we remove non-required systemd units, remove them only if they do not belong to any kept APT package, else mask. This prevents future service reinstall and especially reactivation on package upgrades, in case of ARMbian services harmful in combination with DietPi-RAMlog and tmpfs + ARMbian zRam double mount: ``` Setting up linux-buster-root-next-tinkerboard (5.95) ... Created symlink /etc/systemd/system/sysinit.target.wants/armbian-ramlog.service → /lib/systemd/system/armbian-ramlog.service. ```
+ DietPi-Software | Amiberry: Update to current upstream v3.0.4, including Stretch binaries and merge SDL2 libraries right into the Amiberry install dir + DietPi-Software | Amiberry: Download archives are not split per platform to provide smaller downloads and less file moving hassle + DietPi-Software | Amiberry: autostart.uae has been removed, as it contained obviously auto-created defaults from an RPi1 instance and non-existent file paths. Re-evaluation if a default file makes sense should be done, then it should be named default.uae, which is used by Amiberry automatically, if present, since some versions ago + DietPi-Patch | Reinstall/update Amiberry and be more verbose on what we're patching (a tiny start)
+ DietPi-Software | Mosquitto: Since Buster, the APT package ships a systemd unit. On Stretch, use the upstream systemd unit, which includes some enhanced feature, e.g. systemd PID file handling/notify, start on network-online.target instead of network.target, reload feature, documentation etc: https://github.com/eclipse/mosquitto/tree/master/service/systemd + DietPi-Software | Apply safe and clean systemd unit removal to more software uninstalls (WIP)
+ DietPi-Patch | DietPi-Update will save version info to /DietPi/dietpi/.version via G_VERSIONDB_SAVE (at update start and) after every subversion patch from v6.27 on. This allows DietPi-Patch to rely on DietPi-Globals loading the correct info without requiring any input argument to override the subversion. As well it assures that subscripts, which load .version/globals anyway, have the correct info based on last applied subversion patch. In case of DietPi-Patch error, an update rerun can continue with the failed subversion patch instead of repeating all incremental patches from initial subversion on. + DietPi-Patch | Minor coding and wording
+ DietPi-Update | Store version info after every incremental patch to allow multi-version updates continuing at current step, in case of failure of abortion. Transparently inform user when reducing subversion string and always print correct new version to avoid confusion. + DietPi-Patch | patch_file can now read correct version info from file, hence does not require an input argument anymore. However for debugging and backwards compatibility it will still handle inputs to override the saved version string, read from file.
+ DietPi-Software | Home Assistant: Add simple HA update script which can be called by any sudo capable user to update the HA module within pyenv + DietPi-Software | Home Assistant: Use network-online.target instead of network.target, since HA requires active network to launch and be available. network-online.target is available since Debian Stretch, which is the reason we did not use it while still supporting Jessie.
+ DietPi-Software | Replace G_CHECK_URL against first sources.list entry with purge connectivity test and separate DNS resolver test via ping. This solves an issue where sources.list parsing failed when [arch=...] was specified and allows better debugging. The sources list entries themselves are checked and error handled by G_AGUP already. Ping target IP for connection test and domain for DNS resolver test can be set via dietpi.txt, default is Cloudflare DNS IP+domain which should be most reliable and very fast all over the world.
+ DietPi-Software | When running "dietpi-software reinstall <ID>", check first if title is currently installed, before checking arch/device/distro support. Without this, when calling reinstalls from DietPi-Update (patch_file), users see "[FAILED] Software not supported", which is confusing at this point.
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 v6.27.0
(08/12/19)
Changes / Improvements / Optimisations
@NastySpill
for reporting an underlying issue: https://dietpi.com/phpbb/viewtopic.php?f=11&t=6862Bug Fixes
@NZRob
fore reporting this issue: https://dietpi.com/phpbb/viewtopic.php?f=11&t=6550@slopsjon
,@tyjtyj
and@pakikje
for reporting this issue: https://dietpi.com/phpbb/viewtopic.php?f=11&t=6531, https://dietpi.com/phpbb/viewtopic.php?p=20408#p20408Known/Outstanding Issues