-
-
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 v7.7.1 #4829
Merged
Beta v7.7.1 #4829
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 | Kodi: Since Bullseye, Kodi is built with GBM support, hence does not require an X server anymore. + DietPi-Software | Kodi: Remove device restrictions: Generally Kodi runs on all devices, whether performance is sufficient may be decided by user instead of by us. Especially since Bullseye with GBM support and recent Mesa drivers, it is often quite good, tested successfully on a pretty bad VM without deducated GPU and no hardware support passed through. + DietPi-Software | Kodi: To assure that Kodi installs on all Odroids, be more compatible with missing packages from Meverics repository, respectively skip install of special Odroid packages and use Debian's Kodi, if required, e.g. currently on Bullseye. + DietPi-Software | X.Org X Server: Similar to Kodi, skip install of Odroid drivers and libraries if those are not available, in which case the Mesa drivers are used.
+ CHANGELOG | Kodi: On Debian Bullseye, with Kodi 19, GBM support is present by default, which means that Kodi can be started without a wrapping X server. This is now done by default when starting Kodi outside of a desktop session, including the dietpi-autostart option. This also means that an X server is not installed anymore as a dependency of Kodi, but only as a dependency of a deskop environment. + CHANGELOG | Kodi: It can now be installed on all devices. In some cases, video playback performance may be bad, depending on the GPU, whether good drivers are available, and on the video quality, of course. However, it should be our users who evaluate whether it's sufficient or not, instead of us. With Debian Bullseye, new Mesa drivers and Kodi 19 started via GBM, performance should be much better than it was with older Debian/package versions.
+ DietPi-Update | Be less verbose on live patches, as the system in general has been proven reliable + DietPi-Update | Only show the live patches menu when any applicable and not applied live patches have been found instead of when any live patches have been found + DietPi-Update | Currently, when doing an RC update (beta/dev branch updates) or reapplying the last update via "dietpi-update -1", pre-patches intended for the target version may not be reapplied. To solve this, the version strings which were possibly decreased updater-internally are not passed an used by the pre-patches script.
+ DietPi-Software | Kodi: Since Bullseye, Kodi is built with GBM support, hence does not require an X server anymore. + DietPi-Software | Kodi: Remove device restrictions: Generally Kodi runs on all devices, whether performance is sufficient may be decided by user instead of by us. Especially since Bullseye with GBM support and recent Mesa drivers, it is often quite good, tested successfully on a pretty bad VM without deducated GPU and no hardware support passed through. + DietPi-Software | Kodi: To assure that Kodi installs on all Odroids, be more compatible with missing packages from Meverics repository, respectively skip install of special Odroid packages and use Debian's Kodi, if required, e.g. currently on Bullseye. + DietPi-Software | X.Org X Server: Similar to Kodi, skip install of Odroid drivers and libraries if those are not available, in which case the Mesa drivers are used. + DietPi-Software | Kodi: Error-handle uninstall steps + DietPi-Software | Kodi: Merge install and config code blocks
+ DietPi-JustBoom | Fix MPD settings detection when settings are not present + DietPi-JustBoom | Add the ability to set the number of output channels + DietPi-JustBoom | Add the ability to not enforce a format value, preserving the input stream format or leaving conversion to ALSA + DietPi-JustBoom | Add the ability to reset the audio buffer for default. It was 2 MiB in the past, but now is 4 MiB. Also fix the unit as it is KiB, not bytes + DietPi-JustBoom | Remove unused CAVA_ENABLED variable, but do not restart CAVA whenever settings are applied. We have dedicated (re)start/stop CAVA options which can be used to control CAVA instead, including, if wanted, a restart when settings were changed. + DietPi-JustBoom | Align menu format, merge/remove some non-required variables and steps and other minor coding enhancements
+ General | Worked around an issue on Debian Stretch where "systemctl enable/disable --now" does not start/stop the service in certain circumstances. This is solved within our error handler "G_EXEC", hence when manually calling systemctl you may still face this: #4815 + General | For the above workaround to be effective, all related systemctl calls have been wrapped into our G_EXEC error handler, in case of DietPi-Software uninstall steps along with a lot of other uninstall steps, to be both, more transparent and assure cleaner uninstalls
I guess change log entry for File Browser change missing 😃 |
Is this worth a note? I mean it affects only fresh installs. |
just for documentation. But fine to leave it out. |
On the other hand, why not 😄: b98d0a9 |
+ General | The /boot/dietpi/func/obtain_network_details script has been removed, including the related /run/dietpi/.network file to obtain network details. All uses of these files have been replaced with the new DietPi-Globals G_GET_NET function. + DietPi-Patches | Remove obsolete /boot/dietpi/func/obtain_network_details + DietPi-Patches | GMediaRender: Patch service + DietPi-Config | Enter WiFi adapter menu after it has been enabled + DietPi-Config | Do not copy /etc/network/interfaces to /tmp to read interface info from tmpfs but read it from disk location directly. After first access this file is in filesystem cache so that reading it is as fast as from tmpfs. + DietPi-Patches | Extend wg0 patch to replace previous patches and remove those in turn.
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.7.1
(2021-10-14)
Changes since v7.7.0
Fixes since v7.7.0
@elevader
for reporting this issue: https://dietpi.com/phpbb/viewtopic.php?t=9426@jowelboy
for reporting this issue: https://dietpi.com/phpbb/viewtopic.php?t=9531