Alpine Linux - User contributions [en]

Release Notes for Alpine 3.23.0

2025-12-04T01:47:55Z

Omni: /* Important changes */ iwlwifi linux-firmware-other -> linux-firmware-intel

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== {{pkg|apk-tools}} v3 ===

After 5 years of development in the <code>master</code> branch of apk-tools, apk v3 is now ready for Alpine v3.23.0. This should be a safe and seamless upgrade from apk v2, but might has some breaking changes if you use <code>libapk</code>.

Note that we will only transition the package manager to v3, but will keep the v2 index and package format. We plan to move to the v3 index and package format after Alpine v3.23.

For more information, take a look at the release notes of apk v3: https://gitlab.alpinelinux.org/alpine/apk-tools/-/releases/v3.0.0

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

=== {{Pkg|linux-stable}} replaces {{Pkg|linux-edge}} ===

For years, {{Pkg|linux-lts}} and {{Pkg|linux-edge}} grew apart and developed their own kernel configs, different architectures, etc.

Now {{Pkg|linux-edge}} gets replaced with {{Pkg|linux-stable}} which has the identical configuration as {{Pkg|linux-lts}}, but follows the stable releases instead of the long-term releases (see https://kernel.org/).

If you had {{Pkg|linux-edge}} installed, apk automatically installs {{Pkg|linux-stable}} as a replacement. There is a reasonably amount of kernel config differences, if you need a config option that existed previously in {{Pkg|linux-edge}}, please open a issue to add the required option to {{Pkg|linux-lts}}. Also this change might involve manual boot loader configuration, as the kernel has been renamed and follows {{Pkg|linux-lts}}' packaging recipe.

=== <code>iwlwifi</code> firmware has moved from {{Pkg|linux-firmware-other}} to {{Pkg|linux-firmware-intel}} ===

This is important for Intel wireless users who have chosen a minimal set of firmware packages, with the {{Pkg|linux-firmware-none}} meta package plus {{Pkg|linux-firmware-other}}, you now need to <code>apk add linux-firmware-intel</code> to get <code>iwlwifi*.ucode.zstd</code> for your device.

== Significant changes ==

=== LLVM metapackage ===

Unversioned LLVM symlinks to their versioned components are now moved from their versioned LLVM package to a meta-package. This should have no impact on your usage.

=== nftrules subpackages ===

nftables rulesets are now packaged in <code>$pkgname-nftrules</code> subpackages, which contain rules for their individual packages in <code>/usr/share/nftables.avail/</code>. To enable rules, you can symlink the specific rule-files to `/etc/nftables.d/`. ({{Issue|16177}})

To install all available nftrules packages, you can install the metapackage {{Pkg|nftables-rulesets}}.

=== udev rules subpackages ===

Most udev rules were moved from main packages to their subpackages <code>$pkgname-udev</code>. It will be automatically installed if the system has <code>udev</code> installed, so it shouldn't require any manual intervention, but simplifies systems without udev.

=== systemd service subpackages ===

Although we don't have systemd packaged, many packages now have subpackages <code>$pkgname-systemd</code>, that contain systemd services. This will have no effect on systems, but simplifies systemd integration for [https://postmarketos.org/blog/2025/06/22/v25.06-release/#introduction postmarketOS]. There is no plan to move the default init system away from OpenRC to systemd.

=== curl HTTP/3 ===

{{Pkg|curl}} now got built with HTTP/3 support using nghttp3 and openssl-quic. ({{MR|89382}})

=== nginx --with-compat ===

{{pkg|nginx}} is now compiled with <code>--with-compat</code> (enables dynamic modules compatibility) to make it easier to build third-party nginx modules out-of-tree. There’s also a new subpackage {{pkg|nginx-mod-dev}} which provides the nginx sources and build dependencies needed for building nginx modules.

Please note that using nginx from aports with binary modules built against a different version of nginx or for a different platform (i.e. a different distro or Alpine branch) is '''not supported and will not work correctly'''! The same applies to using nginx modules from aports with a different nginx build.

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1.4
* busybox 1.37.0
* ffmpeg 8
* Garage 2.1.0
* GCC 15.2.0
* GNOME 49
* Go 1.25
* ISC BIND 9.20.16
* ISC Kea 3.0.2
* KDE Plasma 6.5.3
* Linux 6.18
* LLVM 21.1.2
* LXQt 2.30
* .NET 10
* NodeJS 24.11.1 (LTS)
* OpenJDK 25
* OpenSMTPD 7.8.0
* OpenZFS 2.4.0-rc4
* PHP 8.5.0
* Qt 6.10
* Ruby 3.4.7
* Rust 1.91.1
* Sway 1.11
* Valkey 9.0.0
* wlroots 0.19
* zigbee2mqtt 2.6.3

=== GCC 15 ===

We upgraded GCC from 14 to 15 and all packages have been built with GCC 15.

Make sure to read their release changes (https://gcc.gnu.org/gcc-15/changes.html) and porting guide (https://gcc.gnu.org/gcc-15/porting_to.html).

=== LLVM 21 ===

We upgraded our LLVM suite to 21.1.2. Older clang packages are still available for version 20. But we removed relevant LLVM/Clang packages that are no longer needed by our distribution packages. If you still need older versions, please port your software to newer LLVM versions or use third-party builds.

=== GNOME 49 ===

https://release.gnome.org/49/

* We kept gnome-session (and gdm, and similar) at 48 because of the [https://release.gnome.org/49/developers/index.html#stronger-systemd-dependencies stricter systemd dependency] ({{Issue|17514}})
* Our gdk-pixbuf didn't enable the glycin sandboxing library yet ({{Issue|17550}})

=== ffmpeg 8 ===

The {{Pkg|ffmpeg}} package got upgraded from version 6 to 8.

Most consumers of ffmpeg are now built against ffmpeg 8, but some packages might still use ffmpeg 6 or 7, depending on its API compatability. Therefore the {{Pkg|ffmpeg6}} and {{Pkg|ffmpeg7}} packages are also still available.

Also note that {{Pkg|ffmpeg4}} got removed and all consumers were migrated to at least ffmpeg 6.

=== ifstate 2 ===

The declarative network configuration tool {{Pkg|ifstate}} has been upgraded from version 1.x to version 2. It is not possible to use the old configuration file of ifstate 1.x with ifstate 2.x! The configuration file '''must''' be adapted to the new schema and file name to prevent breaking the host's network the next time it is booted! More information about the required config changes can be found in the [https://ifstate.net/2.2/docs/upgrades/#ifstate-20 ifstate documentation].

== Significant removals ==

=== More Qt5 removals ===

Just as [[Release_Notes_for_Alpine_3.22.0#Qt_5|last release]], we removed more Qt5 libraries that were no longer used by our distribution packages. ({{Issue|17114}})

=== ffmpeg4 ===

We removed <code>ffmpeg4</code> from our repository and are only providing versions 6, 7 and 8.

=== rssh ===

rssh package has been removed due to the dead upstream.

=== ircservices ===

unmaintained upstream for years

=== postgresql-age ===

Apache AGE [https://github.com/apache/age/issues/2229 lacks behind] in supporting the latest version of PostgreSQL. The project seems to [https://github.com/apache/age/issues/2111#issuecomment-2441903180 lack sufficient manpower]. :(

If you want a graph database on top of PostgreSQL, you can use {{pkg|agensgraph}}. However, unlike AGE, it’s not an extension, but a fork of PostgreSQL.

<hr><center>[[Release Notes for Alpine 3.22.0|← Previous page: Release Notes for Alpine 3.22.0]] — [[Draft Release Notes for Alpine 3.24.0|Next page: Release Notes for Alpine 3.24.0 →]]</center>

Release Notes for Alpine 3.23.0

2025-12-03T13:08:36Z

Omni: /* systemd service subpackages */ what about s6?

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== {{pkg|apk-tools}} v3 ===

After 5 years of development in the <code>master</code> branch of apk-tools, apk v3 is now ready for Alpine v3.23.0. This should be a safe and seamless upgrade from apk v2, but might has some breaking changes if you use <code>libapk</code>.

Note that we will only transition the package manager to v3, but will keep the v2 index and package format. We plan to move to the v3 index and package format after Alpine v3.23.

For more information, take a look at the release notes of apk v3: https://gitlab.alpinelinux.org/alpine/apk-tools/-/releases/v3.0.0

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

=== {{Pkg|linux-stable}} replaces {{Pkg|linux-edge}} ===

For years, {{Pkg|linux-lts}} and {{Pkg|linux-edge}} grew apart and developed their own kernel configs, different architectures, etc.

Now {{Pkg|linux-edge}} gets replaced with {{Pkg|linux-stable}} which has the identical configuration as {{Pkg|linux-lts}}, but follows the stable releases instead of the long-term releases (see https://kernel.org/).

If you had {{Pkg|linux-edge}} installed, apk automatically installs {{Pkg|linux-stable}} as a replacement. There is a reasonably amount of kernel config differences, if you need a config option that existed previously in {{Pkg|linux-edge}}, please open a issue to add the required option to {{Pkg|linux-lts}}. Also this change might involve manual boot loader configuration, as the kernel has been renamed and follows {{Pkg|linux-lts}}' packaging recipe.

== Significant changes ==

=== LLVM metapackage ===

Unversioned LLVM symlinks to their versioned components are now moved from their versioned LLVM package to a meta-package. This should have no impact on your usage.

=== nftrules subpackages ===

nftables rulesets are now packaged in <code>$pkgname-nftrules</code> subpackages, which contain rules for their individual packages in <code>/usr/share/nftables.avail/</code>. To enable rules, you can symlink the specific rule-files to `/etc/nftables.d/`. ({{Issue|16177}})

To install all available nftrules packages, you can install the metapackage {{Pkg|nftables-rulesets}}.

=== udev rules subpackages ===

Most udev rules were moved from main packages to their subpackages <code>$pkgname-udev</code>. It will be automatically installed if the system has <code>udev</code> installed, so it shouldn't require any manual intervention, but simplifies systems without udev.

=== systemd service subpackages ===

Although we don't have systemd packaged, many packages now have subpackages <code>$pkgname-systemd</code>, that contain systemd services. This will have no effect on systems, but simplifies any future integrations with systemd in Alpine and for [https://postmarketos.org/blog/2025/06/22/v25.06-release/#introduction postmarketOS]. There is no plan to move the default init system away from OpenRC to systemd.

=== curl HTTP/3 ===

{{Pkg|curl}} now got built with HTTP/3 support using nghttp3 and openssl-quic. ({{MR|89382}})

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1.4
* busybox 1.37.0
* Deno 2.3.1
* ffmpeg 8
* GCC 15.2.0
* GNOME 49
* Go 1.25
* ISC BIND 9.20.16
* ISC Kea 3.0.2
* KDE Plasma 6.5.3
* Linux 6.18
* LLVM 21.1.2
* LXQt 2.30
* .NET 10
* nginx 1.28
* NodeJS 24.11.1 (LTS)
* OpenJDK 25
* OpenZFS 2.4.0-rc4
* PHP 8.5.0
* Qt 6.10
* Ruby 3.4.7
* Rust 1.91.1
* wlroots 0.19
* zigbee2mqtt 2.6.3

=== GCC 15 ===

We upgraded GCC from 14 to 15 and all packages have been built with GCC 15.

Make sure to read their release changes (https://gcc.gnu.org/gcc-15/changes.html) and porting guide (https://gcc.gnu.org/gcc-15/porting_to.html).

=== LLVM 21 ===

We upgraded our LLVM suite to 21.1.2. Older clang packages are still available for version 20. But we removed relevant LLVM/Clang packages that are no longer needed by our distribution packages. If you still need older versions, please port your software to newer LLVM versions or use third-party builds.

=== GNOME 49 ===

https://release.gnome.org/49/

* We kept gnome-session (and gdm, and similar) at 48 because of the [https://release.gnome.org/49/developers/index.html#stronger-systemd-dependencies stricter systemd dependency] ({{Issue|17514}})
* Our gdk-pixbuf didn't enable the glycin sandboxing library yet ({{Issue|17550}})

=== ffmpeg 8 ===

The {{Pkg|ffmpeg}} package got upgraded from version 6 to 8.

Most consumers of ffmpeg are now built against ffmpeg 8, but some packages might still use ffmpeg 6 or 7, depending on its API compatability. Therefore the {{Pkg|ffmpeg6}} and {{Pkg|ffmpeg7}} packages are also still available.

Also note that {{Pkg|ffmpeg4}} got removed and all consumers were migrated to at least ffmpeg 6.

=== ifstate 2 ===

The declarative network configuration tool {{Pkg|ifstate}} has been upgraded from version 1.x to version 2. It is not possible to use the old configuration file of ifstate 1.x with ifstate 2.x! The configuration file '''must''' be adapted to the new schema and file name to prevent breaking the host's network the next time it is booted! More information about the required config changes can be found in the [https://ifstate.net/2.2/docs/upgrades/#ifstate-20 ifstate documentation].

== Significant removals ==

=== More Qt5 removals ===

Just as [[Release_Notes_for_Alpine_3.22.0#Qt_5|last release]], we removed more Qt5 libraries that were no longer used by our distribution packages. ({{Issue|17114}})

=== ffmpeg4 ===

We removed <code>ffmpeg4</code> from our repository and are only providing versions 6, 7 and 8.

=== rssh ===

rssh package has been removed due to the dead upstream.

=== ircservices ===

unmaintained upstream for years

<hr><center>[[Release Notes for Alpine 3.22.0|← Previous page: Release Notes for Alpine 3.22.0]] — [[Draft Release Notes for Alpine 3.24.0|Next page: Release Notes for Alpine 3.24.0 →]]</center>

Release Notes for Alpine 3.23.0

2025-12-03T13:06:43Z

Omni: /* Note-worthy updates */ move alphabetically since I called it "OpenZFS", I'll let someone else decide if this is what it should be called or just "ZFS"

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== {{pkg|apk-tools}} v3 ===

After 5 years of development in the <code>master</code> branch of apk-tools, apk v3 is now ready for Alpine v3.23.0. This should be a safe and seamless upgrade from apk v2, but might has some breaking changes if you use <code>libapk</code>.

Note that we will only transition the package manager to v3, but will keep the v2 index and package format. We plan to move to the v3 index and package format after Alpine v3.23.

For more information, take a look at the release notes of apk v3: https://gitlab.alpinelinux.org/alpine/apk-tools/-/releases/v3.0.0

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

=== {{Pkg|linux-stable}} replaces {{Pkg|linux-edge}} ===

For years, {{Pkg|linux-lts}} and {{Pkg|linux-edge}} grew apart and developed their own kernel configs, different architectures, etc.

Now {{Pkg|linux-edge}} gets replaced with {{Pkg|linux-stable}} which has the identical configuration as {{Pkg|linux-lts}}, but follows the stable releases instead of the long-term releases (see https://kernel.org/).

If you had {{Pkg|linux-edge}} installed, apk automatically installs {{Pkg|linux-stable}} as a replacement. There is a reasonably amount of kernel config differences, if you need a config option that existed previously in {{Pkg|linux-edge}}, please open a issue to add the required option to {{Pkg|linux-lts}}. Also this change might involve manual boot loader configuration, as the kernel has been renamed and follows {{Pkg|linux-lts}}' packaging recipe.

== Significant changes ==

=== LLVM metapackage ===

Unversioned LLVM symlinks to their versioned components are now moved from their versioned LLVM package to a meta-package. This should have no impact on your usage.

=== nftrules subpackages ===

nftables rulesets are now packaged in <code>$pkgname-nftrules</code> subpackages, which contain rules for their individual packages in <code>/usr/share/nftables.avail/</code>. To enable rules, you can symlink the specific rule-files to `/etc/nftables.d/`. ({{Issue|16177}})

To install all available nftrules packages, you can install the metapackage {{Pkg|nftables-rulesets}}.

=== udev rules subpackages ===

Most udev rules were moved from main packages to their subpackages <code>$pkgname-udev</code>. It will be automatically installed if the system has <code>udev</code> installed, so it shouldn't require any manual intervention, but simplifies systems without udev.

=== systemd service subpackages ===

Although we don't have systemd packaged, many packages now have subpackages <code>$pkgname-systemd</code>, that contain systemd services. This will have no effect on systems, but simplifies any future integrations with systemd in Alpine and for [https://postmarketos.org/blog/2025/06/22/v25.06-release/#introduction postmarketOS]. There is no plan to move the default init system away from OpenRC.

=== curl HTTP/3 ===

{{Pkg|curl}} now got built with HTTP/3 support using nghttp3 and openssl-quic. ({{MR|89382}})

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1.4
* busybox 1.37.0
* Deno 2.3.1
* ffmpeg 8
* GCC 15.2.0
* GNOME 49
* Go 1.25
* ISC BIND 9.20.16
* ISC Kea 3.0.2
* KDE Plasma 6.5.3
* Linux 6.18
* LLVM 21.1.2
* LXQt 2.30
* .NET 10
* nginx 1.28
* NodeJS 24.11.1 (LTS)
* OpenJDK 25
* OpenZFS 2.4.0-rc4
* PHP 8.5.0
* Qt 6.10
* Ruby 3.4.7
* Rust 1.91.1
* wlroots 0.19
* zigbee2mqtt 2.6.3

=== GCC 15 ===

We upgraded GCC from 14 to 15 and all packages have been built with GCC 15.

Make sure to read their release changes (https://gcc.gnu.org/gcc-15/changes.html) and porting guide (https://gcc.gnu.org/gcc-15/porting_to.html).

=== LLVM 21 ===

We upgraded our LLVM suite to 21.1.2. Older clang packages are still available for version 20. But we removed relevant LLVM/Clang packages that are no longer needed by our distribution packages. If you still need older versions, please port your software to newer LLVM versions or use third-party builds.

=== GNOME 49 ===

https://release.gnome.org/49/

* We kept gnome-session (and gdm, and similar) at 48 because of the [https://release.gnome.org/49/developers/index.html#stronger-systemd-dependencies stricter systemd dependency] ({{Issue|17514}})
* Our gdk-pixbuf didn't enable the glycin sandboxing library yet ({{Issue|17550}})

=== ffmpeg 8 ===

The {{Pkg|ffmpeg}} package got upgraded from version 6 to 8.

Most consumers of ffmpeg are now built against ffmpeg 8, but some packages might still use ffmpeg 6 or 7, depending on its API compatability. Therefore the {{Pkg|ffmpeg6}} and {{Pkg|ffmpeg7}} packages are also still available.

Also note that {{Pkg|ffmpeg4}} got removed and all consumers were migrated to at least ffmpeg 6.

=== ifstate 2 ===

The declarative network configuration tool {{Pkg|ifstate}} has been upgraded from version 1.x to version 2. It is not possible to use the old configuration file of ifstate 1.x with ifstate 2.x! The configuration file '''must''' be adapted to the new schema and file name to prevent breaking the host's network the next time it is booted! More information about the required config changes can be found in the [https://ifstate.net/2.2/docs/upgrades/#ifstate-20 ifstate documentation].

== Significant removals ==

=== More Qt5 removals ===

Just as [[Release_Notes_for_Alpine_3.22.0#Qt_5|last release]], we removed more Qt5 libraries that were no longer used by our distribution packages. ({{Issue|17114}})

=== ffmpeg4 ===

We removed <code>ffmpeg4</code> from our repository and are only providing versions 6, 7 and 8.

=== rssh ===

rssh package has been removed due to the dead upstream.

=== ircservices ===

unmaintained upstream for years

<hr><center>[[Release Notes for Alpine 3.22.0|← Previous page: Release Notes for Alpine 3.22.0]] — [[Draft Release Notes for Alpine 3.24.0|Next page: Release Notes for Alpine 3.24.0 →]]</center>

Release Notes for Alpine 3.23.0

2025-12-03T13:04:30Z

Omni: /* Note-worthy updates */ zfs

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== {{pkg|apk-tools}} v3 ===

After 5 years of development in the <code>master</code> branch of apk-tools, apk v3 is now ready for Alpine v3.23.0. This should be a safe and seamless upgrade from apk v2, but might has some breaking changes if you use <code>libapk</code>.

Note that we will only transition the package manager to v3, but will keep the v2 index and package format. We plan to move to the v3 index and package format after Alpine v3.23.

For more information, take a look at the release notes of apk v3: https://gitlab.alpinelinux.org/alpine/apk-tools/-/releases/v3.0.0

=== /usr merge ===

New installations can opt-in to being /usr-merged, by setting the <code>BOOTSTRAP_USR_MERGED</code> environment variable to <code>1</code> before running <code>setup-disk</code>. Manual migration is also possible by installing the <code>merge-usr</code> package and running its binary as root. For more details see the [https://alpinelinux.org/posts/2025-10-01-usr-merge.html official announcement].

=== {{Pkg|linux-stable}} replaces {{Pkg|linux-edge}} ===

For years, {{Pkg|linux-lts}} and {{Pkg|linux-edge}} grew apart and developed their own kernel configs, different architectures, etc.

Now {{Pkg|linux-edge}} gets replaced with {{Pkg|linux-stable}} which has the identical configuration as {{Pkg|linux-lts}}, but follows the stable releases instead of the long-term releases (see https://kernel.org/).

If you had {{Pkg|linux-edge}} installed, apk automatically installs {{Pkg|linux-stable}} as a replacement. There is a reasonably amount of kernel config differences, if you need a config option that existed previously in {{Pkg|linux-edge}}, please open a issue to add the required option to {{Pkg|linux-lts}}. Also this change might involve manual boot loader configuration, as the kernel has been renamed and follows {{Pkg|linux-lts}}' packaging recipe.

== Significant changes ==

=== LLVM metapackage ===

Unversioned LLVM symlinks to their versioned components are now moved from their versioned LLVM package to a meta-package. This should have no impact on your usage.

=== nftrules subpackages ===

nftables rulesets are now packaged in <code>$pkgname-nftrules</code> subpackages, which contain rules for their individual packages in <code>/usr/share/nftables.avail/</code>. To enable rules, you can symlink the specific rule-files to `/etc/nftables.d/`. ({{Issue|16177}})

To install all available nftrules packages, you can install the metapackage {{Pkg|nftables-rulesets}}.

=== udev rules subpackages ===

Most udev rules were moved from main packages to their subpackages <code>$pkgname-udev</code>. It will be automatically installed if the system has <code>udev</code> installed, so it shouldn't require any manual intervention, but simplifies systems without udev.

=== systemd service subpackages ===

Although we don't have systemd packaged, many packages now have subpackages <code>$pkgname-systemd</code>, that contain systemd services. This will have no effect on systems, but simplifies any future integrations with systemd in Alpine and for [https://postmarketos.org/blog/2025/06/22/v25.06-release/#introduction postmarketOS]. There is no plan to move the default init system away from OpenRC.

=== curl HTTP/3 ===

{{Pkg|curl}} now got built with HTTP/3 support using nghttp3 and openssl-quic. ({{MR|89382}})

== Note-worthy updates ==

As always, many packages were upgraded. Make sure to read the individual release notes of the projects you use.

* BIRD 3.1.4
* busybox 1.37.0
* Deno 2.3.1
* ffmpeg 8
* GCC 15.2.0
* GNOME 49
* Go 1.25
* ISC BIND 9.20.16
* ISC Kea 3.0.2
* KDE Plasma 6.5.3
* Linux 6.18
* LLVM 21.1.2
* LXQt 2.30
* .NET 10
* nginx 1.28
* NodeJS 24.11.1 (LTS)
* OpenJDK 25
* PHP 8.5.0
* Qt 6.10
* Ruby 3.4.7
* Rust 1.91.1
* wlroots 0.19
* OpenZFS 2.4.0-rc4
* zigbee2mqtt 2.6.3

=== GCC 15 ===

We upgraded GCC from 14 to 15 and all packages have been built with GCC 15.

Make sure to read their release changes (https://gcc.gnu.org/gcc-15/changes.html) and porting guide (https://gcc.gnu.org/gcc-15/porting_to.html).

=== LLVM 21 ===

We upgraded our LLVM suite to 21.1.2. Older clang packages are still available for version 20. But we removed relevant LLVM/Clang packages that are no longer needed by our distribution packages. If you still need older versions, please port your software to newer LLVM versions or use third-party builds.

=== GNOME 49 ===

https://release.gnome.org/49/

* We kept gnome-session (and gdm, and similar) at 48 because of the [https://release.gnome.org/49/developers/index.html#stronger-systemd-dependencies stricter systemd dependency] ({{Issue|17514}})
* Our gdk-pixbuf didn't enable the glycin sandboxing library yet ({{Issue|17550}})

=== ffmpeg 8 ===

The {{Pkg|ffmpeg}} package got upgraded from version 6 to 8.

Most consumers of ffmpeg are now built against ffmpeg 8, but some packages might still use ffmpeg 6 or 7, depending on its API compatability. Therefore the {{Pkg|ffmpeg6}} and {{Pkg|ffmpeg7}} packages are also still available.

Also note that {{Pkg|ffmpeg4}} got removed and all consumers were migrated to at least ffmpeg 6.

=== ifstate 2 ===

The declarative network configuration tool {{Pkg|ifstate}} has been upgraded from version 1.x to version 2. It is not possible to use the old configuration file of ifstate 1.x with ifstate 2.x! The configuration file '''must''' be adapted to the new schema and file name to prevent breaking the host's network the next time it is booted! More information about the required config changes can be found in the [https://ifstate.net/2.2/docs/upgrades/#ifstate-20 ifstate documentation].

== Significant removals ==

=== More Qt5 removals ===

Just as [[Release_Notes_for_Alpine_3.22.0#Qt_5|last release]], we removed more Qt5 libraries that were no longer used by our distribution packages. ({{Issue|17114}})

=== ffmpeg4 ===

We removed <code>ffmpeg4</code> from our repository and are only providing versions 6, 7 and 8.

=== rssh ===

rssh package has been removed due to the dead upstream.

=== ircservices ===

unmaintained upstream for years

<hr><center>[[Release Notes for Alpine 3.22.0|← Previous page: Release Notes for Alpine 3.22.0]] — [[Draft Release Notes for Alpine 3.24.0|Next page: Release Notes for Alpine 3.24.0 →]]</center>

Release Notes for Alpine 3.21.0

2024-12-07T18:00:07Z

Omni: /* ISC DHCP */ dracut-modules-network

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification. Please note that <code>/</code> on separate filesystem than <code>/usr</code> is not officially supported.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 0.18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

=== GNOME 47 ===

{{pkg|gnome-software}} has been held back to version 45, after several regressions in the apk plugin on update. See {{issue|16637}} for more details.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

==== dracut-modules-network network-legacy removal ====

As a consequence of the above, the <code>network-legacy</code> module has been removed from {{pkg|dracut-modules-network}}, as it had a depedency on the {{pkg|dhclient}} sub-package of the ISC DHCP aport.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

=== .NET 6 ===

.NET 6 reached EOL in 12 November 2024 (see https://devblogs.microsoft.com/dotnet/dotnet-6-end-of-support/) and the following packages have been moved to the testing repository ({{MR|73655}}):
* {{pkg|dotnet6-build|branch=edge|arch=}}
* {{pkg|dotnet6-runtime|branch=edge|arch=}}
* {{pkg|dotnet6-stage0|branch=edge|arch=}}
* {{pkg|lidarr|branch=edge|arch=}}
* {{pkg|prowlarr|branch=edge|arch=}}
* {{pkg|radarr|branch=edge|arch=}}
* {{pkg|sonarr|branch=edge|arch=}}

[[Category:News]]

Release Notes for Alpine 3.21.0

2024-12-05T12:19:55Z

Omni: /* Note-worthy updates */ wlroots 0.18, not 18

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service fails for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

Plans for /usr-merge are underway and we should be able to finalize it in Alpine Linux, version 3.22.

Much preparation has gone into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counterparts in <code>/usr</code>. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place.

'''Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care and report any issues.''' They should also ensure that an entry <code>/usr</code> is added to <code>/etc/fstab</code> before upgrading, and all modules required to mount <code>/usr</code> from the initramfs are added to mkinitfs configuration. New/fresh installations of v3.21 will work out of the box without modification. Please note that <code>/</code> on separate filesystem than <code>/usr</code> is not officially supported.

If you have one of these setups, and have doubts about the configuration, you can open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>. We will also publish a blog post soon with further information on the timeline and progress of the merge, as well as how the changes may affect users.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change the default, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. There is now a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You can choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no longer exist.

If you prefer to use GNU {{pkg|coreutils}}, remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 0.18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and as a result, all packages built with {{pkg|gcc}} in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now Wayland ready¹, but Wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, as well as settings for monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on Wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

=== GNOME 47 ===

{{pkg|gnome-software}} has been held back to version 45, after several regressions in the apk plugin on update. See {{issue|16663}} for more details.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp|branch=v3.20}} aport has the subpackage {{pkg|keama|branch=v3.20}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities for which issues have remained open for a year. The developers of Gogs were contacted multiple times by the Forgejo team but unfortunately received no response. Therefore we have removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo.

The Gitea fork of Gogs was created in 2016 by contributors who were frustrated with the single-maintainer management model of Gogs. Forgejo is a fork of Gitea which was created as a result of the for-profit company Gitea Ltd taking over maintainership (see also https://forgejo.org/compare-to-gitea/).

=== neofetch ===

The upstream repository was archived in April and became unmaintained, therefore we have removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-04T20:31:22Z

Omni: /* ISC DHCP */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care. As part of the merge, <code>/usr</code> will be mounted from the initramfs to make sure everybody has all necessary binaries in place. However, there are currently some bugs being [https://gitlab.alpinelinux.org/alpine/mkinitfs/-/merge_requests/186 worked on]. Until those are worked out and backported, it is advisable to hold the upgrade back. Once it is ready, we will provide more detailed information. If you have one of those setups, and want to help testing, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code>.

We'll publish soon a blog post with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. Now there is a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and, as a result, all packages built with {{pkg|gcc}} are in Alpine 3.21 compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

If you are still running an ISC DHCP server, you are advised to migrate to a maintained alternative '''before''' upgrading to the 3.21 release.

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

Up to, and including, the 3.20 version of Alpine, the {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

Alternative DHCP servers packaged in Alpine include:
* {{pkg|kea}}
* {{pkg|freeradius-dhcp}}
* {{pkg|dnsmasq}}
* udhcpd - packaged in {{pkg|busybox-extras}}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-04T12:55:26Z

Omni: /* Note-worthy updates */ busybox being a core part, move it to under Linux

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

We'll publish soon a blog post about with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. Now there is a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* busybox 1.37
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and, as a result, all packages built with {{pkg|gcc}} are in Alpine 3.21 compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-04T12:54:09Z

Omni: /* Note-worthy updates */ move PHP together with the other languages and skip the patch release number, as with the others

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

We'll publish soon a blog post about with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. ({{Issue|16613}})

=== Bats ===

<code>main/bats</code> was renamed to <code>main/bats-core</code>. Now there is a meta package <code>community/bats</code> which contains:

* {{pkg|bats-core}}
* {{pkg|bats-file}}
* {{pkg|bats-support}}
* {{pkg|bats-assert}}

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* PHP 8.4
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18
* busybox 1.37

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and, as a result, all packages built with {{pkg|gcc}} are in Alpine 3.21 compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. A total of 5 LLVM versions are supported: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We will try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-03T18:47:29Z

Omni: /* Preparations for /usr-merge */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate filesystems (partitions, volumes, disk drives or other) should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

We'll publish soon a blog post about with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18
* busybox 1.37

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and, as a result, all packages built with {{pkg|gcc}} are in Alpine 3.21 compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-03T17:31:05Z

Omni: /* GCC 14 */ other packages are not, at least directly, built with gcc

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

We'll publish soon a blog post about with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18
* busybox 1.37

=== GCC 14 ===

The Gnu Compiler Collection was upgraded to 14.2.0 and, as a result, all packages built with {{pkg|gcc}} are in Alpine 3.21 compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-12-03T17:26:23Z

Omni: /* OpenSSH requires restart */ accepted and merged

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH service requires restart ===

From the <code>9.8_p1</code> release, and on, of {{pkg|openssh}}, {{pkg|openssh-server}} is split into two binaries (<code>/usr/lib/ssh/sshd-session</code> and <code>/usr/sbin/sshd</code>). Due to this change, it will not be possible to <code>ssh</code> into a system that has upgraded from a release prior to <code>9.8_p1</code> to this release or later, without restarting the <code>sshd</code> service.

We have previously brought attention to this - https://alpinelinux.org/posts/2024-07-02-openssh-upgrade-edge.html

Managing services has always been out-of-scope for {{pkg|apk-tools}}, but this one time we will '''make an exception''' when the following conditions are met:
# You have both the {{pkg|openssh-server}} and {{pkg|openssh-server-common-openrc}} packages installed at a version lower than <code>9.8_p1</code>
# The <code>sshd</code> service is started

We will then, post {{pkg|openssh-server}} upgrade, have a <code>post-upgrade</code> script that will:
# Print a message on what is about to happen and why
# Restart the <code>sshd</code> service
# If the command to restart the service would fail, for any reason, a warning message will be printed and an error code returned to <code>apk</code>, to be noticed by the end of the package upgrades (this will not interrupt the upgrade process).

We have decided to do this in order to help keep you from getting locked out of your system(s) and be able to fix any issues with the upgrade.

See also:
* https://bugzilla.mindrot.org/show_bug.cgi?id=3706
* https://git.alpinelinux.org/aports/commit/?id=6adff08ae09961d4eea66b55a8cca14d3941fb53

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

We'll publish soon a blog post about with further information, the timeline and the effects.

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18
* busybox 1.37

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|hplip}} ({{Issue|16685}})
* {{pkg|imageflow}} ({{Issue|16679}})
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{Issue|16580}})
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}} ({{Issue|16686}})

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T04:45:28Z

Omni: /* Note-worthy updates */ busybox

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18
* busybox 1.37

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T03:27:49Z

Omni: /* Note-worthy updates */ wlroots 18

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8
* wlroots 18

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:40:00Z

Omni: /* Preparations for /usr-merge */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and it may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:39:09Z

Omni: /* Preparations for /usr-merge */ there are many possible configurations where a user may have chosen to separate / and /usr

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are on separate partitions, volumes or disk devices should proceed with care, and may be advisable to skip the 3.21 upgrade.

If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:32:08Z

Omni: /* uutils-coreutils */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the <code>/usr/bin/uutils</code> binary. The <code>/usr/bin/uutils-*</code> symlinks, previously provided by {{pkg|uutils-coreutils}}, no loger exist.

If you prefer to use GNU {{pkg|coreutils}}, you want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package, containing the <code>/usr/bin/uutils</code> binary.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:23:40Z

Omni: /* uutils-coreutils */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package.

If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:22:57Z

Omni: /* uutils-coreutils */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be '''purged''' and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading, and then add the {{pkg|uutils}} package.

A few parts of the {{pkg|uutils}} aport are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-30T02:18:52Z

Omni: /* ISC DHCP */ not in the same mood

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something ''cool'' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

ISC DHCP has been EoL since 2022. They have a guide for migrating to {{pkg|kea}} here: https://www.isc.org/dhcp_migration/

The {{pkg|dhcp}} aport has the subpackage {{pkg|keama}} that is a tool for helping with migration from ISC DHCP configuration to ISC Kea configuration.

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T01:59:50Z

Omni: /* Xen */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen 4.19 ===

''qemu-traditional'' and ''stubdom'' are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

There is still the {{pkg|xen-qemu}} package, but the regular {{pkg|qemu}} aport [https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13 is now built with Xen support], so a {{pkg|qemu-system-*}} package can be used instead.

You would choose to use it in your ''xl.cfg(1)'' like so:
<pre>
device_model_override = "/usr/bin/qemu-system-x86_64"
device_model_version = "qemu-xen"
</pre>

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to {{pkg|kea}}, why don't you? https://www.isc.org/dhcp_migration/

something something {{pkg|keama}} https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T00:14:32Z

Omni: /* Linux 6.12 */ patch

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.1 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to {{pkg|kea}}, why don't you? https://www.isc.org/dhcp_migration/

something something {{pkg|keama}} https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T00:13:37Z

Omni: /* Note-worthy updates */ drop patch numbers

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2
* LLVM 19
* Go 1.23
* Rust 1.83
* GNOME 47
* KDE Plasma 6.2
* LXQt 2.1
* Qt 6.8

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.0 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to {{pkg|kea}}, why don't you? https://www.isc.org/dhcp_migration/

something something {{pkg|keama}} https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T00:11:01Z

Omni: /* Note-worthy updates */ rust

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.83
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0
* Qt 6.8.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.0 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to {{pkg|kea}}, why don't you? https://www.isc.org/dhcp_migration/

something something {{pkg|keama}} https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T00:09:06Z

Omni: /* ISC DHCP */ still cool?

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0
* Qt 6.8.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.0 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to {{pkg|kea}}, why don't you? https://www.isc.org/dhcp_migration/

something something {{pkg|keama}} https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-29T00:05:26Z

Omni: /* uutils-coreutils */

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

{{pkg|uutils-coreutils}} is repackaged as a sub-package to {{pkg|uutils}} in such a way as to be a drop-in replacement for GNU {{pkg|coreutils}}.

If you have both {{pkg|uutils-coreutils}} and {{pkg|coreutils}} installed, the latter will be purged and its symlinks replaced with ones pointing to the ''/usr/bin/uutils'' binary, provided by the {{pkg|uutils}} package. If you prefer to use GNU {{pkg|coreutils}}, you may want to remove the {{pkg|uutils-coreutils}} package before upgrading and add {{pkg|uutils}} after.

A few parts of the {{pkg|uutils}} are also split into {{pkg|uutils-*}} subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0
* Qt 6.8.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.0 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to Kea, why don't you? https://www.isc.org/dhcp_migration/

something something keama https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-28T23:28:47Z

Omni: /* ISC DHCP */ cool, huh?

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preparations went into this release to ensure that the merge happens as smoothly as possible. That included moving the location of some binaries and many libraries from <code>/bin</code>, <code>/sbin</code>, and <code>/lib</code> to their counter-parts in <code>/usr</code>. Users with installations where <code>/</code> and <code>/usr</code> are in different partitions should proceed with care, and may be advisable to skip the 3.21 upgrade. If you still want to go ahead, you may open an [https://gitlab.alpinelinux.org/alpine/aports/-/issues/new issue] and ping <code>@pabloyoyoista</code> to ask for support.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ({{MR|69924}})

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: {{Issue|16613}}

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

"uutils-coreutils" is repackaged as a sub-package to "community/uutils" in such a way as to be a drop-in replacement for GNU coreutils.

If you have both "uutils-coreutils" and "coreutils" installed, the latter will be purged and its symlinks replaced with ones pointing to the /usr/bin/uutils binary, provided by the "uutils" package. If you prefer to use GNU "coreutils", or run into issues with "uutils" as replacement, you may want to remove the "uutils-coreutils" package before upgrading.

A few parts of the uutils are also split into subpackages, to avoid conflicts or other issues.

=== linux-firmware ===

{{pkg|linux-firmware}} is now compressed with ZSTD compression. If you run a custom built Linux kernel, you need to ensure that <code>CONFIG_FW_LOADER_COMPRESS_ZSTD=y</code> is set in your configuration.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux 6.12
* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0
* Qt 6.8.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== Linux 6.12 ===

Alpine 3.21.0 ships Linux 6.12.0 in the {{pkg|linux-lts}} package.

Please note that {{pkg|linux-headers}} still is on 6.6, because the kernel was released after we kicked off our rebuilds and we coudn't ensure that the upgrade doesn't break other packages. (More about the linux-headers 6.12 upgrade: {{MR|75618}})

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== Disabled packages due to FTBS ===

{{note|update to latest state (last update 2024-11-28)}}

The following packages are temporarily disabled because they failed to build. We try to restore them as soon as possible.

* {{pkg|guacamole-dotool}} ({{MR|75998}})
* {{pkg|hplip}}
* {{pkg|kdevelop}} ({{MR|75839}})
* {{pkg|postgresql-citus}} ({{MR|75381}}
* {{pkg|uvicorn}} ({{Issue|16646}})
* {{pkg|vulkan-validation-layers}}

=== ISC DHCP ===

{{Note|TODO: Write something '''cool''' if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

Like, you know, you should prolly migrate to some other thing disregardless, yeah? I mean, it has been EoL since friggin' '''2022''', jeez!

Have an ISC guide for migrating to Kea, why don't you? https://www.isc.org/dhcp_migration/

something something keama https://pkgs.alpinelinux.org/package/edge/main/x86_64/keama

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ({{MR|75304}})

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-17T23:58:11Z

Omni: /* Note-worthy updates */ Qt

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preperations went into this release to ensure that the merge happens as smoothly as possible.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69924 !69924])

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16613

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

"uutils-coreutils" is repackaged as a sub-package to "community/uutils" in such a way as to be a drop-in replacement for GNU coreutils.

If you have both "uutils-coreutils" and "coreutils" installed, the latter will be purged and its symlinks replaced with ones pointing to the /usr/bin/uutils binary, provided by the "uutils" package. If you prefer to use GNU "coreutils", or run into issues with "uutils" as replacement, you may want to remove the "uutils-coreutils" package before upgrading.

A few parts of the uutils are also split into subpackages, to avoid conflicts or other issues.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0
* Qt 6.8.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== ISC DHCP ===

{{Note|TODO: Write something cool if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/75304 !75304])

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-17T23:55:40Z

Omni: /* Significant changes */ uutils

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preperations went into this release to ensure that the merge happens as smoothly as possible.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69924 !69924])

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16613

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

=== uutils-coreutils ===

"uutils-coreutils" is repackaged as a sub-package to "community/uutils" in such a way as to be a drop-in replacement for GNU coreutils.

If you have both "uutils-coreutils" and "coreutils" installed, the latter will be purged and its symlinks replaced with ones pointing to the /usr/bin/uutils binary, provided by the "uutils" package. If you prefer to use GNU "coreutils", or run into issues with "uutils" as replacement, you may want to remove the "uutils-coreutils" package before upgrading.

A few parts of the uutils are also split into subpackages, to avoid conflicts or other issues.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== ISC DHCP ===

{{Note|TODO: Write something cool if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/75304 !75304])

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.21.0

2024-11-17T23:36:20Z

Omni: /* Significant changes */ xen

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

=== OpenSSH requires restart ===

{{Note|TODO: Remove this section if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/68589 gets merged before 3.21 is released }}

You need to restart your sshd service!

Since the <code>9.8_p1</code> release, openssh-server is now split into two binaries, sshd and sshd-session. With this change sshd needs to be restarted to be able to accept new connections.

Since managing services has always been out-of-scope for apk, we will NOT do the following for you:

<code>
rc-service --ifstarted sshd restart
</code>

=== New loongarch64 architecture ===

Alpine 3.21 is the first release which is available for <code>loongarch64</code>.

Thanks to the support of the team of Loongson dedicated to supporting Alpine Linux and many other contributors.

=== Preparations for /usr-merge ===

We plan for the next Alpine Linux, version 3.22, to contain the /usr-merge.

A lot of preperations went into this release to ensure that the merge happens as smoothly as possible.

{{Note|TODO: replace with actual blog post}}

For more information, the timeline and the effects, read the blog post: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/88/diffs

== Significant changes ==

=== Jellyfin ===

Jellyfin now uses the recommended fork of ffmpeg called {{pkg|jellyfin-ffmpeg}} by default. If you want to change that, take a look at the <code>ffmpegpath</code> variable in <code>/etc/conf.d/jellyfin</code>. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/69924 !69924])

Jellyfin was disabled for ARM architectures (<code>aarch64</code> and <code>armv7</code>) and is only available for <code>x86_64</code>. The relevant issue is: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16613

=== Bats ===

"main/bats" was renamed to "main/bats-core". Now there is a meta package "community/bats" which contains:

* bats-core
* bats-file
* bats-support
* bats-assert

=== Xen ===

qemu-traditional and stubdom are removed from the build in this release, see https://git.alpinelinux.org/aports/commit/?id=24217a24da3924039b000eb17c04bf3f01bf1f12

The regular qemu aport, community/qemu, is now build with xen support, see https://git.alpinelinux.org/aports/commit/?id=a9249e2e0de827e88d84c01f9731aeebd248be13

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* GCC 14.2.0
* LLVM 19
* Go 1.23.3
* Rust 1.82
* GNOME 47.1
* KDE Plasma 6.2.3
* LXQt 2.1.0

=== GCC 14 ===

GCC was upgraded to 14.2.0 and as a result all packages in Alpine 3.21 are compiled with GCC 14.2.0.

Make sure to read all changes: https://gcc.gnu.org/gcc-14/changes.html

=== LXQt 2.1 ===

LXQt has been updated to release 2.1.0
* It now uses Qt6
* Many parts of LXQt are now wayland ready¹, but wayland ports of the following are pending: {{pkg|screengrab}}, {{pkg|lxqt-globalkeys}}, and keyboard indicator, some input settings, and settings of monitor, power button, and screen locker.
* LXQt Panel has a new default application menu called Fancy Menu.
¹ [https://github.com/lxqt/lxqt-wayland-session lxqt-wayland-session] has not been packaged yet, but most folks wanting to test on wayland will want to use it.

=== PostgreSQL 17 ===

This release features {{pkg|postgresql17}}. We dropped support for {{pkg|postgresql14}}, and moved {{pkg|postgreSQL15}} from main to community.

=== LLVM 19 ===

We packaged LLVM 19 in our repositories. Coming to total of 5 supported LLVM versions: {{pkg|llvm19}}, {{pkg|llvm18}}, {{pkg|llvm17}}, {{pkg|llvm16}}, {{pkg|llvm15}}.

== Significant removals ==

=== ISC DHCP ===

{{Note|TODO: Write something cool if https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/70974 (or alternative) is merged }}

=== Gogs ===

<code>gogs</code> was removed due to multiple high-severity vulnerabilities which are open within a year. The developers of Gogs were contacted multiple times by the Forgejo team, but got no response. Therefore we removed Gogs from our repositories. ([https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/75304 !75304])

Please consider migrating to {{pkg|forgejo|branch=edge|arch=}} or {{pkg|gitea|branch=edge|arch=}}. Both forks are available in our community repo, like gogs was.

The Gitea fork of Gogs was created in 2016 by contributors who were annoyed by the single-maintainer management model of Gogs. Forgejo is a fork of Gitea, which was created because the for-profit company Gitea Ltd took over the maintainership, see also https://forgejo.org/compare-to-gitea/.

=== neofetch ===

The upstream repository was archived in April, therefore is unmaintained and we removed it from our repositories. {{pkg|fastfetch}} provides similar functionality.

Release Notes for Alpine 3.20.0

2024-05-20T22:42:32Z

Omni: podman 5.x

== 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 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.

==== 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 workaround ====

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 }}

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

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

== 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 {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|valkey-compat|branch=v3.20|arch=}}|{{pkg|valkey-compat|branch=edge|arch=}}}} package is provided with symlinks and group for easy Redis replacement.

The {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|redis|branch=v3.20|arch=}}|{{pkg|redis|branch=edge|arch=}}}} 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 #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 upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]

=== GNOME 46 ===

New upstream release of GNOME.

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 ==

* 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.78
* R 4.4
* Sway 1.9

Release Notes for Alpine 3.20.0

2024-05-20T22:27:40Z

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

== 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 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.

==== 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 workaround ====

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 }}

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

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

== 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 {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|valkey-compat|branch=v3.20|arch=}}|{{pkg|valkey-compat|branch=edge|arch=}}}} package is provided with symlinks and group for easy Redis replacement.

The {{#ifexpr: {{AlpineLatest}} >= 3.20 |{{pkg|redis|branch=v3.20|arch=}}|{{pkg|redis|branch=edge|arch=}}}} 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 #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 upstream: [https://github.com/aws/aws-cli/issues/8342 #8342]

=== GNOME 46 ===

New upstream release of GNOME.

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.78
* R 4.4
* Sway 1.9

Release Notes for Alpine 3.20.0

2024-05-05T10:13:33Z

Omni: Add information about Redis, Valkey and Redict

== 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 <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.

==== 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:

{{Cmd|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 <code>update-grub</code> has not been executed any more since the upgrade to grub 2.12.

== Others ==

=== 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.

A [https://pkgs.alpinelinux.org/packages?name=valkey-compat valkey-compat] package is provided with symlinks and group for easy Redis replcament.

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

Creating an Alpine package

2024-02-12T10:27:45Z

Omni: Undo revision 26384 by Omni (talk)

{{TOC right}}
== Overview ==

This is a brief list of the steps to add a new package. Details are below, but a NB can miss a few steps.
<ol>
<li>Create an account on github.alpine
<li>Setup the build environment for aports.
<li>Fork the aports repository.
<li>Clone your new fork.
<li>Set git pull.rebase=true, set your username and email.
<li>Create and switch to a new branch (don't use master).
<li>Add a new directory under testing that is your new package name.
<li>Add your APKBUILD file.
<li>Run abuild checksum
<li>Make sure you run the apkbuild-lint and aport -r and there are no warnings.
<li>Commit your APKBUILD with the commit message: 'testing/packagename: new aport'
<li>Push your changes to your fork on github.alpine.
<li>Create a merge request.
</ol>

Please see the rest of this wiki for details on the steps above.

== Requirements ==

To build a package for Alpine Linux you need an Alpine Linux installation. Check the [[Installation]] page to see all available installation options.

== Setup your system and account ==
{{:Setup_your_system_and_account_for_building_packages}}

== Getting some help ==

It might be wise to start by checking what the [[Abuild and Helpers|abuild]] program can/cannot do.

{{Cmd|abuild -h}}

For real help, you can also go on #alpine-devel on [[IRC]].

A reference for APKBUILD files is available as [[APKBUILD Reference]] wiki page or a man page in the 'abuild-doc' package:

{{Cmd|man APKBUILD}}

== Creating an APKBUILD file ==

=== Use a template APKBUILD ===

To create the actual APKBUILD file {{Pkg|newapkbuild}} can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.

If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.

{{:Abuild and Helpers}}

{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}

[[Abuild_and_Helpers#apkbuild-cpan|apkbuild-cpan]] simplifies the creation of perl packages from CPAN and [[Abuild_and_Helpers#apkbuild-pypi|apkbuild-pypi]] ease the generation of APKBUILD files for python packages from PyPi.

If you are creating a daemon package which needs initd scripts you can add the -c making it:

{{Cmd|newapkbuild -c ''packagename''}}

This will copy the sample initd and confd files to the build directory. 
A third file sample.install file will be copied as well (we will discuss this later on).

=== Modify your APKBUILD ===
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source).

If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like:

"$pkgdir"/somedir

This will prevent issues with spaces/special characters in the future.

{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}

=== APKBUILD variables/functions ===

==== source ====

The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.

Here are few things to note:

* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
: {{cmd|abuild checksum}}
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
: (or similar depending on the package).

* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
: You must prepend '${pkgname}-${pkgver}.tar.gz::' to the protocol, like so:
: <pre>source="${pkgname}-${pkgver}.tar.gz::http://oss.example.org/?get=software&ver=1.0"</pre>
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.

* Some projects didn't provide a release tarball. Beware that some git services (gitweg, cgit, …?) doesn’t provide ''stable'' tarballs, so when you point source to an tarball like <tt>https://repo.or.cz/w/gitstats.git/snapshot/ad7efbb9399e60cee6cb217c6b47e604174a8093.tar.gz</tt>, then you will run into issues because the checksum changes when downloading on the build system. This is not a problem on GitHub, GitLab and other decent services provides, they provide ''stable'' tarballs.

* abuild currently supports the following protocols for remote file retrieval:
** http
** https
** ftp



* abuild currently supports the following archive types/archive file extensions:
** .tar
** .tar.gz / .tgz
** .tar.bz2
** .tar.lz (only in Alpine >=3.7)
** .tar.lzma
** .tar.xz
** .zip

==== depends & makedepends ====

Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package in depends, you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [https://en.wikipedia.org/wiki/Rtfm RTFM].

No kidding, lots of important information can be found in the package INSTALL and README files (or the likes). Another good way is the run <code>./configure --help</code> from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a source directory you can create one with the command:

{{Cmd|abuild unpack}}

Running <code>configure</code> will also show you how you can disable a specific option for this package. For instance, a good example is "--disable-nls" which will disable native language support and thus does not depend on gettext (libiconv, glib, ...).

Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided by the package builder but please try to follow Alpine's design concept as much as possible.

An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo Linux ebuilds (previous versions of Alpine were based on Gentoo).

* [https://gitweb.gentoo.org/repo/gentoo.git/tree/ Gentoo Ebuilds]
* [https://archlinux.org/packages/?q=search Arch Linux packages] [https://aur.archlinux.org/ Arch Linux User Repository]

==== license ====

The '''license''' tag must reflect the license of the source code. Please check the source tarball for COPYING, LICENSE, or other files with names that indicates that it contains licensing information. Beside the license file most developer include headers in the source code files with licensing details.

If the license is on the [https://spdx.org/licenses/ SPDX License List] or [https://spdx.org/licenses/exceptions-index.html SPDX License Exceptions], use the identifier specified by SPDX.

Note that some licenses have additional requirements that should be adhered to. The <code>MIT</code> license for example has the requirement:

<blockquote>
The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.
</blockquote>

This means that we need to include the license as shipped with the project.

If a package has a special/custom license or is not listed as [https://opensource.org/licenses/alphabetical OSI approved], use the identifier "custom". In that case we need to provide the license file with the package as well.

Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows:

subpackages="$pkgname-doc"

Add a similar line to the following to your package() function, depending on the license description file:

{{Cmd|install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING}}

If you follow these steps then abuild will automatically add the license to the package-doc apk for you.

{{Note|Some build tools, such as Python's <code>gpep517</code>, automatically include the license during the build step. In such cases it is not necessary to package the license separately.}}

{{Warning|It is not acceptable to package software with "unknown" license! If you can't find the license of the source code, please contact the author and ask them to specify the license. }}

==== arch ====

The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (e.g., a pure-python package).
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}

==== url ====

Website address for the program. This is useful later on when either finding documentation or other information about the package.

==== pkgdesc ====

A brief, one line, description of what the package does. Useful for the package management system. It should start with a capital letter and does '''not''' end with a period.

Here is an example from apk_info for the OpenSSH client package:

pkgdesc="Port of OpenBSD's free SSH release - client"

==== pkgver ====

Provide the release number of the package you are building.

==== pkgrel ====

The $pkgrel versioning is made so that if you change something in your APKBUILD file without changing the actual $pkgver, you can increment pkgrel so apk tools will detect it as an update. For instance, if you forget to add a dependency, you can add it afterward and you can +1 pkgver so apk finds this update and adds the missing dependency. When there's an upstream version change, we reset the pkgrel to 0.

==== pkgname ====

The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"

==== install ====

There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:

<dl>
<dt>$pkgname.pre-install
<dd>This script is executed before package is installed. Typical use is when package needs a group and a user to be created. For example:
<pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and <code>apk add</code> will exit with failure.

<dt>$pkgname.post-install
<dd>This script is executed after the package is installed.

<dt>$pkgname.pre-upgrade
<dd>Same as pre-install but is executed before upgrading/downgrading/reinstalling an already installed package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

<dt>$pkgname.post-upgrade
<dd>Same as post-install but is executed after upgrading/downgrading/reinstalling an already installed package.

<dt>$pkgname.pre-deinstall
<dd>This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.

<dt>$pkgname.post-deinstall
<dd>This script is executed after a package have been uninstalled. For example, can be used to restore busybox links:
<pre>
#!/bin/sh
busybox --install -s
</pre>

</dl>

If the package has a pre-install and post-install script the APKBUILD should have the ''install'' variable defined:
<pre>
...
install="$pkgname.pre-install $pkgname.post-install"

...
</pre>

==== subpackages ====

$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc.

The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system.

To see if you need the -dev package you can run the following cmd:

{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}

If this returns any files you need to include the -dev package.

 To see if you need the -doc package you can run the following cmd:

{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}

If this returns any directories you need to include the -doc package.

===== Custom subpackages =====

Some software additionally has non-essential files that do not qualify as either documentation or development content. These files should be placed in their own, specialized subpackage(s). Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function:

test() {
mkdir -p "$subpkgdir"/usr
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/
# or amove usr/package-test
}

We also need to add the package info to $subpackages variable:

subpackages="$pkgname-doc $pkgname-dev $pkgname-test"

After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir.

The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add:

depends="perl"
makedepends="perl-dev"

If we would install the base package it would not install perl, but if we install the package-test package it would.

==== Patches ====

Please make sure you always submit human readable patches. Ways to create them are:

directory compare:

{{Cmd|diff -Nurp original_directory new_directory > filename.patch}}

file compare:

{{Cmd|diff -up original.file new.file > filename.patch}}

If a patch contains a completely new file but not *.rej or *.orig file, you need to add -N option to diff, but you may need to add exclusions with <code>--exclude PATTERN</code> so that you do not inadvertently add files. You may need to manually delete unwanted files inside the patch file.

Because multiple patches can patch the same file, they can change the offsets required by subsequent patches. To make sure we always patch in a specific way, we should number the patches as follows:

10-patch1.patch 20-patch2.patch 30-patch3.patch

This way we are always sure that patch 1 is applied first, and if we want to add additional patches between them we can use appropriate indexes (e.g. 11, 12, 21, 22).

Add the names of the patch files to the ''source'' variable. If you haven't declared a custom ''prepare'' function, no further action is necessary. Otherwise, be sure to call ''default_prepare'' in your ''prepare'' function. For example:

prepare() {
default_prepare

# do your stuff
}

Note: Some older packages contain a ''for'' loop in the ''prepare'' function to apply patches. This is not needed anymore, as patches are handled by ''default_prepare''.

In Alpine >=3.4 you can define patch_args to supply the patch level. This only works if all the patches have the same patch level. If there are a lot of patches from different sources, there is a good chance that you may need to edit them, as discussed below.

To automatically patch the package (available only in Alpine >=3.4) if it uses a patch level (-pX) other than the default (-p1), you need to carefully modify the patch. First, you'll need a text editor that does not automatically convert between Windows and Unix new lines (or, disable this feature) so that it preserves the old code. The next thing you'll need to do is modify the paths on "+++" and "---" lines in the .patch file. You can begin the path with a/ and b/ like shown below. Next, you need to adjust the paths so that the relative base path is from inside $builddir. Anything to the left of $builddir, including $builddir itself, needs to be removed from the path. So, if $builddir is /home/USER/aports/community/chromium/src/chromium-65, you need to erase it on the "+++" and "---" lines. Inside the chromium-65 folder you can see a src folder that has 3rdparty as a descendant. If a patch originally has a deeper patch level, you may need to fill in the missing portion of the path. For example, use the <code>find . -name "Assertions.cpp"</code> command to find the full path to the file relative to the base.

{{Cat|example.patch|<nowiki>
Author: John Doe <johndoe@mail.com>
URL: http://.....
Summary: Fixes musl compatibility
----
--- a/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp.orig
+++ b/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp
@@ -142,7 +142,7 @@
};

FrameToNameScope::FrameToNameScope(void* addr) : m_name(0), m_cxaDemangled(0) {
-#if OS(MACOSX) || (OS(LINUX) && !defined(__UCLIBC__))
+#if OS(MACOSX) || (OS(LINUX) && defined(__GLIBC__))
Dl_info info;
if (!dladdr(addr, &info) || !info.dli_sname)
return;
</nowiki>}}

Portions of the patch may be outdated, removed completely as in the source code file completely removed, or moved or renamed files. You need to delete that section of the patch or find where that section of code changed and re-diff it.

It is good etiquette to give credit at the top and the location of where you originally found them with notes.

Excluding patches with global variable resembling patch_opts is not available on Alpine. To exclude patches you need to create your own custom prepare().

If you have a monolithic patch where there are a bunch of patches in one big patch, you could use filterdiff which is available in the patchutils package.

Just do something like:

<pre>
makedepends="patchutils"

prepare() {
...
cd "$builddir"
filterdiff -x '*drivers/video/logo*' "$srcdir"/original.patch > "$builddir"/modified.patch
patch -p1 -i "$builddir"/modified.patch
}
</pre>

You need to put the wildcard pattern in single quotes for it to work.

==== Configure options ====

Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location.

We are not covering the depend switches here we have discussed this already in the depend section.

==== Make options ====

If you notice weird problems when compiling or installing the package with make/make install you could try to disable [https://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be:

{{Cmd|make}}

To disable parallel we use:

{{Cmd|make -j1}}

We can use the same for make install.

Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed:

{{Cmd|make DESTDIR{{=}}"$pkgdir" install}}

Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and doas when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.

==== builddir ====
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.

<pre>
builddir="$srcdir"/$pkgname-$pkgver
</pre>

==== Additional files ====

If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file):

{{Cmd|install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf}}

== Build the package ==

If you did not already create the checksums as mentioned above you can do so now:

{{Cmd|cd $pkgname
abuild checksum}}

It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependencies from your repository and builds it, afterwards it will uninstall all those depending packages again.

{{Cmd|abuild -r}}

See also [[Abuild_and_Helpers|Abuild and Helpers]].

== Testing the package locally ==

When it completes, your package will be found in a subfolder of <code>~/packages</code>. You may want to test it on your machine but only if the package is not a critical system package like musl or apk-tools package. To avoid borking your system (as in making it impossible to use <code>apk add</code> or to restore back the system and the compiler toolchain) for a critical system package, you should test on a chroot first before using it live.

The best way to test a package locally is to modify your <code>/etc/apk/repositories</code> so that it includes the indexes to your locally built packages - the directories that contain <code>ARCH/APKINDEX.tar.gz</code>. For example the <code>/etc/apk/repositories</code> below includes locally built packages in testing, community and main. To use this example change <code>USER</code> to your login name.

{{Cat|/etc/apk/repositories|/home/USER/packages/testing/
/home/USER/packages/main/
/home/USER/packages/community/
https://dl-cdn.alpinelinux.org/alpine/edge/main
https://dl-cdn.alpinelinux.org/alpine/edge/community
https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

If you prefer to test a package without changing any other configuration you can use the <code>-X, --repository</code> option to <code>apk</code>:

{{Cmd|doas apk add --repository /home/USER/packages/testing $pkgname}}

== Code review ==

To successfully have your package pass through code reviewers (as of Feb 18, 2018 are nmeum and jirutka on GitHub) and possible increased acceptance, the following conventions need to be followed:

# Custom global variables should be prefixed with underscore (_).
# Compact code as in merged commands, removed unused variables, removal of functions that do the same thing that are automatically handled by abuild.
# Versioning is done properly. For details see [[APKBUILD_Reference#pkgver]].
# Licensing is done properly. Remove unnecessary copying of licensing that is already OSI approved.
# Naming conventions rules for unofficial variables as in _gitrev is preferred over commit.
# Indent with tabs not spaces.
# Removal of explicit return 1. (They are still found the old APKBUILD files if you are learning but are now strongly discouraged.)
# Disabling check() requires either (1) a comment (#) stating next to options="!check" that there is no test suite/unit tests or (2) functioning working check() function.
# Explicit call to subpackages="$pkgname-doc" must be used instead of explicit gzip man page compression.
# Ideally, lines should be no more than 80 columns wide

Additionally, make sure to run the linter on your package:
{{Cmd|doas apk add atools
apkbuild-lint APKBUILD}}

For more information see [[Development using git:Quality assurance]] and [[Package_policies]].
Also check out [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/COMMITSTYLE.md?ref_type=heads aports/COMMITSTYLE.md] and [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/CODINGSTYLE.md?ref_type=heads aports/CODINGSTYLE.md]

== Commit your work ==

After you successfully build your package and properly followed the conventions and requirements in the code review section, you can submit your APKBUILD to Alpine's git repository.

Update your git repo, before adding new files:

{{Cmd|cd $aportsdir
git pull}}

This should pull all the changes made by others into your local git repo.

When you think you are ready you can add your files to git:

NOTE: when using our Gitlab instance, you can create MR's for each package. Please squash all commits related to the same package into a single one per MR.

{{Cmd|cd $aportsdir
git add testing/$pkgdir (include any other files needed for the build; $pkgname.install...)
git commit}}

Use the following commit message template for new aports (without the comments):

{{Cat|template|testing/$pkgname: new aport # this will be the subject line
# a blank line
$url # project homepage
$pkgdesc # one line description}}

Or you could add the following and <code>chmod +x ports/.git/hooks/prepare-commit-msg</code> to automatically generate commit message which the default aports/.githooks/ does not:

{{Cat|aports/.git/hooks/prepare-commit-msg|<nowiki>#!/bin/sh
case "$2,$3" in
,|template,)
if git diff-index --diff-filter=A --name-only --cached HEAD \
| grep -q '/APKBUILD$'; then
meta() { git diff --staged | grep "^+$1" | sed 's/.*="\?//;s/"$//';}
printf 'testing/%s: new aport\n\n%s\n%s\n' "$(meta pkgname)" \
"$(meta url)" "$(meta pkgdesc)" "$(cat $1)" > "$1"
else
printf '%s\n\n%s' `git diff-index --name-only --cached HEAD \
| sed -n 's/\/APKBUILD$//p;q'` "$(cat $1)" > "$1"
fi;;
esac</nowiki>}}

Now your changes are only available locally in your repository.

Because you do not have push rights to the Alpine aports repository you need to create a merge request to [https://gitlab.alpinelinux.org/alpine/aports Alpine's GitLab instance].

Alternatively you can also create a diff (patch) of the changes you made and send this patch to the
[https://lists.alpinelinux.org/~alpine/aports alpine-aports mailinglist].

To create a diff patch:

{{Cmd|git format-patch HEAD^}}

or if you have sprunge, you can create a link to your patch for convenience

{{Cmd|git format-patch HEAD^ --stdout <nowiki>|</nowiki> sprunge}}

== Automated flagging of outdated ports ==
Consider adding your port to [https://release-monitoring.org/ Anitya], so it will be flagged as outdated
as soon as a new stable version is released by upstream.

== See Also ==
* [[APKBUILD Reference]]
* [[APKBUILD examples]]
* [[Development using git]]
* [[Development using git:Quality assurance]]

[[category: Package Manager]]

Creating an Alpine package

2024-02-12T10:22:58Z

Omni: /* license */ add note on gpep517 packaged python projects

{{TOC right}}
== Overview ==

This is a brief list of the steps to add a new package. Details are below, but a NB can miss a few steps.
<ol>
<li>Create an account on github.alpine
<li>Setup the build environment for aports.
<li>Fork the aports repository.
<li>Clone your new fork.
<li>Set git pull.rebase=true, set your username and email.
<li>Create and switch to a new branch (don't use master).
<li>Add a new directory under testing that is your new package name.
<li>Add your APKBUILD file.
<li>Run abuild checksum
<li>Make sure you run the apkbuild-lint and aport -r and there are no warnings.
<li>Commit your APKBUILD with the commit message: 'testing/packagename: new aport'
<li>Push your changes to your fork on github.alpine.
<li>Create a merge request.
</ol>

Please see the rest of this wiki for details on the steps above.

== Requirements ==

To build a package for Alpine Linux you need an Alpine Linux installation. Check the [[Installation]] page to see all available installation options.

== Setup your system and account ==
{{:Setup_your_system_and_account_for_building_packages}}

== Getting some help ==

It might be wise to start by checking what the [[Abuild and Helpers|abuild]] program can/cannot do.

{{Cmd|abuild -h}}

For real help, you can also go on #alpine-devel on [[IRC]].

A reference for APKBUILD files is available as [[APKBUILD Reference]] wiki page or a man page in the 'abuild-doc' package:

{{Cmd|man APKBUILD}}

== Creating an APKBUILD file ==

=== Use a template APKBUILD ===

To create the actual APKBUILD file {{Pkg|newapkbuild}} can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.

If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.

{{:Abuild and Helpers}}

{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}

[[Abuild_and_Helpers#apkbuild-cpan|apkbuild-cpan]] simplifies the creation of perl packages from CPAN and [[Abuild_and_Helpers#apkbuild-pypi|apkbuild-pypi]] ease the generation of APKBUILD files for python packages from PyPi.

If you are creating a daemon package which needs initd scripts you can add the -c making it:

{{Cmd|newapkbuild -c ''packagename''}}

This will copy the sample initd and confd files to the build directory. 
A third file sample.install file will be copied as well (we will discuss this later on).

=== Modify your APKBUILD ===
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source).

If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like:

"$pkgdir"/somedir

This will prevent issues with spaces/special characters in the future.

{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}

=== APKBUILD variables/functions ===

==== source ====

The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.

Here are few things to note:

* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
: {{cmd|abuild checksum}}
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
: (or similar depending on the package).

* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
: You must prepend '${pkgname}-${pkgver}.tar.gz::' to the protocol, like so:
: <pre>source="${pkgname}-${pkgver}.tar.gz::http://oss.example.org/?get=software&ver=1.0"</pre>
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.

* Some projects didn't provide a release tarball. Beware that some git services (gitweg, cgit, …?) doesn’t provide ''stable'' tarballs, so when you point source to an tarball like <tt>https://repo.or.cz/w/gitstats.git/snapshot/ad7efbb9399e60cee6cb217c6b47e604174a8093.tar.gz</tt>, then you will run into issues because the checksum changes when downloading on the build system. This is not a problem on GitHub, GitLab and other decent services provides, they provide ''stable'' tarballs.

* abuild currently supports the following protocols for remote file retrieval:
** http
** https
** ftp



* abuild currently supports the following archive types/archive file extensions:
** .tar
** .tar.gz / .tgz
** .tar.bz2
** .tar.lz (only in Alpine >=3.7)
** .tar.lzma
** .tar.xz
** .zip

==== depends & makedepends ====

Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package in depends, you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [https://en.wikipedia.org/wiki/Rtfm RTFM].

No kidding, lots of important information can be found in the package INSTALL and README files (or the likes). Another good way is the run <code>./configure --help</code> from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a source directory you can create one with the command:

{{Cmd|abuild unpack}}

Running <code>configure</code> will also show you how you can disable a specific option for this package. For instance, a good example is "--disable-nls" which will disable native language support and thus does not depend on gettext (libiconv, glib, ...).

Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided by the package builder but please try to follow Alpine's design concept as much as possible.

An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo Linux ebuilds (previous versions of Alpine were based on Gentoo).

* [https://gitweb.gentoo.org/repo/gentoo.git/tree/ Gentoo Ebuilds]
* [https://archlinux.org/packages/?q=search Arch Linux packages] [https://aur.archlinux.org/ Arch Linux User Repository]

==== license ====

The '''license''' tag must reflect the license of the source code. Please check the source tarball for COPYING, LICENSE, or other files with names that indicates that it contains licensing information. Beside the license file most developer include headers in the source code files with licensing details.

If the license is on the [https://spdx.org/licenses/ SPDX License List] or [https://spdx.org/licenses/exceptions-index.html SPDX License Exceptions], use the identifier specified by SPDX.

Note that some licenses have additional requirements that should be adhered to. The <code>MIT</code> license for example has the requirement:

<blockquote>
The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.
</blockquote>

This means that we need to include the license as shipped with the project.

{{Note|For python projects packaged with ''gpep517'', license files are per design already put under <code>/usr/lib/python3.11/site-packages/$pkgname-$pkgver.dist-info/</code> for you.}}

If a package has a special/custom license or is not listed as [https://opensource.org/licenses/alphabetical OSI approved], use the identifier "custom". In that case we need to provide the license file with the package as well.

Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows:

subpackages="$pkgname-doc"

Add a similar line to the following to your package() function, depending on the license description file:

{{Cmd|install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING}}

If you follow these steps then abuild will automatically add the license to the package-doc apk for you.

{{Note|Some build tools, such as Python's <code>gpep517</code>, automatically include the license during the build step. In such cases it is not necessary to package the license separately.}}

{{Warning|It is not acceptable to package software with "unknown" license! If you can't find the license of the source code, please contact the author and ask them to specify the license. }}

==== arch ====

The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (e.g., a pure-python package).
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}

==== url ====

Website address for the program. This is useful later on when either finding documentation or other information about the package.

==== pkgdesc ====

A brief, one line, description of what the package does. Useful for the package management system. It should start with a capital letter and does '''not''' end with a period.

Here is an example from apk_info for the OpenSSH client package:

pkgdesc="Port of OpenBSD's free SSH release - client"

==== pkgver ====

Provide the release number of the package you are building.

==== pkgrel ====

The $pkgrel versioning is made so that if you change something in your APKBUILD file without changing the actual $pkgver, you can increment pkgrel so apk tools will detect it as an update. For instance, if you forget to add a dependency, you can add it afterward and you can +1 pkgver so apk finds this update and adds the missing dependency. When there's an upstream version change, we reset the pkgrel to 0.

==== pkgname ====

The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"

==== install ====

There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:

<dl>
<dt>$pkgname.pre-install
<dd>This script is executed before package is installed. Typical use is when package needs a group and a user to be created. For example:
<pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and <code>apk add</code> will exit with failure.

<dt>$pkgname.post-install
<dd>This script is executed after the package is installed.

<dt>$pkgname.pre-upgrade
<dd>Same as pre-install but is executed before upgrading/downgrading/reinstalling an already installed package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

<dt>$pkgname.post-upgrade
<dd>Same as post-install but is executed after upgrading/downgrading/reinstalling an already installed package.

<dt>$pkgname.pre-deinstall
<dd>This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.

<dt>$pkgname.post-deinstall
<dd>This script is executed after a package have been uninstalled. For example, can be used to restore busybox links:
<pre>
#!/bin/sh
busybox --install -s
</pre>

</dl>

If the package has a pre-install and post-install script the APKBUILD should have the ''install'' variable defined:
<pre>
...
install="$pkgname.pre-install $pkgname.post-install"

...
</pre>

==== subpackages ====

$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc.

The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system.

To see if you need the -dev package you can run the following cmd:

{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}

If this returns any files you need to include the -dev package.

 To see if you need the -doc package you can run the following cmd:

{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}

If this returns any directories you need to include the -doc package.

===== Custom subpackages =====

Some software additionally has non-essential files that do not qualify as either documentation or development content. These files should be placed in their own, specialized subpackage(s). Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function:

test() {
mkdir -p "$subpkgdir"/usr
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/
# or amove usr/package-test
}

We also need to add the package info to $subpackages variable:

subpackages="$pkgname-doc $pkgname-dev $pkgname-test"

After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir.

The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add:

depends="perl"
makedepends="perl-dev"

If we would install the base package it would not install perl, but if we install the package-test package it would.

==== Patches ====

Please make sure you always submit human readable patches. Ways to create them are:

directory compare:

{{Cmd|diff -Nurp original_directory new_directory > filename.patch}}

file compare:

{{Cmd|diff -up original.file new.file > filename.patch}}

If a patch contains a completely new file but not *.rej or *.orig file, you need to add -N option to diff, but you may need to add exclusions with <code>--exclude PATTERN</code> so that you do not inadvertently add files. You may need to manually delete unwanted files inside the patch file.

Because multiple patches can patch the same file, they can change the offsets required by subsequent patches. To make sure we always patch in a specific way, we should number the patches as follows:

10-patch1.patch 20-patch2.patch 30-patch3.patch

This way we are always sure that patch 1 is applied first, and if we want to add additional patches between them we can use appropriate indexes (e.g. 11, 12, 21, 22).

Add the names of the patch files to the ''source'' variable. If you haven't declared a custom ''prepare'' function, no further action is necessary. Otherwise, be sure to call ''default_prepare'' in your ''prepare'' function. For example:

prepare() {
default_prepare

# do your stuff
}

Note: Some older packages contain a ''for'' loop in the ''prepare'' function to apply patches. This is not needed anymore, as patches are handled by ''default_prepare''.

In Alpine >=3.4 you can define patch_args to supply the patch level. This only works if all the patches have the same patch level. If there are a lot of patches from different sources, there is a good chance that you may need to edit them, as discussed below.

To automatically patch the package (available only in Alpine >=3.4) if it uses a patch level (-pX) other than the default (-p1), you need to carefully modify the patch. First, you'll need a text editor that does not automatically convert between Windows and Unix new lines (or, disable this feature) so that it preserves the old code. The next thing you'll need to do is modify the paths on "+++" and "---" lines in the .patch file. You can begin the path with a/ and b/ like shown below. Next, you need to adjust the paths so that the relative base path is from inside $builddir. Anything to the left of $builddir, including $builddir itself, needs to be removed from the path. So, if $builddir is /home/USER/aports/community/chromium/src/chromium-65, you need to erase it on the "+++" and "---" lines. Inside the chromium-65 folder you can see a src folder that has 3rdparty as a descendant. If a patch originally has a deeper patch level, you may need to fill in the missing portion of the path. For example, use the <code>find . -name "Assertions.cpp"</code> command to find the full path to the file relative to the base.

{{Cat|example.patch|<nowiki>
Author: John Doe <johndoe@mail.com>
URL: http://.....
Summary: Fixes musl compatibility
----
--- a/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp.orig
+++ b/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp
@@ -142,7 +142,7 @@
};

FrameToNameScope::FrameToNameScope(void* addr) : m_name(0), m_cxaDemangled(0) {
-#if OS(MACOSX) || (OS(LINUX) && !defined(__UCLIBC__))
+#if OS(MACOSX) || (OS(LINUX) && defined(__GLIBC__))
Dl_info info;
if (!dladdr(addr, &info) || !info.dli_sname)
return;
</nowiki>}}

Portions of the patch may be outdated, removed completely as in the source code file completely removed, or moved or renamed files. You need to delete that section of the patch or find where that section of code changed and re-diff it.

It is good etiquette to give credit at the top and the location of where you originally found them with notes.

Excluding patches with global variable resembling patch_opts is not available on Alpine. To exclude patches you need to create your own custom prepare().

If you have a monolithic patch where there are a bunch of patches in one big patch, you could use filterdiff which is available in the patchutils package.

Just do something like:

<pre>
makedepends="patchutils"

prepare() {
...
cd "$builddir"
filterdiff -x '*drivers/video/logo*' "$srcdir"/original.patch > "$builddir"/modified.patch
patch -p1 -i "$builddir"/modified.patch
}
</pre>

You need to put the wildcard pattern in single quotes for it to work.

==== Configure options ====

Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location.

We are not covering the depend switches here we have discussed this already in the depend section.

==== Make options ====

If you notice weird problems when compiling or installing the package with make/make install you could try to disable [https://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be:

{{Cmd|make}}

To disable parallel we use:

{{Cmd|make -j1}}

We can use the same for make install.

Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed:

{{Cmd|make DESTDIR{{=}}"$pkgdir" install}}

Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and doas when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.

==== builddir ====
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.

<pre>
builddir="$srcdir"/$pkgname-$pkgver
</pre>

==== Additional files ====

If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file):

{{Cmd|install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf}}

== Build the package ==

If you did not already create the checksums as mentioned above you can do so now:

{{Cmd|cd $pkgname
abuild checksum}}

It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependencies from your repository and builds it, afterwards it will uninstall all those depending packages again.

{{Cmd|abuild -r}}

See also [[Abuild_and_Helpers|Abuild and Helpers]].

== Testing the package locally ==

When it completes, your package will be found in a subfolder of <code>~/packages</code>. You may want to test it on your machine but only if the package is not a critical system package like musl or apk-tools package. To avoid borking your system (as in making it impossible to use <code>apk add</code> or to restore back the system and the compiler toolchain) for a critical system package, you should test on a chroot first before using it live.

The best way to test a package locally is to modify your <code>/etc/apk/repositories</code> so that it includes the indexes to your locally built packages - the directories that contain <code>ARCH/APKINDEX.tar.gz</code>. For example the <code>/etc/apk/repositories</code> below includes locally built packages in testing, community and main. To use this example change <code>USER</code> to your login name.

{{Cat|/etc/apk/repositories|/home/USER/packages/testing/
/home/USER/packages/main/
/home/USER/packages/community/
https://dl-cdn.alpinelinux.org/alpine/edge/main
https://dl-cdn.alpinelinux.org/alpine/edge/community
https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

If you prefer to test a package without changing any other configuration you can use the <code>-X, --repository</code> option to <code>apk</code>:

{{Cmd|doas apk add --repository /home/USER/packages/testing $pkgname}}

== Code review ==

To successfully have your package pass through code reviewers (as of Feb 18, 2018 are nmeum and jirutka on GitHub) and possible increased acceptance, the following conventions need to be followed:

# Custom global variables should be prefixed with underscore (_).
# Compact code as in merged commands, removed unused variables, removal of functions that do the same thing that are automatically handled by abuild.
# Versioning is done properly. For details see [[APKBUILD_Reference#pkgver]].
# Licensing is done properly. Remove unnecessary copying of licensing that is already OSI approved.
# Naming conventions rules for unofficial variables as in _gitrev is preferred over commit.
# Indent with tabs not spaces.
# Removal of explicit return 1. (They are still found the old APKBUILD files if you are learning but are now strongly discouraged.)
# Disabling check() requires either (1) a comment (#) stating next to options="!check" that there is no test suite/unit tests or (2) functioning working check() function.
# Explicit call to subpackages="$pkgname-doc" must be used instead of explicit gzip man page compression.
# Ideally, lines should be no more than 80 columns wide

Additionally, make sure to run the linter on your package:
{{Cmd|doas apk add atools
apkbuild-lint APKBUILD}}

For more information see [[Development using git:Quality assurance]] and [[Package_policies]].
Also check out [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/COMMITSTYLE.md?ref_type=heads aports/COMMITSTYLE.md] and [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/CODINGSTYLE.md?ref_type=heads aports/CODINGSTYLE.md]

== Commit your work ==

After you successfully build your package and properly followed the conventions and requirements in the code review section, you can submit your APKBUILD to Alpine's git repository.

Update your git repo, before adding new files:

{{Cmd|cd $aportsdir
git pull}}

This should pull all the changes made by others into your local git repo.

When you think you are ready you can add your files to git:

NOTE: when using our Gitlab instance, you can create MR's for each package. Please squash all commits related to the same package into a single one per MR.

{{Cmd|cd $aportsdir
git add testing/$pkgdir (include any other files needed for the build; $pkgname.install...)
git commit}}

Use the following commit message template for new aports (without the comments):

{{Cat|template|testing/$pkgname: new aport # this will be the subject line
# a blank line
$url # project homepage
$pkgdesc # one line description}}

Or you could add the following and <code>chmod +x ports/.git/hooks/prepare-commit-msg</code> to automatically generate commit message which the default aports/.githooks/ does not:

{{Cat|aports/.git/hooks/prepare-commit-msg|<nowiki>#!/bin/sh
case "$2,$3" in
,|template,)
if git diff-index --diff-filter=A --name-only --cached HEAD \
| grep -q '/APKBUILD$'; then
meta() { git diff --staged | grep "^+$1" | sed 's/.*="\?//;s/"$//';}
printf 'testing/%s: new aport\n\n%s\n%s\n' "$(meta pkgname)" \
"$(meta url)" "$(meta pkgdesc)" "$(cat $1)" > "$1"
else
printf '%s\n\n%s' `git diff-index --name-only --cached HEAD \
| sed -n 's/\/APKBUILD$//p;q'` "$(cat $1)" > "$1"
fi;;
esac</nowiki>}}

Now your changes are only available locally in your repository.

Because you do not have push rights to the Alpine aports repository you need to create a merge request to [https://gitlab.alpinelinux.org/alpine/aports Alpine's GitLab instance].

Alternatively you can also create a diff (patch) of the changes you made and send this patch to the
[https://lists.alpinelinux.org/~alpine/aports alpine-aports mailinglist].

To create a diff patch:

{{Cmd|git format-patch HEAD^}}

or if you have sprunge, you can create a link to your patch for convenience

{{Cmd|git format-patch HEAD^ --stdout <nowiki>|</nowiki> sprunge}}

== Automated flagging of outdated ports ==
Consider adding your port to [https://release-monitoring.org/ Anitya], so it will be flagged as outdated
as soon as a new stable version is released by upstream.

== See Also ==
* [[APKBUILD Reference]]
* [[APKBUILD examples]]
* [[Development using git]]
* [[Development using git:Quality assurance]]

[[category: Package Manager]]

Custom Kernel

2023-12-15T14:29:04Z

Omni: /* Vanilla targets and tuning */ x86-64 bitness 64

{{Draft}}

This process of building a '''custom configured kernel''' assumes you are running on Alpine Linux utilizing abuild & aports.

== But why? ==

You want to build a custom kernel to enable experimental hardware or features or outdated hardware, to reduce bloat further, to tune the kernel to the hardware.

The lts kernel for most Alpine ARCHs uses defaults to balance throughput at the expense of some responsiveness, and support for many devices. You can tweak the kernel for desktop use and low latency and responsiveness.

You should disable modules to increase security. By default, Alpine will install modules but not disable most of them. Disabling modules will reduce an DMA attack but not eliminate it completely. If you have a newer processor with VT-d, you can mitigate as long as you:

Leave <code>CONFIG_INTEL_IOMMU_DEFAULT_ON=y</code> or pass <code>intel_iommu=on</code> as a kernel parameter and disable kernel logging so the attacker doesn't gain DMAR address information through dmesg.[https://blog.frizk.net/2016/11/disable-virtualization-based-security.html] Also remove references to the kernel version to calculate the IOMMU addresses.[https://link.springer.com/content/pdf/10.1186/s13173-017-0066-7.pdf]

To increase the security of the boot process, if you have a TPM, you could set <code>CONFIG_INTEL_TXT=y</code> (Enable Intel(R) Trusted Execution Technology (Intel(R) TXT)) (which is not enabled in the hardened kernel by default), then you would need the SINIT module (provided only by Intel)[https://software.intel.com/en-us/articles/intel-trusted-execution-technology], a possibly compiled TrustedGrub2[https://github.com/Rohde-Schwarz-Cybersecurity/TrustedGRUB2], trousers[https://sourceforge.net/projects/trousers/?source=navbar], tboot[https://sourceforge.net/projects/tboot/]. These packages are not in aports and it is unknown if these tools work on musl. It's not recommended for Edge. Also, there would be trigger packages to generate hashes for the kernel and the mkinitfs updates.

== Setting up the Alpine Build System ==

First, you need to follow the steps in [[Creating_an_Alpine_package#Setup_your_system_and_account|Setup your system and account for building packages]]. You also need to configure your {{path|/etc/apk/repositories}} so that they search locally for your apks. See [[Creating_an_Alpine_package#Testing_the_package_locally|Testing the package locally]] for details.

After setting up accounts and repos, change your shell's current working directory to '''aports''' that you just cloned.

{{cmd|$ cd aports}}

== Working with aports ==

We will try using an existing lts kernel just tweaking the {{path|lts.ARCH.config}} file.

=== Switching to the proper release version ===

You need to switch to the proper branch that matches the release so that the kernel compiles against the dependencies properly.

{| cellpadding="5" border="1" class="wikitable"
|-
! Alpine version
! Remote branch
|-
| Edge
| master
|-
| 3.17.0
| 3.17-stable
|-
|}

The following is required to get access to the {{path|APKBUILD}} released for that version of Alpine and which you will create a commit for.

If you are on 3.17 do:

{{cmd|$ git checkout -b 3.17-stable origin/3.17-stable}}

If you are on Edge do:

{{cmd|$ git checkout master}}

=== Creating your config ===

You can use {{pkg|linux-lts}} but what you should do is create a local branch by doing:

For Alpine Edge:

{{cmd|$ git checkout -b my-custom-kernel}}

For Alpine 3.17:

{{cmd|$ git checkout -b my-custom-kernel origin/3.17-stable}}

Doing it this way, you do less work in maintaining. All you need to do is keep ''master'' or ''3.17-stable'' in sync[https://help.github.com/articles/syncing-a-fork/][https://help.github.com/articles/configuring-a-remote-for-a-fork/] and merge any conflicts.

First switch to the branch by doing <code>git checkout my-custom-kernel</code>. Then, you need to navigate to the {{path|main/linux-lts}} folder where you should see a APKBUILD and some config- files. When you are done with your edits either by editing directly the APKBUILD and copying the {{path|lts.ARCH.config}} as {{path|.config}} in the {{path|linux-4.15}} folder. You will then move the {{path|.config}} back overriding the {{path|lts.ARCH.config}} generated by <code>make menuconfig</code> (discussed below in the ''Configuring kernel'' section). After generating your config, you need to <code>abuild checksum</code>. Then, do <code>git add APKBUILD lts.ARCH.config</code> where ARCH is whatever architecture (x86, x86_64, ...) you use. Then, you need to do <code>git commit APKBUILD config-NAME.ARCH -m "Enabled these options ...."</code> for your customization the ARCHitecture of your system. You do this so that git can keep your code separate from Alpine's and so your changes float forward between kernel updates.

== Adding custom patches ==

Custom patches should be added to ''sources=''.

After you added the URL, you need to produce a checksum by doing <code>abuild checksum</code>.

The custom patches may not be autopatched, due to being distributed as an archive or different patch level, so you need to define what to do with it in the prepare().

== Configuring kernel ==

Attempt to build the kernel first. To do that, you do <code>abuild -rK</code> to install most of the dependencies. If it complains about a dependency like {{pkg|elfutils-dev}} use <code>-rKd</code>. Then, when it prompts for values for new found config options just hold enter till it starts compiling the kernel. There should be two sets one for -lts and the other for the -virt. Just {{Key|Ctrl}}+{{Key|C}} out of the compilation process after the second set so you can further customize the config. Then you go into the {{path|src/linux-VER}} and edit the config file. Copy the {{path|.config}} file overriding the {{path|lts.ARCH.config}} in the srcdir.

The alternative is to use the kernel configuration menu in the build-NAME folder, but before yo do that you need to <code>sudo apk add {{pkg|ncurses-dev}}</code>
{{path|
After you are done using the menu in the build-NAME folder by doing <code>make menuconfig</code>, you want to remove <code>ncurses-dev</code>. When you are done, it will be stored in ''.config'' which you need to again override the {{path|lts.ARCH.config}} file. When you are done updating the {{path|config-NAME.ARCH}}, you need to do <code>abuild checksum</code>.

The options in the kernel config are typically defaults. If your device is old, it may be set to n by default.

=== Vanilla targets and tuning ===

{|cellpadding="5" border="1" class="wikitable"
!ARCH
!Processor Type / CPU Selection / System Type
!Code Generation / Instruction Extensions
!Timer Frequency
!Preemption Model
!Bitness
|-
|s390x
|IBM zEnterprise 114 and 196
|IBM zBC12 and zEC12 (<code>-march=zEC12 -mtune=zEC12</code>)
|100 Hz
|No Forced Preemption (Server)
|64
|-
|ppc64le
|Server processors
|POWER8 (<code>-mcpu=power8</code>), AltiVec (<code>-Wa,-maltivec</code> to assembler or <code>-maltivec -mabi=altivec</code>), VSX
|100 HZ
|No Forced Preemption (Server)
|64
|-
|ppc
|
512x/52xx/6xx/7xx/74xx/82xx/83xx/86xx
* Apple PowerMac based machines
|AltiVec (<code>-Wa,-maltivec</code> to assembler or <code>-maltivec -mabi=altivec</code>) on >=74xx
|250 HZ
|No Forced Preemption (Server)
|32
|-
|x86_64
|Generic-x86-64
|(-mtune=generic ; SIMD assembly modules enabled based on simple compile test and/or presence of CPU flag)
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|64
|-
|x86
|586/K5/5x86/6x86/6x86MX
|(-mtune=generic ; SIMD assembly modules enabled based on simple compile test and/or presence of CPU flag)
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|32
|-
|armhf
|
* ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)
* Freescale i.MX family -- Cortex A (i.MX51, i.MX53, i.MX6 Quad/DualLite, i.MX6 SoloLite, i.MX6 SoloX, i.MX6 UltraLite, i.MX7 Dual)
* Qualcomm -- (MSM8X60, MSM8960, MSM8974)
* Allwinner SoCs -- (A10 (sun4i), A10s / A13 (sun5i), A31 (sun6i), A20 (sun7i), sun8i Family, (sun9i))
* ARM Ldt Versatile Express family --
|Either <code>-march=armv7-a</code> or <code>-march=armv5t -Wa,-march=armv7-a</code> based on a compile test. <code>-mfpu=vfp</code>
|100 Hz
|Voluntary Kernel Preemption (Desktop)
|32
|-
|aarch64
|
* Allwinner sunxi 64-bit SoC Family
* Broadcom BCM2835 family
* Marvell Berlin SoC Family
* ARMv8 based Samsung Exynos SoC family
* ARMv8 based Freescale Layerscape SoC family
* Hisilicon SoC Family
* Mediatek MT65xx & MT81xx ARMv8 SoC
* Marvell EBU SoC Family
* Qualcomm Platforms
* Rockchip Platforms
* AMD Seattle SoC Family
* Altera's Stratix 10 SoCFPGA Family
* NVIDIA Tegra SoC Family
* Spreadtrum SoC platform
* Cavium Inc. Thunder SoC Family
* ARMv8 software model (Versatile Express)
* AppliedMicro X-Gene SOC Family
* Xilinx ZynqMP Family
|
|300 HZ
|Voluntary Kernel Preemption (Desktop)
|64
|-
|}
If you do desktop multitasking, you may want to switch to Voluntary Kernel Preemption (Desktop) or Preemptible Kernel (Low-Latency Desktop) and up the Timer Frequency. If you run a dedicated render farm node or a dedicated bitcoin miner use No Forced Preemption (Server) and decrease the Timer Frequency.

Optimized modules (most are already compiled as modules):
* raid6 -- altivec, avx512, ssse3, avx2, mmx, sse, sse2, neon
* some operations of raid5 -- mmx (32 bit), sse (64 bit), avx
For Kernel API:
* 32-bit memcpy -- 3dnow
* 32-bit memory page clearing and copying -- sse (Athlon/K7 only), mmx
From x86/crypto, arm/crypto, powerpc/crypto:
* CAMELLIA -- avx2, avx, aes-ni
* CHACHA20 -- avx2, neon
* CAST5 -- avx
* CAST6 -- avx
* TWOFISH -- avx
* SERPENT -- avx2, avx, sse2
* SHA1 -- avx2, ssse3, neon, spe
* SHA2 -- avx2
* SHA256 -- ssse3, neon, spe
* SHA512 -- avx2, ssse3, neon
* POLY1305 -- avx2
* GHASH -- pclmulqdq (part of aes-ni), vmx (power8)
* AES -- aes-ni, neon, vmx (power8), spe
* CRC32 -- pclmulqdq, sse, neon, vmx (power8)
* CRCT10DIF -- pclmulqdq, sse, neon, vmx (power8)

=== Fast reboots with kexec ===

If you want to reboot the kernel fast avoiding the POST test, you need <code>sudo apk add {{pkg|kexec-tools}}</code> and enable kexec in the kernel:

Processor type and features
[*] kexec system call

=== Hibernation to prevent data loss ===

Power management and ACPI options
[*] Hibernation (aka 'suspend to disk')

Hibernation should be used if you have a laptop. You don't want the laptop to suddenly shut off resulting in data loss, you want it to save your work based on a percentage of battery life (this requires special script). When you do hibernation and when it restores back, it should lock down the computer and ask for prompt. Depending on your needs, the hibernated image can be encrypted/decrypted which again requires additional customization to scripts.

Hibernation with an unsanitized swap file is generally insecure because data and unlocked memory pages is swapped out in plaintext. To increase the security either disable swap (Alpine default) or use an encrypted swap. The swap file/partition is typically used as a dump of the hibernated image.

== Building ==

Before building, you may want to remove as many modules as possible. This will reduce the time to compile greatly. Also, you may want to use [https://github.com/ccache/ccache/ ccache] for faster recompiles especially if you are searching for the minimal set of options or modules to use or include.

You should then do an <code>abuild -r</code> to attempt to build it.

== Installing ==

To install it you do a <code>sudo apk add linux-NAME</code> where NAME is your custom kernel name.

== Testing ==

Before you test, you should install the lts kernel too, using <code>apk add {{pkg|linux-lts}}</code>. You may be missing a module and can't boot, so you use the other kernel as the fallback boot kernel. Don't forget to update your bootloader configuration.

To test, first you should make a bootable Alpine USB image. Then, when you have your rescue USB done, you <code>reboot</code> the computer.

To test it, you basically do trial and error. Sometimes your config is missing something if you want to have a bare minimum setting.

If you are curious about correctness testing, some kernel modules or components do preform self tests at the beginning of the boot process. The tools may have test suites that you run with the make command.

== See Also ==
* [https://wiki.archlinux.org/title/Kernel Archwiki Kernels]
* [https://wiki.gentoo.org/wiki/Kernel Gentoo Wiki Kernel]
* [https://wiki.gentoo.org/wiki/Kernel/Configuration Gentoo Wiki Kernel Configuration]

[[Category:Kernel]]

Release Notes for Alpine 3.19.0

2023-12-12T11:41:49Z

Omni: Mention openrc now defaults to cgroups v2

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

=== cgroups v2 ===

Cgroups version 2, or "unified", is now the default cgroup mode in [[OpenRC]]. The previous default was "hybrid", both version 1 and version 2.

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software has been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

<code>libc6-compat</code> [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

=== ifupdown ===

The <code>ifupdown</code> aport ('''not''' {{pkg|busybox-ifupdown}}) was unmaintained and removed in favor of the preferred {{pkg|ifupdown-ng}}.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry Pi ==

[https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] package has been simplified: there is now a single kernel flavor for each architecture. Previous [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] kernel packages are therefore replaced by [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. 
{{Path|config.txt}} file is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

This also means that the prebuilt images and files to download and use for the various models have changed, see the [[Raspberry_Pi#Compability_list|Compability list]] for guidance.

[[Category:News]]

OpenRC

2023-12-12T11:26:48Z

Omni: /* cgroups v2 */

== Quick-Start Information ==
Alpine Linux uses [https://github.com/OpenRC/openrc OpenRC] for its init system.

The following commands are available to manage the init system:
* Basics:
{{Cmd|rc-update add <service> <runlevel>}}
{{Cmd|rc-update del <service> <runlevel>}}
{{Cmd|rc-service <service> <start stop restart> # ⇔ /etc/init.d/service <start stop restart>}}

* To check services and their set runlevels:
{{Cmd|rc-status}}

* To change to a different runlevel:
{{Cmd|openrc <runlevel>}}

* Reboot/Halt/Poweroff: (And their equivalent from traditional GNU/Linux systems)
{{Cmd|reboot # ⇔ shutdown now -r}}
{{Cmd|halt # ⇔ shutdown now -H}}
{{Cmd|poweroff # ⇔ shutdown now -P}}

== Available Runlevels ==
The available runlevels are:
* '''default''' - Used if no runlevel is specified. (This is generally the runlevel you want to add services to.)
* '''hotplugged'''
* '''manual'''

The special runlevels are:
* '''sysinit''' - Brings up system specific stuff such as <code>/dev</code>, <code>/proc</code> and optionally <code>/sys</code> for Linux based systems. It also mounts <code>/lib/rc/init.d</code> as a ramdisk using tmpfs where available unless <code>/</code> is mounted rw at boot. <code>'''rc'''</code> uses <code>/lib/rc/init.d</code> to hold state information about the services it runs. sysinit always runs when the host first starts and should not be run again.
* '''boot''' - Generally the only services you should add to the boot runlevel are those which deal with the mounting of filesystems, set the initial state of attached peripherals and logging. Hotplugged services are added to the boot runlevel by the system. All services in the boot and sysinit runlevels are automatically included in all other runlevels except for those listed here.
* '''single''' - Stops all services except for those in the sysinit runlevel.
* '''reboot''' - Changes to the shutdown runlevel and then reboots the host.
* '''shutdown''' - Changes to the shutdown runlevel and then halts the host.

== rc-update usage ==
Usage: rc-update [options] add service <runlevel>
rc-update [options] del service <runlevel>
rc-update [options] show

Options: [suChqv]
-s, --stack Stack a runlevel instead of a service
-u, --update Force an update of the dependency tree
-h, --help Display this help output
-C, --nocolor Disable color output
-v, --verbose Run verbosely
-q, --quiet Run quietly

== rc-status usage ==
Usage: rc-status [options] [runlevel1] [runlevel2] ...

Options: [aclrsuChqv]
-a, --all Show services from all run levels
-c, --crashed Show crashed services
-l, --list Show list of run levels
-r, --runlevel Show the name of the current runlevel
-s, --servicelist Show service list
-u, --unused Show services not assigned to any runlevel
-h, --help Display this help output
-C, --nocolor Disable color output
-v, --verbose Run verbosely
-q, --quiet Run quietly

== rc-service usage ==
Usage: rc-service [options]

Options: [e:ilr:ChqVv]
-e, --exists <arg> tests if the service exists or not
-i, --ifexists if the service exists then run the command
-l, --list list all available services
-r, --resolve <arg> resolve the service name to an init script
-h, --help Display this help output
-C, --nocolor Disable color output
-V, --version Display software version
-v, --verbose Run verbosely
-q, --quiet Run quietly

== rc usage ==
Usage: rc [options]

Options: [a:o:s:SChqVv]
-a, --applet <arg> runs the applet specified by the next argument
-o, --override <arg> override the next runlevel to change into
when leaving single user or boot runlevels
-s, --service <arg> runs the service specified with the rest
of the arguments
-S, --sys output the RC system type, if any
-h, --help Display this help output
-C, --nocolor Disable color output
-V, --version Display software version
-v, --verbose Run verbosely
-q, --quiet Run quietly

== Preventing slow services from delaying boot ==

Services that take a while to start will block the boot process until they complete. E.g.: <code>iwd</code> and <code>networking</code> might delay startup of an interactive system rather than start in the background.

This can be remedied using [https://ptrcnull.me/posts/openrc-async-services/ async services]. See [https://wiki.gentoo.org/wiki/OpenRC/Stacked%20runlevel stacked runlevels] for more details on this.

== cgroups v2 ==

Since {{pkg|openrc}} 0.51 cgroups v2, or "unified", is the default.
You can enable hybrid cgroups v1 & v2 by editing <code>/etc/rc.conf</code> and setting <code>rc_cgroup_mode="hybrid"</code>.

Then you should run
{{Cmd|rc-service cgroups start}}
to take effect

and
{{Cmd|rc-update add cgroups}}
to auto mount the cgroup filesystem on boot

== See also ==
* [https://wiki.gentoo.org/wiki/OpenRC Gentoo Wiki]
* [https://wiki.archlinux.org/title/OpenRC ArchWiki]
* [https://wiki.postmarketos.org/wiki/OpenRC PostmarketOS Wiki]

[[Category:Booting]]

Release Notes for Alpine 3.19.0

2023-12-09T12:53:52Z

Omni: /* Raspberry pi */

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software has been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

<code>libc6-compat</code> [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

=== ifupdown ===

The <code>ifupdown</code> aport ('''not''' {{pkg|busybox-ifupdown}}) was unmaintained and removed in favor of the preferred {{pkg|ifupdown-ng}}.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry Pi ==

[https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] package has been simplified: there is now a single kernel flavor for each architecture. Previous [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] kernel packages are therefore replaced by [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. 
{{Path|config.txt}} file is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

This also means that the prebuilt images and files to download and use for the various models have changed, see the [[Raspberry_Pi#Compability_list|Compability list]] for guidance.

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-12-09T12:53:17Z

Omni: /* Raspberry pi */ Add information on changes to what image/file to download

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software has been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

<code>libc6-compat</code> [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

=== ifupdown ===

The <code>ifupdown</code> aport ('''not''' {{pkg|busybox-ifupdown}}) was unmaintained and removed in favor of the preferred {{pkg|ifupdown-ng}}.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

[https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] package has been simplified: there is now a single kernel flavor for each architecture. Previous [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] kernel packages are therefore replaced by [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. 
{{Path|config.txt}} file is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

This also means that the prebuilt images and files to download and use for the various models have changed, see the [[Raspberry_Pi#Compability_list|Compability list]] for guidance.

[[Category:News]]

Raspberry Pi

2023-12-09T12:44:38Z

Omni: Add compability list and remove invalid suggestions from the first preparation step

{{warning | 11 Feb 2021 - There is currently a known bug upstream [https://github.com/raspberrypi/firmware/issues/1529 kernel/initramfs cannot be loaded from subdirectory with same name as volume label]. Since the kernel is installed to <code>boot/</code>, you must not use a label named <code>boot</code> for the fat32 partition. }}

{{TOC right}}

This tutorial explains how to install Alpine Linux on a Raspberry Pi. Alpine Linux will be installed in [[Installation#Diskless_Mode|diskless mode]], hence, [[Alpine local backup|Alpine Local Backup (lbu)]] is required to save modifications between reboots.

For scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs.

If any of the following apply, then installation in [[Classic install or sys mode on Raspberry Pi|sys-mode installation]] is likely more appropriate.

* There will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)
* Logs should persists across reboots
* Plan to install packages which consume more space than can be loaded into RAM
* Plan to install kernel modules (such as ZFS)

== Compability list ==

* '''armhf''' (defconfig bcmrpi) - Raspberry Pi 1, Zero, ZeroW, cm1
* '''armv7''' (defconfig bcm2709) - Raspberry Pi 2, 3, 3+, Zero2W, cm3, cm3+
* '''aarch64''' (defconfig bcm2711) - Raspberry Pi 3, 3+, 4, 400, Zero2W, cm3, cm3+, cm4, 5

== Preparation ==

# [https://alpinelinux.org/downloads/ Download] the Alpine for Raspberry Pi tarball. Use the compability list above when choosing image/file to download.
# [[Create_a_Bootable_Device#Manually_copying_Alpine_files|Create a bootable FAT32 partition on your SD card.]] The partitioning and formatting part of the instructions on the linked page could be done using a graphical partitioning tool such as [https://en.wikipedia.org/wiki/GNOME_Disks gnome-disks], just make sure the partition type is <code>W95 FAT32 (LBA)</code>. (The current type can be found in the "Type" column in the output of <code>fdisk -l</code>.)
# Extract the tarball to the root of the bootable FAT32 partition.

To setup a headless system, a bootstrapping configuration overlay file [https://github.com/macmpi/alpine-linux-headless-bootstrap headless.apkovl.tar.gz] may be added to enable basic networking, so that following configuration steps can be performed under <code>ssh</code>. Pi Zero may be configured with simple USB ethernet-gadget networking with another computer sharing its internet connection.

Optionally create a '''usercfg.txt''' file on the partition to configure low-level system settings. Specifications can be found [https://www.raspberrypi.org/documentation/configuration/config-txt here]. However, note some settings can only be set directly in '''config.txt''', which may be overwritten after updates. In particular, <code>gpu_mem</code> will have no effect when specified in '''usercfg.txt''' ([https://github.com/raspberrypi/firmware/issues/1332 source]). Some interesting values include:
* To enable the UART console: <code>enable_uart=1</code>
* To enable audio: <code>dtparam=audio=on</code>
* If you see black edges around your screen after booting the Pi, you can add <code>disable_overscan=1</code>
* If you plan to install on a Pi Compute Module 4 with I/O board, you may need to add: <code>otg_mode=1</code>

Recent versions include Broadcom firmware files. If you're using an older Alpine version, see [[#Wireless_support_with_older_Alpine_images|section below]].

== Installation ==

Follow these steps to install Alpine Linux in Diskless Mode:

# Insert the SD card into the Raspberry Pi and power it on
# Login into the Alpine system as root. Leave the password empty.
# Type <code>setup-alpine</code>
# Once the installation is complete, commit the changes by typing <code>lbu commit -d</code>

Type <code>reboot</code> to verify that the installation was indeed successful.

== Post Installation ==

=== Update the System ===

After installation, make sure your system is up-to-date:

{{cmd|apk update
apk upgrade}}

Don't forget to save the changes:

{{cmd|lbu commit -d}}

Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in [[Upgrading Alpine#Upgrading Alpine Linux on other removable media (such as CF/USB)|upgrading Alpine Linux for removable media]].

=== Clock-related error messages ===

During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have
a hardware clock, thus you need to disable the hwclock daemon and enable swclock:

{{cmd|rc-update add swclock boot # enable the software clock
rc-update del hwclock boot # disable the hardware clock}}

Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a
[https://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol (NTP)] daemon. Make sure you have a
NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following
command:

{{cmd|setup-ntp}}

The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is
installed and running:

{{cmd|lbu commit -d
reboot}}

After reboot, make sure the <code>date</code> command outputs the correct date and time.

=== WiFi on boot ===
If you have already [[Connecting_to_a_wireless_access_point|configured WiFi]] during the setup, the connection will not return on reboot.
You will need to start up a service to automatically connect to the wireless access point.
# Run <code>rc-update add wpa_supplicant boot</code> to connect to the wireless access point during bootup.
# Run it manually with <code>rc-service wpa_supplicant start</code>.

=== Enable Graphics ===
Remount the boot partition writeable (i.e. <code>/media/mmcblk0p1</code>):

{{cmd|mount /media/mmcblk0p1 -o rw,remount}}

Add the following lines to <code>/media/mmcblk0p1/config.txt</code>:

dtoverlay=vc4-kms-v3d

If you are experiencing graphical issues, you can also try:

dtoverlay=vc4-fkms-v3d

And perhaps also raising the default <code>gpu_mem</code>:

gpu_mem=128

Note that raising the gpu memory is not likely to [https://www.raspberrypi.com/documentation/computers/config_txt.html#gpu_mem actually improve performance on the Pi4]

Install the Mesa drivers:

{{cmd|<nowiki>apk add mesa-dri-gallium</nowiki>}}

Then reboot:

{{cmd|lbu_commit -d; reboot}}

=== WiFi drivers ===
As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from <code>linux-firmware-brcm</code> to the <code>linux-firmware-cypress</code> package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break.
Use the ethernet interface to download the required packages:

{{cmd|apk add linux-firmware-cypress}}

And reboot.

== Persistent storage ==
=== Loopback image with overlayfs ===

When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs.

First, make the SD card writable again and change fstab to always do so:
{{cmd|mount /media/mmcblk0p1 -o rw,remount
sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab}}

Create the loop-back file, this example is 1 GB:

{{cmd|dd if=/dev/zero of=/media/mmcblk0p1/persist.img bs=1024 count=0 seek=1048576}}

Install the ext utilities:

{{cmd|apk add e2fsprogs}}

Format the loop-back file:

{{cmd|mkfs.ext4 /media/mmcblk0p1/persist.img}}

Mount the storage:

{{cmd|echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0" >> /etc/fstab
mkdir /media/persist
mount -a}}

Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else.
{{Warning|Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay must use its own workdir.}}

{{cmd|mkdir /media/persist/usr
mkdir /media/persist/.work_usr
echo "overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work_usr 0 0" >> /etc/fstab
mount -a}}

Your /etc/fstab should look something like this:
{{Cmd|/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0
/dev/usbdisk /media/usb vfat noauto,ro 0 0
/dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,errors=remount-ro 0 0
/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0
overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work_usr 0 0}}

Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)
{{cmd|lbu_commit -d}}

Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage.

If you do want to install something small at boot, you can use <code>apk add</code> and <code>lbu commit -d</code>.

If it is something a bit bigger, then you can use <code>apk add</code> but then not commit it. It will be persistent (in <code>/user</code>), but be sure to check everything you need is in that directory and not in folders you have not made persistent.

=== Traditional disk-based (sys) installation ===
{{Merge|Classic install or sys mode on Raspberry Pi|There's an existing page for sys-installations on RasPi.}}

It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.

Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be <code>mmcblk0p1</code>) , and a second partition to hold the root filesystem (here it'll be <code>mmcblk0p2</code>). Boot and configure your diskless system as above, then create a root filesystem:

{{cmd|apk add e2fsprogs
mkfs.ext4 /dev/mmcblk0p2}}

Now do a disk install via a mountpoint. The <code>setup-disk</code> script will give some errors about syslinux/extlinux, but you can ignore them.
The Raspberry Pi doesn't need them to boot.

{{cmd|<nowiki>mkdir /stage
mount /dev/mmcblk0p2 /stage
setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage
# (ignore errors about syslinux/extlinux)</nowiki>}}

Add a line to <code>/stage/etc/fstab</code> to mount the Pi's boot partition again:

{{cmd|/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0}}

Now add a <code>root=/dev/mmcblk0p2</code> parameter to the Pi's boot command line, either <code>cmdline-rpi2.txt</code> or <code>cmdline-rpi.txt</code> depending on model:

{{cmd|<nowiki>mount -o remount,rw /media/mmcblk0p1
sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt</nowiki>}}

You might also consider <code>overlaytmpfs=yes</code> here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown.

N.B. the contents of /boot will be ignored when the Pi boots. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case,
copying the files to boot partition manually, is not needed.

{{cmd|<nowiki>echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab</nowiki>}}

=== Persistent Installation on Raspberry Pi 3 ===
See [[Classic install or sys mode on Raspberry Pi]] and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084

=== Persistent Installation on Raspberry Pi 4 ===
As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4.

== Netboot ==

=== Netbooting Raspberry Pi 4 ===

The Raspberry Pi 4 bootloader can be configured to boot from the network [https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-4-bootloader-configuration]. Configure the bootloader with at least

{{cmd|<nowiki>BOOT_ORDER=0xf142
TFTP_PREFIX=1</nowiki>}}

and optionally also {{cmd|<nowiki>TFTP_IP=x.x.x.x</nowiki>}} where <code>x.x.x.x</code> is the IP address of your TFTP server.

If not configuring <code>TFTP_IP</code> in the bootloader, you'll need to configure your DHCP server to advertise the TFTP server IP address. This varies depending on your DHCP server; use the following details if applicable:

# Vendor class: <code>PXEClient:Arch:00000:UNDI:002001</code>
# Filename: <code>/</code>

The minimal set of files that your TFTP server needs to host are:

# <code>bcm2711-rpi-4-b.dtb</code> (from [https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/bcm2711-rpi-4-b.dtb raspberrypi/firmware/master/boot/bcm2711-rpi-4-b.dtb])
# <code>cmdline.txt</code> (see below)
# <code>config.txt</code> (see below)
# <code>fixup4.dat</code> (from [https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/fixup4.dat raspberrypi/firmware/master/boot/fixup4.dat], alternatively <code>fixup4cd.dat</code> for the cut down version)
# <code>initramfs-rpi4</code> (from [https://dl-cdn.alpinelinux.org/alpine/edge/releases/aarch64/netboot/initramfs-rpi4 alpine/edge/releases/aarch64/netboot/initramfs-rpi4])
# <code>start4.elf</code> (from [https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/start4.elf raspberrypi/firmware/master/boot/start4.elf], alternatively <code>start4cd.elf</code> for the cut down version)
# <code>vmlinuz-rpi4</code> (from [https://dl-cdn.alpinelinux.org/alpine/edge/releases/aarch64/netboot/vmlinuz-rpi4 alpine/edge/releases/aarch64/netboot/vmlinuz-rpi4])

<code>config.txt</code>:
{{cmd|<nowiki>[pi4]
kernel=vmlinuz-rpi4
initramfs initramfs-rpi4
arm_64bit=1
</nowiki>}}

<code>cmdline.txt</code>:
{{cmd|<nowiki>modules=loop,squashfs console=ttyAMA0,115200 ip=dhcp alpine_repo=http://dl-cdn.alpinelinux.org/alpine/edge/main modloop=http://dl-cdn.alpinelinux.org/alpine/edge/releases/aarch64/netboot/modloop-rpi4</nowiki>}}

Instead of using the <nowiki>http://dl-cdn.alpinelinux.org/alpine/edge/releases/aarch64/netboot/</nowiki> base URL above, pinning to a specific point in time is preferred. Raspberry Pi 4 netboot files are available from https://dl-cdn.alpinelinux.org/alpine/edge/releases/aarch64/netboot-20230329/ onward.

With the above configured the Raspberry Pi 4 should be able to boot from the network without an SD card.

== Troubleshooting ==

=== Long boot time when running headless ===

If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy.

If this is the case, simply plugging in any USB device should work around this issue, since it increases the amount of entropy available to the kernel via interrupts.

=== apk indicating 'No space left on device' ===

Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards.

=== Wireless support with older Alpine images ===

If you need Wi-Fi, you'll need to [https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm download] the latest Broadcom drivers to your SD card.
(Replace /mnt/sdcard with the correct mount point.)

git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git
cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm

== See Also ==

* [[Classic install or sys mode on Raspberry Pi]] - a variant.
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Browser Client]]
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Create a bootable SDHC from a Mac]]
* Build custom Raspberry Pi images based on Alpine via [https://github.com/tolstoyevsky/pieman Pieman]
* [[Tutorials and Howtos#Raspberry Pi]]

[[Category:Installation]]
[[Category: Raspberry]]

Release Notes for Alpine 3.19.0

2023-12-07T11:50:46Z

Omni: /* Others */ use code tags

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

<code>libc6-compat</code> [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

=== ifupdown ===

The <code>ifupdown</code> aport ('''not''' {{pkg|busybox-ifupdown}}) was unmaintained and removed in favor of the preferred {{pkg|ifupdown-ng}}.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

[https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] package has been simplified: there is now a single kernel flavor for each architecture. Previous [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] kernel packages are therefore replaced by [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. 
{{Path|config.txt}} file is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-12-07T11:04:42Z

Omni: /* Others */ ifupdown

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

''libc6-compat'' [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

=== ifupdown ===

The ''ifupdown'' aport ('''not''' {{pkg|busybox-ifupdown}}) was unmaintained and removed in favor of the preferred {{pkg|ifupdown-ng}}.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

The [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] has been simplified. There is now a single kernel flavor for each architecture. This means that the kernels [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] are replaced with [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. The {{Path|config.txt}} is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-12-07T10:52:14Z

Omni: /* Others */ gcompat

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== GNOME ===

GNOME packages have been updated to 45. As part of that release, Cheese has been replaced by Snapshot, and Eye of GNOME by Loupe as the default apps for taking and seeing pictures, respectively. In additions, GNOME Photos was dropped as being mostly unmaintained.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

=== GNU C Library Compatibility Layer ===

''libc6-compat'' [https://git.alpinelinux.org/aports/commit/?h=3.19-stable&id=1a122638315d6fe7908de9c34d3ac06eae76917a was removed] in favor of {{pkg|gcompat}} from Adélie Linux.

== Upgrades ==

* Linux 6.6
* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.4
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

== Raspberry pi ==

The [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi] has been simplified. There is now a single kernel flavor for each architecture. This means that the kernels [https://pkgs.alpinelinux.org/packages?name=linux-rpi2&branch=v3.18 linux-rpi2] and [https://pkgs.alpinelinux.org/packages?name=linux-rpi4&branch=v3.18 linux-rpi4] are replaced with [https://pkgs.alpinelinux.org/packages?name=linux-rpi&branch=edge linux-rpi]. The {{Path|config.txt}} is now generated by [https://pkgs.alpinelinux.org/packages?name=raspberrypi-bootloader-common&branch=edge raspberrypi-bootloader-common].

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-11-30T13:53:51Z

Omni: /* Others */ Yggdrasil breaking changes

Release Notes for Alpine 3.19.0

2023-11-27T11:39:25Z

Omni: /* HashiCorp packages */ Restructure and add SPDX link.

Release Notes for Alpine 3.19.0

2023-11-27T11:29:48Z

Omni: /* HashiCorp packages */ Present removed software as a list. I don't think we need to provide links to the respective project web sites but am not going to remove the links again if someone wants to re-add them.

Release Notes for Alpine 3.19.0

2023-11-27T11:18:40Z

Omni: /* HashiCorp packages */ Add link to our discussion. OpenTofu may not be moved to community before a stable release.

Creating an Alpine package

2023-11-13T21:36:42Z

Omni: /* license */ Add comment about MIT license

{{TOC right}}

== Requirements ==

To build a package for Alpine Linux you need an Alpine Linux installation. Check the [[Installation]] page to see all available installation options.

== Setup your system and account ==
{{:Include:Setup_your_system_and_account_for_building_packages}}

== Getting some help ==

It might be wise to start by checking what the [[Abuild|abuild]] program can/cannot do.

{{Cmd|abuild -h}}

For real help, you can also go on #alpine-devel on [[IRC]].

A reference for APKBUILD files is available as [[APKBUILD Reference]] wiki page or a man page in the 'abuild-doc' package:

{{Cmd|man APKBUILD}}

== Creating an APKBUILD file ==

=== Use a template APKBUILD ===

To create the actual APKBUILD file {{Pkg|newapkbuild}} can serve you a template to start with. It will create a directory with the given package name, place an example/template APKBUILD file to the given directory, and fill some variables if those are provided. Please check the [[Package_policies| package policies]] page about naming details.

If you doubt to which repository your package belongs to you can safely use '''testing'''. Building package in your aports/testing directory is not mandatory but this way the package is already at the right place.

{{:Include:Newapkbuild}}

{{Note|On older Alpine systems, abuild -c -n ''packagename'' was the way to create APKBUILD files. The 'packagename' was a parameter to the -n option so order of -c and -n matters. }}

[[Abuild_and_Helpers#apkbuild-cpan|apkbuild-cpan]] simplifies the creation of perl packages from CPAN and [[Abuild_and_Helpers#apkbuild-pypi|apkbuild-pypi]] ease the generation of APKBUILD files for python packages from PyPi.

If you are creating a daemon package which needs initd scripts you can add the -c making it:

{{Cmd|newapkbuild -c ''packagename''}}

This will copy the sample initd and confd files to the build directory. 
A third file sample.install file will be copied as well (we will discuss this later on).

=== Modify your APKBUILD ===
Edit APKBUILD and fill in the needed info (especially pkgname, pkgver, pkgdesc, url, license, depends and source).

If you are going to use any of the variables for directories like $pkgdir, always make sure they are double quoted like:

"$pkgdir"/somedir

This will prevent issues with spaces/special characters in the future.

{{Note|If you like syntax highlighting we suggest you to install vim. We have setup vim to recognize the APKBUILD file as a bash scripts so its easier to read them.}}

=== APKBUILD variables/functions ===

==== source ====

The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[Creating an Alpine package#install|install variable]]), patches, and all other necessary files.

Here are few things to note:

* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
: {{cmd|abuild checksum}}
: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
: (or similar depending on the package).

* When the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
: You must prepend '${pkgname}-${pkgver}.tar.gz::' to the protocol, like so:
: <pre>source="${pkgname}-${pkgver}.tar.gz::http://oss.example.org/?get=software&ver=1.0"</pre>
: This causes the file to be saved as ''software-1.0.tar.gz'' where abuild can use it, instead of ''?get=software&ver=1.0'', where abuild cannot use it.

* Some projects didn't provide a release tarball. Beware that some git services (gitweg, cgit, …?) doesn’t provide ''stable'' tarballs, so when you point source to an tarball like <tt>https://repo.or.cz/w/gitstats.git/snapshot/ad7efbb9399e60cee6cb217c6b47e604174a8093.tar.gz</tt>, then you will run into issues because the checksum changes when downloading on the build system. This is not a problem on GitHub, GitLab and other decent services provides, they provide ''stable'' tarballs.

* abuild currently supports the following protocols for remote file retrieval:
** http
** https
** ftp



* abuild currently supports the following archive types/archive file extensions:
** .tar
** .tar.gz / .tgz
** .tar.bz2
** .tar.lz (only in Alpine >=3.7)
** .tar.lzma
** .tar.xz
** .zip

==== depends & makedepends ====

Depends are the actual running dependencies that a package would need when it is running. Makedepends are only needed when you are building a package. If you set a package in depends, you do not need to add it to makedepends as well. The best way to find out what the depends and makedepends of a package are is to [https://en.wikipedia.org/wiki/Rtfm RTFM].

No kidding, lots of important information can be found in the package INSTALL and README files (or the likes). Another good way is the run <code>./configure --help</code> from the source directory to see which options are needed for configure to finish without errors. If you do not yet have a source directory you can create one with the command:

{{Cmd|abuild unpack}}

Running <code>configure</code> will also show you how you can disable a specific option for this package. For instance, a good example is "--disable-nls" which will disable native language support and thus does not depend on gettext (libiconv, glib, ...).

Alpine likes to keep things small, so we try to disable as much as possible without losing too many features. The exact disable/enable options are decided by the package builder but please try to follow Alpine's design concept as much as possible.

An easy way of quickly finding out the build info for a package is to check Arch Linux (Alpine package management and build scripts are similar) or Gentoo Linux ebuilds (previous versions of Alpine were based on Gentoo).

* [https://gitweb.gentoo.org/repo/gentoo.git/tree/ Gentoo Ebuilds]
* [https://archlinux.org/packages/?q=search Arch Linux packages] [https://aur.archlinux.org/ Arch Linux User Repository]

==== license ====

The '''license''' tag must reflect the license of the source code. Please check the source tarball for COPYING, LICENSE, or other files with names that indicates that it contains licensing information. Beside the license file most developer include headers in the source code files with licensing details.

If the license is on the [https://spdx.org/licenses/ SPDX License List] or [https://spdx.org/licenses/exceptions-index.html SPDX License Exceptions], use the identifier specified by SPDX.

If a package has a special/custom license or is not listed as [https://opensource.org/licenses/alphabetical OSI approved], use the identifier "custom". If a package has an MIT license, that license has a copyright notice we need to reproduce. In these cases we additionally need to provide the license file with the release. Because we want to save space and don't like to have licenses all over our system we have decided to include the license in the doc subpackage. Please follow the following guidelines to add a proper license. Locate the license file inside the source package. Add the doc subpackage to the $subpackages variable as follows:

subpackages="$pkgname-doc"

Add a similar line to the following to your package() function, depending on the license description file:

{{Cmd|install -Dm644 COPYING "$pkgdir"/usr/share/licenses/$pkgname/COPYING}}

If you follow these steps then abuild will automatically add the license to the package-doc apk for you.

{{Warning|It is not acceptable to package software with "unknown" license! If you can't find the license of the source code, please contact the author and ask them to specify the license. }}

==== arch ====

The package architecture(s) to build for. This can be one of: ''x86, x86_64, all,'' or ''noarch'', where ''all'' means all architectures, and ''noarch'' means it's architecture-independent (e.g., a pure-python package).
{{Tip|To determine if your APKBUILD can use ''noarch'', build the package for your architecture and then run "scanelf -R pkg" from the directory that the APKBUILD resides in, in order to scan for ELF files in the ''./pkg'' directory. If you do NOT get output from this, then ''noarch'' can be used.}}

==== url ====

Website address for the program. This is useful later on when either finding documentation or other information about the package.

==== pkgdesc ====

A brief, one line, description of what the package does. Useful for the package management system. It should start with a capital letter and does '''not''' end with a period.

Here is an example from apk_info for the OpenSSH client package:

pkgdesc="Port of OpenBSD's free SSH release - client"

==== pkgver ====

Provide the release number of the package you are building.

==== pkgrel ====

The $pkgrel versioning is made so that if you change something in your APKBUILD file without changing the actual $pkgver, you can increment pkgrel so apk tools will detect it as an update. For instance, if you forget to add a dependency, you can add it afterward and you can +1 pkgver so apk finds this update and adds the missing dependency. When there's an upstream version change, we reset the pkgrel to 0.

==== pkgname ====

The base name of the package you are creating. For Freeswitch 1.0.6, you would use "freeswitch"

==== install ====

There are 6 different kinds of install scripts. Each script is called with the $pkgname.''<action>'' where ''<action>'' is one of the following:

<dl>
<dt>$pkgname.pre-install
<dd>This script is executed before package is installed. Typical use is when package needs a group and a user to be created. For example:
<pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
Note the ''exit 0'' at the end. If the script exits with failure (if the user already exist), the package will not be installed and <code>apk add</code> will exit with failure.

<dt>$pkgname.post-install
<dd>This script is executed after the package is installed.

<dt>$pkgname.pre-upgrade
<dd>Same as pre-install but is executed before upgrading/downgrading/reinstalling an already installed package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

<dt>$pkgname.post-upgrade
<dd>Same as post-install but is executed after upgrading/downgrading/reinstalling an already installed package.

<dt>$pkgname.pre-deinstall
<dd>This script is executed before uninstalling a package. If script exits with failure apk will not uninstall the package.

<dt>$pkgname.post-deinstall
<dd>This script is executed after a package have been uninstalled. For example, can be used to restore busybox links:
<pre>
#!/bin/sh
busybox --install -s
</pre>

</dl>

If the package has a pre-install and post-install script the APKBUILD should have the ''install'' variable defined:
<pre>
...
install="$pkgname.pre-install $pkgname.post-install"

...
</pre>

==== subpackages ====

$subpackages are made to split up the normal "make install" into separate packages. The most common subpackages we use are doc and dev. Because we like to keep our target system small we move documentation and development files (only needed when building packages) into separate packages. To use the specific program a user only need to install the base apk without package-doc or package-dev, but if he wants to read the manual he will need to install package-doc.

The easiest way to find out if you need to use -dev and -doc is to first build the package without these options set and wait until the build finishes. When its finished you should have a pkg directory which is the fake root directory. Inside this directory you will see the structure as how it would be installed in / on the target system.

To see if you need the -dev package you can run the following cmd:

{{Cmd|find pkg/usr/ -name '*.[acho]' -o -name '*.la'}}

If this returns any files you need to include the -dev package.

 To see if you need the -doc package you can run the following cmd:

{{Cmd|find pkg/usr/share -name doc -o -name man -o -name info -o -name html -o -name sgml -o -name licenses}}

If this returns any directories you need to include the -doc package.

===== Custom subpackages =====

Some software additionally has non-essential files that do not qualify as either documentation or development content. These files should be placed in their own, specialized subpackage(s). Some packages include large test suites which are only needed in specific circumstances or binaries which have depends which we prefer not to install. To handle those we create our own package/function. In the APKBUILD below the build() function we create another function:

test() {
mkdir -p "$subpkgdir"/usr
mv "$pkgdir"/usr/package-test "$subpkgdir"/usr/
# or amove usr/package-test
}

We also need to add the package info to $subpackages variable:

subpackages="$pkgname-doc $pkgname-dev $pkgname-test"

After we finish building the package you should see another apk called packagename-test.apk which includes the files which we moved to the $subpkgdir dir.

The above mentioned variables can also be used in our custom function. If we want for instance to build the test() function with perl support we would add:

depends="perl"
makedepends="perl-dev"

If we would install the base package it would not install perl, but if we install the package-test package it would.

==== Patches ====

Please make sure you always submit human readable patches. Ways to create them are:

directory compare:

{{Cmd|diff -Nurp original_directory new_directory > filename.patch}}

file compare:

{{Cmd|diff -up original.file new.file > filename.patch}}

If a patch contains a completely new file but not *.rej or *.orig file, you need to add -N option to diff, but you may need to add exclusions with <code>--exclude PATTERN</code> so that you do not inadvertently add files. You may need to manually delete unwanted files inside the patch file.

Because multiple patches can patch the same file, they can change the offsets required by subsequent patches. To make sure we always patch in a specific way, we should number the patches as follows:

10-patch1.patch 20-patch2.patch 30-patch3.patch

This way we are always sure that patch 1 is applied first, and if we want to add additional patches between them we can use appropriate indexes (e.g. 11, 12, 21, 22).

Add the names of the patch files to the ''source'' variable. If you haven't declared a custom ''prepare'' function, no further action is necessary. Otherwise, be sure to call ''default_prepare'' in your ''prepare'' function. For example:

prepare() {
default_prepare

# do your stuff
}

Note: Some older packages contain a ''for'' loop in the ''prepare'' function to apply patches. This is not needed anymore, as patches are handled by ''default_prepare''.

In Alpine >=3.4 you can define patch_args to supply the patch level. This only works if all the patches have the same patch level. If there are a lot of patches from different sources, there is a good chance that you may need to edit them, as discussed below.

To automatically patch the package (available only in Alpine >=3.4) if it uses a patch level (-pX) other than the default (-p1), you need to carefully modify the patch. First, you'll need a text editor that does not automatically convert between Windows and Unix new lines (or, disable this feature) so that it preserves the old code. The next thing you'll need to do is modify the paths on "+++" and "---" lines in the .patch file. You can begin the path with a/ and b/ like shown below. Next, you need to adjust the paths so that the relative base path is from inside $builddir. Anything to the left of $builddir, including $builddir itself, needs to be removed from the path. So, if $builddir is /home/USER/aports/community/chromium/src/chromium-65, you need to erase it on the "+++" and "---" lines. Inside the chromium-65 folder you can see a src folder that has 3rdparty as a descendant. If a patch originally has a deeper patch level, you may need to fill in the missing portion of the path. For example, use the <code>find . -name "Assertions.cpp"</code> command to find the full path to the file relative to the base.

{{Cat|example.patch|<nowiki>
Author: John Doe <johndoe@mail.com>
URL: http://.....
Summary: Fixes musl compatibility
----
--- a/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp.orig
+++ b/src/3rdparty/chromium/third_party/WebKit/Source/wtf/Assertions.cpp
@@ -142,7 +142,7 @@
};

FrameToNameScope::FrameToNameScope(void* addr) : m_name(0), m_cxaDemangled(0) {
-#if OS(MACOSX) || (OS(LINUX) && !defined(__UCLIBC__))
+#if OS(MACOSX) || (OS(LINUX) && defined(__GLIBC__))
Dl_info info;
if (!dladdr(addr, &info) || !info.dli_sname)
return;
</nowiki>}}

Portions of the patch may be outdated, removed completely as in the source code file completely removed, or moved or renamed files. You need to delete that section of the patch or find where that section of code changed and re-diff it.

It is good etiquette to give credit at the top and the location of where you originally found them with notes.

Excluding patches with global variable resembling patch_opts is not available on Alpine. To exclude patches you need to create your own custom prepare().

If you have a monolithic patch where there are a bunch of patches in one big patch, you could use filterdiff which is available in the patchutils package.

Just do something like:

<pre>
makedepends="patchutils"

prepare() {
...
cd "$builddir"
filterdiff -x '*drivers/video/logo*' "$srcdir"/original.patch > "$builddir"/modified.patch
patch -p1 -i "$builddir"/modified.patch
}
</pre>

You need to put the wildcard pattern in single quotes for it to work.

==== Configure options ====

Alpine has some default configure options we set by default. We use /usr for prefix to make sure everything is installed with /usr in front of it. If you notice that anything is installed in the wrong directory please run {{Cmd|./configure --help}} and see if you can set the correct location.

We are not covering the depend switches here we have discussed this already in the depend section.

==== Make options ====

If you notice weird problems when compiling or installing the package with make/make install you could try to disable [https://www.gnu.org/software/make/manual/make.html#Parallel parallel] building/installing. A normal make line would be:

{{Cmd|make}}

To disable parallel we use:

{{Cmd|make -j1}}

We can use the same for make install.

Because we do not want to install the package in our build environment but we want to install it in a fake root directory we need to tell 'make install' to use another destination directory instead of '/'. We do this by setting a variable when we execute make install as followed:

{{Cmd|make DESTDIR{{=}}"$pkgdir" install}}

Please note that some Makefiles do not support this variable and will always install software in '/'. To make sure you do not mess up your build system NEVER run your build system as root but always use a custom user and doas when needed. If by accident the Makefile does not support DESTDIR variable it will fail to install in our build system system directories.

==== builddir ====
If you used <tt>newapkbuild</tt> to create your APKBUILD file, you must specify the path to your unpacked sources. Inside the sections during the prepare/build/install process ''builddir'' is used. Most of the time a combination of ''$srcdir'' and ''$pkgname-$pkgver'' will work. When not, check the /src directory or the source tarball for the right string. Especially when you are working with automatically generated tarballs (like from github and gitorious), this needs to be adjusted.

<pre>
builddir="$srcdir"/$pkgname-$pkgver
</pre>

==== Additional files ====

If you want/need to install additional files not mentioned above you can use the following cmd (this is an example of a conf file):

{{Cmd|install -Dm644 doc/$pkgname.conf "$pkgdir"/etc/$pkgname.conf}}

== Build the package ==

If you did not already create the checksums as mentioned above you can do so now:

{{Cmd|cd $pkgname
abuild checksum}}

It's about time we build our package. Because a build system should never have all the package installed to prevent linking to packages we don't want it to link we use a abuild recursively with the '''-r''' switch. It will install all dependencies from your repository and builds it, afterwards it will uninstall all those depending packages again.

{{Cmd|abuild -r}}

See also [[Abuild_and_Helpers|Abuild and Helpers]].

== Testing the package locally ==

When it completes, your package will be found in a subfolder of <code>~/packages</code>. You may want to test it on your machine but only if the package is not a critical system package like musl or apk-tools package. To avoid borking your system (as in making it impossible to use <code>apk add</code> or to restore back the system and the compiler toolchain) for a critical system package, you should test on a chroot first before using it live.

The best way to test a package locally is to modify your <code>/etc/apk/repositories</code> so that it includes the indexes to your locally built packages - the directories that contain <code>ARCH/APKINDEX.tar.gz</code>. For example the <code>/etc/apk/repositories</code> below includes locally built packages in testing, community and main. To use this example change <code>USER</code> to your login name.

{{Cat|/etc/apk/repositories|/home/USER/packages/testing/
/home/USER/packages/main/
/home/USER/packages/community/
https://dl-cdn.alpinelinux.org/alpine/edge/main
https://dl-cdn.alpinelinux.org/alpine/edge/community
https://dl-cdn.alpinelinux.org/alpine/edge/testing
}}

If you prefer to test a package without changing any other configuration you can use the <code>-X, --repository</code> option to <code>apk</code>:

{{Cmd|doas apk add --repository /home/USER/packages/testing $pkgname}}

== Code review ==

To successfully have your package pass through code reviewers (as of Feb 18, 2018 are nmeum and jirutka on GitHub) and possible increased acceptance, the following conventions need to be followed:

# Custom global variables should be prefixed with underscore (_).
# Compact code as in merged commands, removed unused variables, removal of functions that do the same thing that are automatically handled by abuild.
# Versioning is done properly. For details see [[APKBUILD_Reference#pkgver]].
# Licensing is done properly. Remove unnecessary copying of licensing that is already OSI approved.
# Naming conventions rules for unofficial variables as in _gitrev is preferred over commit.
# Indent with tabs not spaces.
# Removal of explicit return 1. (They are still found the old APKBUILD files if you are learning but are now strongly discouraged.)
# Disabling check() requires either (1) a comment (#) stating next to options="!check" that there is no test suite/unit tests or (2) functioning working check() function.
# Explicit call to subpackages="$pkgname-doc" must be used instead of explicit gzip man page compression.
# Ideally, lines should be no more than 80 columns wide

Additionally, make sure to run the linter on your package:
{{Cmd|doas apk add atools
apkbuild-lint APKBUILD}}

For more information see [[Development using git:Quality assurance]] and [[Package_policies]].
Also check out [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/COMMITSTYLE.md?ref_type=heads aports/COMMITSTYLE.md] and [https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/CODINGSTYLE.md?ref_type=heads aports/CODINGSTYLE.md]

== Commit your work ==

After you successfully build your package and properly followed the conventions and requirements in the code review section, you can submit your APKBUILD to Alpine's git repository.

Update your git repo, before adding new files:

{{Cmd|cd $aportsdir
git pull}}

This should pull all the changes made by others into your local git repo.

When you think you are ready you can add your files to git:

NOTE: when using our Gitlab instance, you can create MR's for each package. Please squash all commits related to the same package into a single one per MR.

{{Cmd|cd $aportsdir
git add testing/$pkgdir (include any other files needed for the build; $pkgname.install...)
git commit}}

Use the following commit message template for new aports (without the comments):

{{Cat|template|testing/$pkgname: new aport # this will be the subject line
# a blank line
$url # project homepage
$pkgdesc # one line description}}

Or you could add the following and <code>chmod +x ports/.git/hooks/prepare-commit-msg</code> to automatically generate commit message which the default aports/.githooks/ does not:

{{Cat|aports/.git/hooks/prepare-commit-msg|<nowiki>#!/bin/sh
case "$2,$3" in
,|template,)
if git diff-index --diff-filter=A --name-only --cached HEAD \
| grep -q '/APKBUILD$'; then
meta() { git diff --staged | grep "^+$1" | sed 's/.*="\?//;s/"$//';}
printf 'testing/%s: new aport\n\n%s\n%s\n' "$(meta pkgname)" \
"$(meta url)" "$(meta pkgdesc)" "$(cat $1)" > "$1"
else
printf '%s\n\n%s' `git diff-index --name-only --cached HEAD \
| sed -n 's/\/APKBUILD$//p;q'` "$(cat $1)" > "$1"
fi;;
esac</nowiki>}}

Now your changes are only available locally in your repository.

Because you do not have push rights to the Alpine aports repository you need to create a merge request to [https://gitlab.alpinelinux.org/alpine/aports Alpine's GitLab instance].

Alternatively you can also create a diff (patch) of the changes you made and send this patch to the
[https://lists.alpinelinux.org/~alpine/aports alpine-aports mailinglist].

To create a diff patch:

{{Cmd|git format-patch HEAD^}}

or if you have sprunge, you can create a link to your patch for convenience

{{Cmd|git format-patch HEAD^ --stdout <nowiki>|</nowiki> sprunge}}

== Automated flagging of outdated ports ==
Consider adding your port to [https://release-monitoring.org/ Anitya], so it will be flagged as outdated
as soon as a new stable version is released by upstream.

== See Also ==
* [[APKBUILD Reference]]
* [[APKBUILD examples]]
* [[Development using git]]
* [[Development using git:Quality assurance]]

[[category: Package Manager]]

Release Notes for Alpine 3.15.0

2021-11-22T22:00:46Z

Omni: /* Support overlaytimpfs mount options */ frx tyop

== Important changes ==

=== New package signing keys ===

New signing keys have been generated for v3.15 ongoing. The key size has been increased from 2048 bits to 4096 bits. Make sure you have <code>alpine-keys-2.4-r0</code> or later before upgrading to 3.15 (or downgrading from edge).

=== MIPS64 discontinued ===

The build hardware we use for building the packages is broken and the architecture is EOL, so there is no new hardware available anymore. As a consequence, there will be no v3.15 release for mips64, and existing releases can no longer receive security updates, so continued use of this architecture is not recommended.

=== radvd no longer enables ipv6 forwarding ===

The radvd init script no longer enables ipv6 forwarding. To enable ipv6 forwarding (necessary for most networks), add <code>net.ipv6.conf.all.forwarding=1</code> to {{path|/etc/sysctl.conf}} or to a file in {{path|/etc/sysctl.d}}.

=== Move from sudo to doas ===

doas is the default temporary privilege escalation tool. You are advised to migrate from sudo to doas as 3.15 will be the last release to support sudo throughout its full lifecycle, in 3.16 sudo will be moved from main to community.

== New features and noteworthy new packages ==

=== Compressed kernel modules ===

Kernel modules are now compressed using gzip.

=== UEFI Secure Boot ===

Complete support for [[UEFI Secure Boot]] realized by package {{pkg|secureboot-hook}} and {{pkg|efi-mkkeys}}.

=== Support overlaytmpfs mount options ===

It is now possible to use tmpfs(5) mount options with <code> overlaytmpfsflags</code>, when using <code>overlaytmpfs</code>, see mkinitfs-bootparams(7). Also, <code>rootflags</code> and <code>rootfstype</code> options are now picked up for the underlying rootfs mount.

=== Support for out-of-tree kernel modules built from source ===

Alpine Kernel Module Support ({{pkg|akms}}) – support for building out-of-tree Linux kernel modules from source in an automated and organized fashion. It’s like DKMS, but designed specifically for Alpine Linux.

=== PostgreSQL multiple major versions ===

PostgreSQL packaging has been reworked to allow multiple major versions of PostgreSQL server to be installed side by side. This makes it possible to allow to upgrade PostgreSQL cluster from one major version to the next using <code>pg_upgrade</code> tool, and also to run an older major version of PostgreSQL on the latest version of Alpine Linux. The latest PostgreSQL version can be installed simply with <code>apk add postgresql</code> as before. If you need an older major version, install the specific package, e.g. {{pkg|postgresql13}}. You can switch between installed major versions using command <code>pg_versions</code>.

See [https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27275|MR #27275] for more information.

=== Rofi for Wayland ===

Rofi can now be used on Wayland desktops thanks to the fork {{pkg|rofi-wayland}}.

=== Encrypted Data Disk and System Disk modes ===

<code>setup-disk</code> ({{pkg|alpine-conf}}) now supports encrypted Data Disk and System Disk modes.

== Significant updates ==

=== 5.15 LTS kernels ===

linux-lts and linux-virt upgraded to 5.15

'''Note:''' If you are using ''ZFS'' and depend on symlinks under /dev/zvol/ some are sporadically not created during boot, this is known upstream by ''OpenZFS'' and we track the issue [https://gitlab.alpinelinux.org/alpine/aports/-/issues/13198 here].

=== Ruby 3.0.2 ===

Ruby has been upgraded to version 3.0.2.

Packages {{pkg|ruby-minitest}}, {{pkg|ruby-net-telnet}}, {{pkg|ruby-power_assert}}, {{pkg|ruby-sdbm}}, {{pkg|ruby-test-unit}}, {{pkg|ruby-xmlrpc}}, {{pkg|ruby-webrick}} has been moved from ruby aport to separate aports. Please note that since they don’t inherit the version from the ruby aport anymore, their new (real) version is ''lower'' than before!

Subpackages ruby-bigdecimal, ruby-etc, ruby-fiddle, ruby-gdbm, ruby-io-console, ruby-irb, and ruby-json have been merged into ruby-libs.

=== LLVM12 added ===

LLVM12 is now available.

=== KDE ===

KDE Plasma has been upgraded to version 5.23, and KDE Applications have been upgraded to 21.08.
Plasma Mobile Gear has been upgraded to 21.10.

=== Node.js ===

Node.js (LTS) has been upgraded to version 16.13.0. nodejs-current has been upgraded to 17.0.1.

=== PHP ===

PHP 7.4 started to phase out (1 year of security support left).
Transition to 8.0 is not finished yet as some app still require old version.

=== PostgreSQL 14 ===

PostgreSQL has been upgraded to version 14.0. Since this release, multiple major versions are provided, currently: 12, 13, and 14.

Support for Just-in-time compilation (JIT) has been moved into subpackage {{pkg|postgresql-jit}}.

{{pkg|libpq}} is now built without LDAP support which reduces number of installed dependencies. Note that this does ''not'' affect the LDAP support in PostgreSQL server, it’s preserved.

=== Mercurial ===

mercurial has been upgraded to 5.9.3

=== Dlang build tools (DMD, DUB, LDC) have been updated ===

Both compilers have been updated to frontend version v2.098.0 (LDC equivalent: v1.28.0).
Dub has been updated to v1.27.0.
LDC now always uses `--export-dynamic` so that code compiled without debug infos (`-g`) will still have the function name in its stack trace.

=== OpenJDK 17 added ===

The latest OpenJDK LTS version (17) has been added to this release and is available via the community repository.

=== GNOME 41 ===

Most GNOME packages have been upgraded to version 41.

=== Crystal ===

{{pkg|crystal}} has been upgraded to version 1.2.2.

=== Kea ===

{{pkg|kea}} has been upgraded to version 2.0.0.

=== OpenLDAP ===

{{pkg|openldap}} has been upgraded to version 2.6.0.

=== Rust ===

{{pkg|rust}} has been upgraded to version 1.56.1.

== Significant removals ==

=== QtWebKit was removed due to lack of upstream support ===

qt5-qtwebkit, kdewebkit, wkhtmltopdf, and py3-pdfkit have been removed due to known vulnerabilities and lack of upstream support for qtwebkit. Other programs have been adjusted to use qt5-qtwebengine where appropriate. The most direct replacement for wkhtmltopdf is weasyprint, which is available in the Alpine Linux community repository. puppeteer and pandoc are also options, depending on your needs. See [https://gitlab.alpinelinux.org/alpine/aports/-/issues/12888 #12888] for more information.

== Development-related changes ==

=== PostgreSQL ===

{{pkg|postgresql-dev}} has been split into {{pkg|libpq-dev}}, {{pkg|libecpg-dev}}, and <code>postgresql-dev</code> (this is ''provided'' by {{pkg|postgresql14-dev}}, {{pkg|postgresql13-dev}} etc.). Basically, only PostgreSQL extensions should use {{pkg|postgresql-dev}} in <code>makedepends</code>; all other aports should use {{pkg|libpq-dev}} and/or {{pkg|libecpg-dev}} (there are some exceptions though).

PostgreSQL extensions (typically packages with <code>postgresql-</code> prefix) should use {{pkg|postgresql-dev}} in <code>makedepends</code> – this will install the latest <code>postgresql<majorver>-dev</code> package, unless there’s a dependency on a specific postgresql version in the dependency graph (which shouldn’t be).

Each aport providing a PostgreSQL extension must explicitly depend on specific <code>postgresql<majorver></code> package, not <code>postgresql</code> provider. This should be solved by adding the following into the <code>package</code> function (!) in each aport that provides PostgreSQL extension:

<pre>
depends="postgresql$(pg_config --major-version)"
</pre>