Release Notes for Alpine 3.20.0: Difference between revisions

From Alpine Linux
(Add information about Redis, Valkey and Redict)
m (fix typo)
Line 35: Line 35:


=== Redis ===
=== Redis ===
Due to [https://github.com/redis/redis/pull/13157 the relicinsing 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.
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 replcament.
A [https://pkgs.alpinelinux.org/packages?name=valkey-compat valkey-compat] package is provided with symlinks and group for easy Redis replcament.

Revision as of 10:16, 5 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 replcament.

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 avalable in the community repository.