Beta v10.0.0 #7875
Draft
Beta v10.0.0 #7875
+967
−2,713
Conversation
This file contains hidden or 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
Locally stored package lists are invalidated if the respective sources.list entries do not exist anymore, hence packages cannot be installed at this section of the code. Install it as part of the dist-upgrade step, which upgrades the fail2ban package as well. Use more transparent variable names for conditional arguments of upgrade and dist-upgrade calls.
The following breaking changes are necessarily implied: - Dropped support for SBCs with ancient kernel versions which cannot run Debian Bookworm properly, or Trixie at all: 32-bit requires Linux >=5.6 for time64 syscalls. This affects the **NanoPi M2/T2/Fire2** and **NanoPi M3/T3/Fire3** series, which both use some Samsung SoC which never got mainline support, as well as the Sparky SBC which uses an even older vendor kernel 3.10.38. Those were support by us until Debian Bullseye only, since WiFi was already not functional well with removed CRDA on Bookworm, as the <=4.14 kernel is not able to pull allowed frequencies from the regulatory database by itself, and applies a limited global profile instead. - For simplicity and reduce potential issues with mixed support for legacy and modern RPi kernel stack, the migration to the modern one is now mandatory, and support for the legacy stack and anything which relies on `libraspberrypi0` has been removed. - The above change implies the removal of **RPi Cam Web Interface**, which (its shipped `raspimjpeg` binary) depends on the legacy MMAL camera API, which is not available with the new RPi kernel stack. Upstream development stalled since some years, without any community taking over in sight. There are some mostly private/situational forks which add support for libcamera using modern (high-level) libraries, but none of them showed any continued progress after their short-term purpose/even was done. ownCloud and Pydio are left in place for now. Maybe we find time to implement ownCloud Infinite Scale and Pydio Cells as direct replacements including migration. Unrelated change: - Temporary workaround for failing HA build or service start all due to an incompatible latest `pycares` version, solved in HA for next release. `cmake` is added as new build dependencies where the wheel is not available. Some test installs: - https://github.com/MichaIng/DietPi/actions/runs/20339705047 - https://github.com/MichaIng/DietPi/actions/runs/20339734526 - RISC-V Forky failure is unrelated. systemd v259 made it, after already several necessary workarounds and limitations, impossible to use QEMU emulation for a container with systemd: https://gitlab.com/qemu-project/qemu/-/issues/3250 - Manual test with Bullseye VM succeeded, including migration to compat branch as well as automatic migration back to master branch, after Bookworm upgrade. Compat branch "9" (DietPi 9) created for DietPi 7 and Debian 11 Bullseye systems: 9ee6cf8 - Once the DietPi update, and in case the Debian upgrade, habe been applied there, systems are migrated back to master branch automatically. - DietPi 6 and Debian 10 Buster systems were/are further redirected to the compat branch "8". - DietPi <6.14 and Debian 8 Stretch were/are further redirected to the compat branches "pre-v6.14" and "stretch" respectively.
* Orange Pi 3B v2.1 uses a Broadcom WiFi/BT chip, hence skip the UNISOC/Spreadtrum 3rd party driver hassle there. Implement revision detection a way that everything that is not v1.1 is treated as v2.1. * DietPi-Installer: Do not add /etc/modules-load.d/dietpi-enable_wifi.conf explicitly, as this is done by `/boot/dietpi/func/dietpi-set_hardware wifimodules enable` already. In case of Orange Pi 3B, as long as it is not executed on a real revision 2.1, this is not the case, but a patch looks like this is not even needed on v1.1, as the device tree nodes might trigger loading of this driver automatically: armbian/build@0b3a1a0
Add dummy G_HW_REVISION to /boot/dietpi/.hw_model, which is now used for Orange Pi 3B in our scripts.
and add a fallback for G_HW_UUID generation if /proc/sys/kernel/random/uuid cannot be used, which seems to be the case in some containers.
G_CONFIG_INJECT works only if the file exists already, and we explicitly want to create this file from scratch.
The Raspbian Forky suite is availalable now.
…an mirror as we did in all other cases already: an alignment. The trailing slash is truncated internally anyway. We tend to add it for fully qualified URLs in other contexts to avoid a potential 301 redirect, but APT mirrors are never accessed like that, but only the (In)Release and Package(.*) files for the repo suite and component.
Remove Blynk Server and YaCy exclusion for retest.
aiodns has been bumped to a version which pins pycares as needed.
A leftover from dropping Debian Bullseye (PHP 7.4) support
Co-authored-by: MichaIng <[email protected]>
Co-authored-by: MichaIng <[email protected]>
Co-authored-by: MichaIng <[email protected]>
No actual values are changed, but the commeted values, including some which have been removed upstream + reordering.
and move to DEB822 format + ASCII-armored key
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.
No description provided.