Release Notes for Alpine 3.20.0 - Revision history

Fossdd: add prev/next page

2025-06-25T14:08:51Z

add prev/next page

← Older revision		Revision as of 14:08, 25 June 2025
Line 82:		Line 82:
	* Sway 1.9		* Sway 1.9

			<hr><center>[[Release Notes for Alpine 3.19.0\|← Previous page: Release Notes for Alpine 3.19.0]] — [[Release Notes for Alpine 3.21.0\|Next page: Release Notes for Alpine 3.21.0 →]]</center>
	[[Category:News]]		[[Category:News]]

Fossdd: add aws-cli again

2024-05-26T14:29:45Z

add aws-cli again

← Older revision		Revision as of 14:29, 26 May 2024
Line 48:		Line 48:
	=== aws-cli ===		=== 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 upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]		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 upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]

			{{Note\|aws-cli has been added to the community repository again. Thanks for the patience!}}

	=== GNOME 46 ===		=== GNOME 46 ===

Encode: Added page to Category:News

2024-05-24T05:06:51Z

Added page to Category:News

← Older revision		Revision as of 05:06, 24 May 2024
Line 79:		Line 79:
	* R 4.4		* R 4.4
	* Sway 1.9		* Sway 1.9

			[[Category:News]]

Ncopa: add kde 6

2024-05-22T10:24:11Z

add kde 6

← Older revision		Revision as of 10:24, 22 May 2024
Line 54:		Line 54:

	Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.		Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.

			=== KDE 6 ===

			KDE Plasma has been upgraded to Plasma 6, bringing the major update to Qt6 with it. This also includes applications from KDE Gear although some individual applications remain on Qt5 for now. The update makes the Wayland session the default and this Alpine release is the last one to support the X11 session.

	=== podman [https://github.com/containers/podman/releases/tag/v5.0.0 5.x] ===		=== podman [https://github.com/containers/podman/releases/tag/v5.0.0 5.x] ===

Omni: podman 5.x

2024-05-20T22:42:32Z

podman 5.x

← Older revision		Revision as of 22:42, 20 May 2024
Line 54:		Line 54:

	Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.		Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.

			=== podman [https://github.com/containers/podman/releases/tag/v5.0.0 5.x] ===

			The default tool for rootless networking has been swapped from <code>slirp4netns</code> to
			<code>pasta</code> (<code>passt</code>) for improved performance. As a result, networks named pasta are
			no longer supported.

	== Upgrades ==		== Upgrades ==

Omni: /* Upgrades */ rust 1.78, not 1.7.8

2024-05-20T22:27:40Z

Upgrades: rust 1.78, not 1.7.8

← Older revision		Revision as of 22:27, 20 May 2024
Line 66:		Line 66:
	* Racket 8.13		* Racket 8.13
	* Ruby 3.3		* Ruby 3.3
	* Rust 1.~~7.8~~		* Rust 1.78
	* R 4.4		* R 4.4
	* Sway 1.9		* Sway 1.9

Jirutka: Improve formatting

2024-05-20T21:43:38Z

Improve formatting

← Older revision		Revision as of 21:43, 20 May 2024
Line 44:		Line 44:

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

	=== aws-cli ===		=== 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 upstream: https://github.com/aws/aws-cli/issues/8342		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 upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]

	=== GNOME 46 ===		=== GNOME 46 ===

Jirutka: Update Upgrades

2024-05-20T21:42:09Z

Update Upgrades

← Older revision		Revision as of 21:42, 20 May 2024
Line 68:		Line 68:
	* Rust 1.7.8		* Rust 1.7.8
	* R 4.4		* R 4.4
			* Sway 1.9

Jirutka: Add Upgrades

2024-05-20T21:41:10Z

Add Upgrades

← Older revision		Revision as of 21:41, 20 May 2024
Line 54:		Line 54:

	Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.		Depending on how you installed GNOME, you may have to manually add <code>gcr-ssh-agent</code> after upgrading to retain GNOME Keyring ssh integration.

			== Upgrades ==

			* Crystal 1.12
			* LLVM 18
			* nginx 1.26
			* .NET 8
			* Nim 2.0
			* OpenJDK 22
			* Python 3.12
			* Racket 8.13
			* Ruby 3.3
			* Rust 1.7.8
			* R 4.4

Jirutka: Fix grammar

2024-05-20T21:20:33Z

Fix grammar

← Older revision		Revision as of 21:20, 20 May 2024
Line 3:		Line 3:
	=== grub 2.12 ===		=== 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.		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 <code>fwsetup --is-supported</code>, but grub 2.06 does not support the <code>--is-supported</code> argument yet, causing grub to ~~unconditionally~~ try to reboot into firmware.		The problem is that grub added a new configuration that executes <code>fwsetup --is-supported</code>, but grub 2.06 does not support the <code>--is-supported</code> argument yet, causing grub to try to reboot into firmware unconditionally.

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

	==== EFI ====		==== EFI ====
Line 22:		Line 22:
	; fwa : The respective [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-disk.in#L320-324 firmware architecture] for your system		; 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~~ ====		==== Short-term workaround ====

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

	{{Cmd\|cp /boot/grub/grub.cfg.backup /boot/grub.cfg }}		{{Cmd\|cp /boot/grub/grub.cfg.backup /boot/grub.cfg }}
Line 42:		Line 42:

	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.		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 ===
Line 48:		Line 47:

	=== aws-cli ===		=== 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		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 upstream: https://github.com/aws/aws-cli/issues/8342

	=== GNOME 46 ===		=== GNOME 46 ===