Skip to content
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.4.1 #4577

Merged
merged 17 commits into from
Jul 22, 2021
Merged

Beta v7.4.1 #4577

merged 17 commits into from
Jul 22, 2021

Conversation

MichaIng
Copy link
Owner

@MichaIng MichaIng commented Jul 22, 2021

Beta v7.4.1

(2021-07-23)

Changes since v7.4.0

  • DietPi-Update | A new live patching system has been implemented. This allows us to ship little fixes and updates, that are safe to apply with a one-line command, until the next DietPi version is released. Live patches are checked for together with DietPi updates and a notification is shown in the login banner as well, when new live patches have been found. When available, each patch can be individually applied or dismissed and the login banner won't bother you again about patches that you have seen in the dietpi-update menu already, regardless whether you applied them or not.
  • DietPi-Software | Komga: Obsolete entries have been removed from the default config and file hashing will be disabled on new installs. Many thanks to @quyentruong for contributing this change: Update Komga new setting for v0.107.0 #4570

Fixes since v7.4.0

MichaIng and others added 14 commits July 18, 2021 23:22
+ DietPi-Globals | G_AGUP: Allow the suite if repos to change without requiring interactive confirmation. Otherwise after the upcoming Bullseye release all G_AGUP calls will fail until "apt(-get) update" is called once manually and the suite change (Stretch: oldstable => oldoldstable, Buster: stable => oldstable, Bullseye: testing => stable) is confirmed. We could try to solve this with some magic, checking the /var/lib/dpkg/lists/*_InRelease files and compare with those in the repository, but 3rd party repos and mirrors make this very complicated and unreliable, e.g. archives.raspberrypi.org Bullseye suite is called "unstable" instead of "testing", and on a G_AGUP call, once repo could have done the transition already (Debian first), while the other might take some days longer (Raspberry Pi, 3rd party software repos). Also a suite name change is naturally happening every two years and does not imply any risk or change to the content, so it is not more than an information, that may even confuse inexperienced users unnecessarily. Luckily we do not use the suite names (testing, stable, oldstable) in *.list files, which would imply a distro upgrade with the next APT upgrade, where an interactive warning and confirmation did make sense.
+ BRANCH_SYSTEM | Minor wording and highlight shell code
+ DietPi-Pre-patches | Update APT repositories once, accepting the suite change, when Bullseye has been released, as pre-v7.4 G_AGUP does not include this yet.
+ DietPi-Software | Komga: Remove obsolete config entries related to unused H2 database
+ DietPi-Software | Komga: Disable file hashing by default to reduce system resource usage. File hashing enables Komga to keep database entries (metadata, read states, ...) associated on file moving and renaming, hence it needs to be documented that this is actively disabled on installs via DietPi-Software.
+ CHANGELOG | Komga: Obsolete entries have been removed from the default config and file hashing will be disabled on new installs
+ DietPi-Set_swapfile | Remount /tmp tmpfs only when it is currently a tmpfs already. Else the remount can fail when the fstab entry has been changed to tmpfs but the mounted filesystem is a different one. The change will become effective then after reboot, as we must not unmount /tmp and loose its content.
+ CHANGELOG | DietPi-Set_swapfile | Resolved an issue where remounting the /tmp tmpfs filesystem failed, if another filesystem type was mounted at /tmp
+ DietPi-PREP | Align mount source for /tmp with fstab entry an be more explicit when checking for /tmp mount point. Both should not have an effect, but better be safe then sorry
+ DietPi-Update | Add initial live patches to remote version file to test the implementation
+ DietPi-Update | Add support for live patches, when present on currently applied Git branch
+ DietPi-Banner | Show new available DietPi live patches in banner, based on flag file
+ DietPi-PREP | Apply live patches via new mechanism and store info of already applied patches in .version file. Do this as early as possible, to have bugs fixed before using the scripts. Copy the separately stored image version file back in place, after .version got removed during a later cleanup step.
+ CHANGELOG | DietPi-Update: A new live patching system has been implemented. This allows us to ship little fixes and updates, that are safe to apply with a one-line command, until the next DietPi version is released. Live patches are checked for together with DietPi updates and a notification is shown in the login banner as well, when new live patches have been found. When available, each patch can be individually applied or dismissed and the login banner won't bother you again about patches that you have seen in the dietpi-update menu already, regardless whether you applied them or not.
+ DietPi-Update | Fix live patch syntax
+ DietPi-Update | Apply single live patch at a time
+ DietPi-PREP | Apply a single live patch at a time
+ DietPi-Banner | Reset colour after live patch notification and colour header notification as well
+ DietPi-Update | Fix removal of live patches flag file
@MichaIng MichaIng added the Beta 🧪 Issues specific to the Beta branch testing label Jul 22, 2021
@MichaIng MichaIng added this to the v7.4 milestone Jul 22, 2021
+ DietPi-Pre-patches | Apply Bullseye pre-patch on v6 systems as well
MichaIng added 2 commits July 23, 2021 01:03
+ RC up
+ DietPi-Globals | Default RC up
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Beta 🧪 Issues specific to the Beta branch testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Open Beta v7.4 | Please help testing and hardening the upcoming release
2 participants