Beta v9.11.0 #7415
Merged
Beta v9.11.0 #7415
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
Workaround failing systemd services in emulated Trixie containers if ImportCredential is used. Workaround failing chpasswd in ARMv6/7 Trixie containers, with AppArmor on recent Ubuntu host. Create tmpfs mounts with 0755 mode, as the default is 1777.
thanks @jkronborg for the hint
initramfs-tools was chosen initially, since the (new) RPi kernel packages forcefully triggered the generation of an iniramfs image, while the RPi kernel does not require it, and tiny-tinitramfs images are some orders of magnitudes smaller. However, in between, the RPi kernel packages set INITRD=No if SKIP_INITRAMFS_GEN=yes is given, so the initramfs generation can be skipped. This exact thing does not work with tiny-initramfs until including Bookworm. Support for INITRD=No has been added for Trixie: https://salsa.debian.org/debian/tiny-initramfs/-/merge_requests/2 Additionally, tiny-initramfs cannot satisfy the dependency of a 64-bit kernel on a 32-bit OS: #7402 (comment)
libary -> library
and merge master back to dev
On Quartz64 and VisionFive 2, filesystem type and label can fail to be detected on this early boot stage. Likely it has something to do with the missing initramfs and hence relatively quick boot into init stage: #6838
…rst run setup During non-interactive first run setup, allow up to 3 retries with 5 seconds delay. The [email protected] has started, but the DHCP client may require some more time.
and add changelog entries for this fix, as well as potential network check failures on first boot.
Replace dash with plus symbol for version suffix, to avoid latest main commit to be shown as latest server version in web UI: dani-garcia/vaultwarden#4936 (reply in thread)
…n Quartz64/Star64/VisionFive 2
If the setup partition is detected directly, no additional log will be done. The additional "1/3" log now means that additional 0.5 seconds are waited, before checking again, and the last "3/3" log means that overall 1.5 seconds has been waited, before the final check is done.
In just replicated case, it was actually wpa_supplicant which took longer to connect, not blocking ifup, while the IP was static.
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 v9.11.0
(2025-02-22)
Bug fixes
wpa_supplicantor DHCP client took a little longer to receive an IP address, withoutifupfurther halting the script. In case ofAUTO_SETUP_AUTOMATED=1indietpi.txt, the very first network check is assured to try at least 4 times, with a 5 seconds delay between each attempt.linux-image-rpi-v8kernel on 32-bit images failed. Many thanks to @SOULV1CE for reporting this issue: Unable to locate package linux-image-rpi-v8 #7402dietpi-softwareoptions, it is offered to uninstall them.