Release Notes for Alpine 3.20.0: Difference between revisions

From Alpine Linux
(Created page with "== Base System == === grub 2.12 === When upgrading existing installations using grub, make sure to update the installed bootloader before rebooting, otherwise your machine might not boot. Here are some examples for various situations assuming default setups. Don't blindly copy these examples but verify what's applicable to your system. ==== BIOS ==== For BIOS systems (x86 or x86_64) {{Cmd|# grub-install --boot-directory{{=}}/boot --target{{=}}i386-pc <var>disk</va...")
 
 
(16 intermediate revisions by 6 users not shown)
Line 3: Line 3:
=== grub 2.12 ===
=== grub 2.12 ===


When upgrading existing installations using grub, make sure to update the installed bootloader before rebooting, otherwise your machine might not boot.
When upgrading existing installations using grub on UEFI systems, make sure to update the installed bootloader before rebooting, otherwise your machine might not boot.


Here are some examples for various situations assuming default setups. Don't blindly copy these examples but verify what's applicable to your system.
The problem is that grub added new configuration that executes <code>fwsetup --is-supported</code>. The problem is that grub 2.06 does not supported the <code>--is-supported</code> argument yet, causing grub to unconditionally try to reboot into firmware.
 
Here is an example assuming the default setup. Don't blindly copy this examples but verify what's applicable to your system.
   
   
==== BIOS ====
==== EFI ====
 
{{Cmd|
# grub-install --target{{=}}<var>$target</var> --efi-directory{{=}}<var>$efi_directory</var> \
    --bootloader-id{{=}}alpine --boot-directory{{=}}/boot --no-nvram
# install -D <var>$efi_directory</var>/EFI/alpine/grub<var>$fwa</var>.efi <var>$efi_directory</var>/EFI/boot/boot<var>$fwa</var>.efi
 
}}
 
; target : The relevant [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 target] for your system
; efi_directory : Either {{Path|/boot/efi}} or {{Path|/boot}}. Run <code>awk '$2 ~ /boot/ && $3 ~ /fat|msdos/ { print $2 }' /proc/mounts</code> to confirm.
; fwa : The respective [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 firmware architecture] for your system
 
==== Short-term work-around ====
 
A short-term work-around to get the system bootable again is to restore the backup configuration:


For BIOS systems (x86 or x86_64)
{{Cmd|cp /boot/grub/grub.cfg.back /boot/grub.cfg }}


{{Cmd|# grub-install --boot-directory{{=}}/boot --target{{=}}i386-pc <var>disk</var>}}
This should allow you to boot the system again to fix it permanently. This will be reverted again when either grub or the kernel is updated again.


; disk : The block device grub has been installed to.
This will only work if <code>update-grub</code> has not been executed any more since the upgrade to grub 2.12.


==== EFI ====
== Others ==
 
=== Redis ===
Due to [https://github.com/redis/redis/pull/13157 the relicensing of Redis] to [https://redis.io/legal/rsalv2-agreement/ RSALv2]+[https://redis.io/legal/server-side-public-license-sspl/ SSPLv1], a non-free license model, the [https://spdx.org/licenses/BSD-3-Clause.html BSD-3-Clause] licensed fork [https://valkey.io/ Valkey] has replaced Redis in the main package repository.
 
A [https://pkgs.alpinelinux.org/packages?name=valkey-compat valkey-compat] package is provided with symlinks and group for easy Redis replacement.
 
The [https://pkgs.alpinelinux.org/packages?name=redis redis aport] has been moved to the community repository, with a shorter support cycle, and will not be upgraded past 7.2.x due to the license change.
 
Another replacement alternative, the [https://spdx.org/licenses/LGPL-3.0-only.html LGPL-3.0-only] licensed fork [https://redict.io/ Redict] is also available in the community repository.
 
 
=== yq ===
yq was renamed to yq-go. https://gitlab.alpinelinux.org/alpine/aports/-/issues/16052
 
=== aws-cli ===
Due to incompatibility issues with Python 3.12, aws-cli has been temporarily disabled until the issue is resolved by upstream. See the corresponding problem at upstream: https://github.com/aws/aws-cli/issues/8342


{{Cmd|# install --target{{=}}<var>target</var> --efi-directory{{=}}"<var>efi_directory</var>" --bootloader-id{{=}}alpine --boot-directory{{=}}"/boot --no-nvram}}
=== GNOME 46 ===


; target : The relevant [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in?ref%20type=heads target] for your system
New upstream release of GNOME.
; efi_directory : Either {{Path|/boot/efi}} or {{Path|/boot}}

Latest revision as of 08:44, 8 May 2024

Base System

grub 2.12

When upgrading existing installations using grub on UEFI systems, make sure to update the installed bootloader before rebooting, otherwise your machine might not boot.

The problem is that grub added new configuration that executes fwsetup --is-supported. The problem is that grub 2.06 does not supported the --is-supported argument yet, causing grub to unconditionally try to reboot into firmware.

Here is an example assuming the default setup. Don't blindly copy this examples but verify what's applicable to your system.

EFI

# grub-install --target=$target --efi-directory=$efi_directory \ --bootloader-id=alpine --boot-directory=/boot --no-nvram # install -D $efi_directory/EFI/alpine/grub$fwa.efi $efi_directory/EFI/boot/boot$fwa.efi

target
The relevant target for your system
efi_directory
Either /boot/efi or /boot. Run awk '$2 ~ /boot/ && $3 ~ /fat|msdos/ { print $2 }' /proc/mounts to confirm.
fwa
The respective firmware architecture for your system

Short-term work-around

A short-term work-around to get the system bootable again is to restore the backup configuration:

cp /boot/grub/grub.cfg.back /boot/grub.cfg

This should allow you to boot the system again to fix it permanently. This will be reverted again when either grub or the kernel is updated again.

This will only work if update-grub has not been executed any more since the upgrade to grub 2.12.

Others

Redis

Due to the relicensing of Redis to RSALv2+SSPLv1, a non-free license model, the BSD-3-Clause licensed fork Valkey has replaced Redis in the main package repository.

A valkey-compat package is provided with symlinks and group for easy Redis replacement.

The redis aport has been moved to the community repository, with a shorter support cycle, and will not be upgraded past 7.2.x due to the license change.

Another replacement alternative, the LGPL-3.0-only licensed fork Redict is also available in the community repository.


yq

yq was renamed to yq-go. https://gitlab.alpinelinux.org/alpine/aports/-/issues/16052

aws-cli

Due to incompatibility issues with Python 3.12, aws-cli has been temporarily disabled until the issue is resolved by upstream. See the corresponding problem at upstream: https://github.com/aws/aws-cli/issues/8342

GNOME 46

New upstream release of GNOME.

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Release_Notes_for_Alpine_3.20.0&oldid=26697"