-
-
Notifications
You must be signed in to change notification settings - Fork 495
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.32.0 #3733
Merged
Beta v6.32.0 #3733
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 | Node.js: Use fixed own installer fork for now: taaem/nodejs-linux-installer#11
+ CHANGELOG | DietPi-Drive_Manager: For NTFS mounts, the "big_files" mount option is now added by default, which reduces CPU load and by this may increase performance. Many thanks to @balexandrov for suggesting this enhancement: #3330 (comment)
+ DietPi-Drive_Manager | For NTFS mounts, add "big_files" option by default which prevents splitting write buffers into 4k chunks. This is generally seen as stable and is the default in new libfuse3: https://unix.stackexchange.com/a/544864
+ DietPi-Obtain_HW_model | RPi: Remove special model names like alpha, beta or first ECN0001, but differentiate by type A and B only, to simplify statistics. The exact revision can always be estimated through the revision code, if it should become relevant in an individual case. + DietPi-Obtain_HW_model | RPi: Merge code for assigning identical hardware info + DietPi-Obtain_HW_model | RPi: Reduce the risk that A+ total memory is estimated wrong due to theoretical larger GPU memory split. 262144 KiB is really the upper boarder of what an 256M model can have, probably even 245760 (minus 16 MiB min GPU memory) would be thinkable or using vcgencmd to estimate the exact values (overkill?). + DietPi-Obtain_HW_model | Pinebook: We do not add and name suffix anymore as our image works on all revisions + DietPi-Survey_report | Add DietPi v6.32 support + DietPi-Survey_report | Merge old and new hardware model names to cleanup statistic
+ DietPi-Software | Python pip: We migrated this software selection to a Python3/pip3 install only, due to Python2 EOL in 2020/01. Where possible, dependant software selections have been migrated to Python3 builds, where not possible, Python2/pip2 is installed separately for now. We hope that most affected software titles will do Python3 releases soon, otherwise we will remove them form our portfolio, at latest in spring 2021. The strongest reason for this is that next Debian Bullseye (summer 2021) will not ship Python2 packages anymore. + DietPi-Software | SABnzbd: Migrated to a Python3-based install. + DietPi-Software | OctoPrint: On Debian Buster and up, migrated to a Python3-based install. + DietPi-Software | HTPC Manager: Resolved an issue where install failed due to missing build-essential dependency. + DietPi-Software | HTPC Manager: Resolved an issue where the internal updater failed due to missing git meta files. + DietPi-Software | EmonPi: Resolved a failing primary UART activation on install. + DietPi-Software | Mopidy: The official Buster repo now supports ARMv8/arm64 as well + DietPi-Software | "apt-cache show package" succeeds as well if package is listed as (optional) dependency/conflict/... by another package, hence is not a reliable measure. In case of python3-distutils on Stretch this causes an install failure if stretch-backports suite has been added, which contains a few packages that list python3-distutils as optional dependency aside of python3 << 3.6.something where Distutils was moved from stdlib into an own package. Allow to succeed if another package "provides" it, like php7.3-apcu provided by php-apcu or awk provided by mawk and gawk. + DietPi-Software | Disable all Python2-only titles for Bullseye, which does not serve Python2 packages anymore + DietPi-Software | Several uninstall enhancements
+ Coding | Replace bc decimal calculation with bash-internal printf conversion + Coding | Several minor enhancements around prior bc usage + DietPi-Cloudshell | Do not disable CPU scene on VM. Most values are "N/A" but usage bar and process count are shown correctly. Let user decide if it's worth it or not.
+ DietPi-Software | Cuberite: Adjust download link as of: "Please DO NOT rely on the links below to represent the correct download location for Cuberite at all times, instead use the official download link: https://download.cuberite.org/linux-armhf-raspbian/Cuberite.tar.gz" + DietPi-Software | Cuberite: Do not run as "dietpi" group since Cuberite does not need to access (R/W) media or downloads and file servers/downloaders/media players do not need to access (R/W) Cuberite files. Lets keep using "dietpi" group for media, downloads and "regular" userdata only, not for software internal data, config and executables.
+ DietPi-Software | Nginx: Use new 512 MiB default max upload size, as a compromise to keep performance up and SD card writes low on usual smaller uploads (pictures, documents, ...), while not risking RAM overload (with swap file enabled) in peek times. Uploads for larger files (disk images, video files, ...) usually require an external drive to hold PHP uploads, either through a large swap file or directly for all uploads.
+ DietPi-Software | PHP: Move session files to tmpfs outside of /tmp and /var/tmp to /run/php_sessions by default + DietPi-Software | PHP: Move tmp upload dir back to tmpfs but limit default max upload size, discuss and find balance between performance, disk (SD card) writes and RAM over-usage. + DietPi-Software | PHP: Assure that opcache.interned_strings_buffer is never larger than half of opcache.memory_consumption: #2293 + DietPi-Software | ownCloud/Nextcloud: On <1 GiB devices assure at least 512 MiB swap space are available to stand 512 MiB file uploads + increased PHP cache and session file usage
+ DietPi-Software | Align max memory usage across Java applications + DietPi-Software | Komga: Disable file logging, reduce log level to warning. Logs can be seen via "journalctl -u komga" + DietPi-Software | Komga: Remove obsolete config options, add "remember me" login feature: #3403 (comment)
+ DietPi-LetsEncrypt | Lighttpd: Update SSL cipher to still Stretch-compatible intermediate recommendations and remove deprecated SSL compression setting, even it was commented + DietPi-LetsEncrypt | Lighttpd: Apply configs via /etc/lighttpd/conf-available/ and lighty-enable|disable-mod commands and use proper priority prefixes for file names. As well use "dietpi-" prefixes as we start to do for all config files we place. + DietPi-LetsEncrypt | Lighttpd: Further config file tuning: "https" instead of "letsencrypt" in case we want to support other CAs at a later time and since it can be changed by only changing cert + key file paths; "https_redirect" instead of "redirect" to separate it more clearly from module configs like "mod_redirect" in Apache.
+ DietPi-PREP | Upgrading haveged entropy daemon to fix an issue on ARM with the version shipped by Debian Buster: jirka-h/haveged#7
+ DietPi-Patch | Upgrading haveged entropy daemon to fix an issue on ARM with the version shipped by Debian Buster: jirka-h/haveged#7
+ DietPi-Config | RPi: Remove deprecated "Max USB current" option: raspberrypi/documentation#1655
+ DietPi-Software | HTPC Manager: Migrate to new Python3-compatible fork: https://github.com/gmiranda/HTPC-Manager + DietPi-Software | HTPC Manager: Fix After=dietpi-boot.service + DietPi-Software | HTPC Manager: Remove all untracked files on update, excluding userdata, especially the compiled module .pyc files need to be removed. + DietPi-Software | HTPC Manager: Add a syslog identifier to have logs prefixed with "HTPC Manager" instead of with "python"
+ DietPi-Config | Show "available" memory as "free" memory as this excludes cache/buffer and hence fits much better what one would expect. The same is true for "used" memory, which should not include file system cache and buffer. + DietPi-Config | Fix KiB to MiB conversion for memory values
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.32.0
(27/08/20)
API Changes
Changes / Improvements / Optimisations
Bug Fixes