Alpine Linux - User contributions [en]

Release Notes for Alpine 3.12.0

2020-05-08T11:57:22Z

Cogitri: Mention apk integration in GNOME Software

== aports ==

===== python2 no longer provides python and python-devel =====

python2 no longer provides python and python-devel, nothing does, it is now required that you explicitly depend on either python2 or python3, any new contributions that depend on python2 will be rejected summarily, and python2 is in the process of being **completely** removed

===== llvm 10.0.0 =====

llvm 10 is now the default in Alpine Linux.

[https://gitlab.alpinelinux.org/alpine/aports/commit/7a1323c27479fb967749c163f34483bc1196055d commit]

===== Initial support for DLang =====

We've added initial support for the D language with this release. We now have GDC, the D compiler frontend using GCC, available on all arches but ppc64le and LDC, a D compiler using the LLVM backend, on x86, x86_64 and aarch64. Most things are built against LDC, since it offers superior optimization and a vastly newer versions of the D runtime and standard library. These contain many important bug fixes (especially on aarch64) and contain features required by many D applications.

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

===== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret =====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

===== Preferring enchant2 over enchant =====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

===== Firefox is now in community =====

Firefox finally left testing and will be in community, supported for 6 months.

===== moonjit is now luajit =====

Our luajit package switched to the alive moonjit fork which has, among other things, s390x support and actual development.

This [https://git.alpinelinux.org/aports/commit/?id=af7f776d08cf7c12c3dd62347829fe33e66dceaa commit] switched luajit over to moonjit, the following [https://git.alpinelinux.org/aports/commit/?id=a7d057d98859940cc3347dba011957f99291b1fa commit] removes our **HUGE** 46k s390x support patch which is now handled by upstream.

===== Support for YubiKeys =====

yubikey-manager and yubikey-manager-qt have been added to the community repos for using and managing your yubikeys. Installing yubikey-manager and enabling the pcscd service should make yubikeys functional.

===== Support for apk in GNOME Software =====

GNOME Software now offers integration with apk, the Alpine Package Keeper, so desktop applications can be installed via a GUI.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

===== The "plain" buildtype for Meson and "None" buildtype for CMake are used now =====

We previously used the "release" or "debugoptimized" buildmode for Meson or "Release" or "RelWithDebInfo" for CMake. This caused Meson and CMake to ignore parts of our C{,XX}FLAGS, e.g. by setting -O2 or even -O3 instead of our default of -Os. We've changed to the "plain" buildtype and the "None" buildtype for CMake. This should result in smaller binaries since -Os is respected now. See [https://lists.alpinelinux.org/~alpine/devel/%3C2896c13070c508a49cbaa72c8fb7f34ea947358b.camel%40cogitri.dev%3E the respective mailing list post]

Release Notes for Alpine 3.12.0

2020-05-08T11:55:26Z

Cogitri: Reword D support notice

== aports ==

===== python2 no longer provides python and python-devel =====

python2 no longer provides python and python-devel, nothing does, it is now required that you explicitly depend on either python2 or python3, any new contributions that depend on python2 will be rejected summarily, and python2 is in the process of being **completely** removed

===== llvm 10.0.0 =====

llvm 10 is now the default in Alpine Linux.

[https://gitlab.alpinelinux.org/alpine/aports/commit/7a1323c27479fb967749c163f34483bc1196055d commit]

===== Initial support for DLang =====

We've added initial support for the D language with this release. We now have GDC, the D compiler frontend using GCC, available on all arches but ppc64le and LDC, a D compiler using the LLVM backend, on x86, x86_64 and aarch64. Most things are built against LDC, since it offers superior optimization and a vastly newer versions of the D runtime and standard library. These contain many important bug fixes (especially on aarch64) and contain features required by many D applications.

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

===== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret =====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

===== Preferring enchant2 over enchant =====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

===== Firefox is now in community =====

Firefox finally left testing and will be in community, supported for 6 months.

===== moonjit is now luajit =====

Our luajit package switched to the alive moonjit fork which has, among other things, s390x support and actual development.

This [https://git.alpinelinux.org/aports/commit/?id=af7f776d08cf7c12c3dd62347829fe33e66dceaa commit] switched luajit over to moonjit, the following [https://git.alpinelinux.org/aports/commit/?id=a7d057d98859940cc3347dba011957f99291b1fa commit] removes our **HUGE** 46k s390x support patch which is now handled by upstream.

===== Support for YubiKeys =====

yubikey-manager and yubikey-manager-qt have been added to the community repos for using and managing your yubikeys. Installing yubikey-manager and enabling the pcscd service should make yubikeys functional.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

===== The "plain" buildtype for Meson and "None" buildtype for CMake are used now =====

We previously used the "release" or "debugoptimized" buildmode for Meson or "Release" or "RelWithDebInfo" for CMake. This caused Meson and CMake to ignore parts of our C{,XX}FLAGS, e.g. by setting -O2 or even -O3 instead of our default of -Os. We've changed to the "plain" buildtype and the "None" buildtype for CMake. This should result in smaller binaries since -Os is respected now. See [https://lists.alpinelinux.org/~alpine/devel/%3C2896c13070c508a49cbaa72c8fb7f34ea947358b.camel%40cogitri.dev%3E the respective mailing list post]

GNOME

2020-04-28T12:03:00Z

Cogitri: Mention that gdm needs a user available

= Initial setup =
Start by booting up Alpine (see [[Installation|these]] instructions on how to do that)<BR>
When you Alpine is up and running, do the initial setup.
{{Cmd|# setup-alpine}}
{{Cmd|# setup-xorg-base}}

= Installing packages =
Install basic desktop system and gnome packages. As of right now, these are in the testing repo.<BR>
This might take a few minutes depending on your network speed.
{{Cmd|# apk add gnome}}
<BR>

If you want to you can also install additional GNOME apps for a more complete GNOME experience with:<BR>
{{Cmd|# apk add gnome-apps}}
<BR>

== Setting up udev ==
You'll have to enable udev in order for GNOME to function properly.

{{Cmd|# apk add udev
# /etc/init.d/udev start && /etc/init.d/udev-trigger start && /etc/init.d/udev-settle start
# rc-update add udev sysinit
# rc-update add udev-trigger sysinit
# rc-update add udev-settle sysinit
}}

== Setting up Xorg ==
Even when using GNOME Wayland you'll still need a setup Xorg for XWayland.

=== Video packages ===

{{cmd|$ apk search xf86-video}}

Then install the driver matching to your card, e.g. if you have an Intel iGPU:

{{cmd|# apk add xf86-video-intel}}

=== Input packages ===

Usually libinput is the best choice, as it's integrated best with GNOME and offers advanced functionality (e.g. palm rejection for touchpads).

{{cmd|# apk add xf86-input-libinput}}

= Starting your desktop =
Start GDM and login with your user. You need a user other than root for this to succeed, since GDM will refuse starting if no user accounts (meaning accounts with a UID >= 1000) are available.
{{Cmd|rc-service gdm start}}

Once you have verified that it actually works you can make gdm start up at boot:
{{Cmd|rc-update add gdm}}

= Troubleshooting =
If you are unable to login, check /var/log/gdm/greeter.log, there may be output there from X to indicate failed modules, etc.

If logging in from GDM returns to logging screen, try {{cmd|# apk add bash}} (bug report: #10953 sorry cannot link yet)

[[Category:Desktop]]

Alpine Linux:Mailing lists

2020-03-22T12:04:44Z

Cogitri: Remove removed MLs, fix links to existing ones.

'''[http://lists.alpinelinux.org/ Mailing List Archives]''' A Web listing of the mailing list archives in a searchable format. Since the mailing list is hosted on Alpine Linux, we are using [http://mlmmj.org/ mlmmj] for the mailing list, [http://www.hypermail-project.org/ hypermail] for translation into html and [http://swish-e.org/ swish-e] for search.

(Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.)

See also https://alpinelinux.org/community/.

== Subscribing ==
Note: "<mailing-list>" can be any of the listed mailing lists below or at [http://lists.alpinelinux.org/ http://lists.alpinelinux.org/]
# Send an email to <mailing-list>+subscribe@lists.alpinelinux.org
# Wait for a reply from the <mailing-list>+help@lists.alpinelinux.org asking you to confirm your email address
# Send a reply to the given "Reply-To" address
# Receive a subscription confirmation from <mailing-list>+help@lists.alpinelinux.org with the subject line Welcome to <mailing-list>@lists.alpinelinux.org

There's also a button for subscribing in each mailing list's web UI, e.g. on [https://lists.alpinelinux.org/~alpine/users ~alpine/users] which will open your mail client for you.

== alpine-announce ==
Low-volume mailing list for release announcements (new versions of Alpine).
;Archives
:https://lists.alpinelinux.org/~alpine/announce
;Subscribe
:[mailto:~alpine/announce+subscribe@lists.alpinelinux.org ~alpine/announce+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/announce+unsubscribe@lists.alpinelinux.org ~alpine/announce+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/announce+help@lists.alpinelinux.org ~alpine/announce+help@lists.alpinelinux.org]

== alpine-users ==
Mailing list for general user support.
;Archives
:http://lists.alpinelinux.org/~alpine/users
;Subscribe
:[mailto:~alpine/users+subscribe@lists.alpinelinux.org ~alpine/users+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/users+unsubscribe@lists.alpinelinux.org ~alpine/users+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/users+help@lists.alpinelinux.org ~alpine/users+help@lists.alpinelinux.org]

== alpine-devel ==
Mailing list for Alpine Linux development.
;Archives
:http://lists.alpinelinux.org/~alpine/devel
;Subscribe
:[mailto:~alpine/devel+subscribe@lists.alpinelinux.org ~alpine/devel+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/devel+unsubscribe@lists.alpinelinux.org ~alpine/devel+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/devel+help@lists.alpinelinux.org ~alpine/devel+help@lists.alpinelinux.org]

== Other mailing lists ==

* [https://lists.alpinelinux.org/~alpine/aports alpine-aports]
:Active mailing list with patches for packages (proposed for incorporating into aports package pools).

* [https://lists.alpinelinux.org/~alpine/infra alpine-infra]
:Active mailing list discussing Alpine web infrastructure.

* [https://lists.alpinelinux.org/~alpine/apk-tools apk-tools]
:Active mailing lis discussing the Alpine Package Keeper (APK)

</div>

Alpine Linux:Mailing lists

2020-03-22T12:02:53Z

Cogitri: Fix links for new ML

'''[http://lists.alpinelinux.org/ Mailing List Archives]''' A Web listing of the mailing list archives in a searchable format. Since the mailing list is hosted on Alpine Linux, we are using [http://mlmmj.org/ mlmmj] for the mailing list, [http://www.hypermail-project.org/ hypermail] for translation into html and [http://swish-e.org/ swish-e] for search.

(Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.)

See also https://alpinelinux.org/community/.

== Subscribing ==
Note: "<mailing-list>" can be any of the listed mailing lists below or at [http://lists.alpinelinux.org/ http://lists.alpinelinux.org/]
# Send an email to <mailing-list>+subscribe@lists.alpinelinux.org
# Wait for a reply from the <mailing-list>+help@lists.alpinelinux.org asking you to confirm your email address
# Send a reply to the given "Reply-To" address
# Receive a subscription confirmation from <mailing-list>+help@lists.alpinelinux.org with the subject line Welcome to <mailing-list>@lists.alpinelinux.org

There's also a button for subscribing in each mailing list's web UI, e.g. on [https://lists.alpinelinux.org/~alpine/users ~alpine/users] which will open your mail client for you.

== alpine-announce ==
Low-volume mailing list for release announcements (new versions of Alpine).
;Archives
:https://lists.alpinelinux.org/~alpine/announce
;Subscribe
:[mailto:~alpine/announce+subscribe@lists.alpinelinux.org ~alpine/announce+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/announce+unsubscribe@lists.alpinelinux.org ~alpine/announce+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/announce+help@lists.alpinelinux.org ~alpine/announce+help@lists.alpinelinux.org]

== alpine-users ==
Mailing list for general user support.
;Archives
:http://lists.alpinelinux.org/~alpine/users
;Subscribe
:[mailto:~alpine/users+subscribe@lists.alpinelinux.org ~alpine/users+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/users+unsubscribe@lists.alpinelinux.org ~alpine/users+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/users+help@lists.alpinelinux.org ~alpine/users+help@lists.alpinelinux.org]

== alpine-devel ==
Mailing list for Alpine Linux development.
;Archives
:http://lists.alpinelinux.org/~alpine/devel
;Subscribe
:[mailto:~alpine/devel+subscribe@lists.alpinelinux.org ~alpine/devel+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/devel+unsubscribe@lists.alpinelinux.org ~alpine/devel+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/devel+help@lists.alpinelinux.org ~alpine/devel+help@lists.alpinelinux.org]

== Other mailing lists ==

* [http://lists.alpinelinux.org/alpine-aports/ alpine-aports]
:Active mailing list with patches for packages (proposed for incorporating into aports package pools).

* [http://lists.alpinelinux.org/alpine-infra/ alpine-infra]
:Active mailing list discussing Alpine web infrastructure.

<div style="color:gray">

* [http://lists.alpinelinux.org/alpine-security/ alpine-security]
:Inactive mailing list.

* [http://lists.alpinelinux.org/alpine-acf/ alpine-acf]
:Inactive mailing list (only 3 messages since April 2013) about Alpine Configuration Framework.

* [http://lists.alpinelinux.org/alpine-build/ alpine-build]
:Inactive mailing list.

</div>

Alpine Linux:Mailing lists

2020-03-22T12:02:12Z

Cogitri: Fix links for new ML

'''[http://lists.alpinelinux.org/ Mailing List Archives]''' A Web listing of the mailing list archives in a searchable format. Since the mailing list is hosted on Alpine Linux, we are using [http://mlmmj.org/ mlmmj] for the mailing list, [http://www.hypermail-project.org/ hypermail] for translation into html and [http://swish-e.org/ swish-e] for search.

(Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.)

See also https://alpinelinux.org/community/.

== Subscribing ==
Note: "<mailing-list>" can be any of the listed mailing lists below or at [http://lists.alpinelinux.org/ http://lists.alpinelinux.org/]
# Send an email to <mailing-list>+subscribe@lists.alpinelinux.org
# Wait for a reply from the <mailing-list>+help@lists.alpinelinux.org asking you to confirm your email address
# Send a reply to the given "Reply-To" address
# Receive a subscription confirmation from <mailing-list>+help@lists.alpinelinux.org with the subject line Welcome to <mailing-list>@lists.alpinelinux.org

There's also a button for subscribing in each mailing list's web UI, e.g. on [https://lists.alpinelinux.org/~alpine/users ~alpine/users] which will open your mail client for you.

== alpine-announce ==
Low-volume mailing list for release announcements (new versions of Alpine).
;Archives
:https://lists.alpinelinux.org/~alpine/announce
;Subscribe
:[mailto:~alpine/announce+subscribe@lists.alpinelinux.org ~alpine/announce+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/announce+unsubscribe@lists.alpinelinux.org ~alpine/announce+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/announce+help@lists.alpinelinux.org ~alpine/announce+help@lists.alpinelinux.org]

== alpine-users ==
Mailing list for general user support.
;Archives
:http://lists.alpinelinux.org/~alpine/users
;Subscribe
:[mailto:~alpine/users+subscribe@lists.alpinelinux.org ~alpine/users+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/users+unsubscribe@lists.alpinelinux.org ~alpine/users+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/users+help@lists.alpinelinux.org ~alpine/users+help@lists.alpinelinux.org]

== alpine-devel ==
Mailing list for Alpine Linux development.
;Archives
:http://lists.alpinelinux.org/alpine-devel/
;Subscribe
:[mailto:alpine-devel+subscribe@lists.alpinelinux.org alpine-devel+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-devel+unsubscribe@lists.alpinelinux.org alpine-devel+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-devel+help@lists.alpinelinux.org alpine-devel+help@lists.alpinelinux.org]

== Other mailing lists ==

* [http://lists.alpinelinux.org/alpine-aports/ alpine-aports]
:Active mailing list with patches for packages (proposed for incorporating into aports package pools).

* [http://lists.alpinelinux.org/alpine-infra/ alpine-infra]
:Active mailing list discussing Alpine web infrastructure.

<div style="color:gray">

* [http://lists.alpinelinux.org/alpine-security/ alpine-security]
:Inactive mailing list.

* [http://lists.alpinelinux.org/alpine-acf/ alpine-acf]
:Inactive mailing list (only 3 messages since April 2013) about Alpine Configuration Framework.

* [http://lists.alpinelinux.org/alpine-build/ alpine-build]
:Inactive mailing list.

</div>

Alpine Linux:Mailing lists

2020-03-22T12:01:17Z

Cogitri: Fix links for new ML

'''[http://lists.alpinelinux.org/ Mailing List Archives]''' A Web listing of the mailing list archives in a searchable format. Since the mailing list is hosted on Alpine Linux, we are using [http://mlmmj.org/ mlmmj] for the mailing list, [http://www.hypermail-project.org/ hypermail] for translation into html and [http://swish-e.org/ swish-e] for search.

(Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.)

See also https://alpinelinux.org/community/.

== Subscribing ==
Note: "<mailing-list>" can be any of the listed mailing lists below or at [http://lists.alpinelinux.org/ http://lists.alpinelinux.org/]
# Send an email to <mailing-list>+subscribe@lists.alpinelinux.org
# Wait for a reply from the <mailing-list>+help@lists.alpinelinux.org asking you to confirm your email address
# Send a reply to the given "Reply-To" address
# Receive a subscription confirmation from <mailing-list>+help@lists.alpinelinux.org with the subject line Welcome to <mailing-list>@lists.alpinelinux.org

There's also a button for subscribing in each mailing list's web UI, e.g. on [https://lists.alpinelinux.org/~alpine/users ~alpine/users] which will open your mail client for you.

== alpine-announce ==
Low-volume mailing list for release announcements (new versions of Alpine).
;Archives
:https://lists.alpinelinux.org/~alpine/announce
;Subscribe
:[mailto:~alpine/announce+subscribe@lists.alpinelinux.org ~alpine/announce+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:~alpine/announce+unsubscribe@lists.alpinelinux.org ~alpine/announce+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:~alpine/announce+help@lists.alpinelinux.org ~alpine/announce+help@lists.alpinelinux.org]

== alpine-user ==
Mailing list for general user support.
;Archives
:http://lists.alpinelinux.org/alpine-user/
;Subscribe
:[mailto:alpine-user+subscribe@lists.alpinelinux.org alpine-user+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-user+unsubscribe@lists.alpinelinux.org alpine-user+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-user+help@lists.alpinelinux.org alpine-user+help@lists.alpinelinux.org]

== alpine-devel ==
Mailing list for Alpine Linux development.
;Archives
:http://lists.alpinelinux.org/alpine-devel/
;Subscribe
:[mailto:alpine-devel+subscribe@lists.alpinelinux.org alpine-devel+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-devel+unsubscribe@lists.alpinelinux.org alpine-devel+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-devel+help@lists.alpinelinux.org alpine-devel+help@lists.alpinelinux.org]

== Other mailing lists ==

* [http://lists.alpinelinux.org/alpine-aports/ alpine-aports]
:Active mailing list with patches for packages (proposed for incorporating into aports package pools).

* [http://lists.alpinelinux.org/alpine-infra/ alpine-infra]
:Active mailing list discussing Alpine web infrastructure.

<div style="color:gray">

* [http://lists.alpinelinux.org/alpine-security/ alpine-security]
:Inactive mailing list.

* [http://lists.alpinelinux.org/alpine-acf/ alpine-acf]
:Inactive mailing list (only 3 messages since April 2013) about Alpine Configuration Framework.

* [http://lists.alpinelinux.org/alpine-build/ alpine-build]
:Inactive mailing list.

</div>

Alpine Linux:Mailing lists

2020-03-22T11:57:26Z

Cogitri: /* Subscribing */

'''[http://lists.alpinelinux.org/ Mailing List Archives]''' A Web listing of the mailing list archives in a searchable format. Since the mailing list is hosted on Alpine Linux, we are using [http://mlmmj.org/ mlmmj] for the mailing list, [http://www.hypermail-project.org/ hypermail] for translation into html and [http://swish-e.org/ swish-e] for search.

(Please don't [http://en.wikipedia.org/wiki/Top-posting top-post] to the list as it makes the archives more or less useless.)

See also https://alpinelinux.org/community/.

== Subscribing ==
Note: "<mailing-list>" can be any of the listed mailing lists below or at [http://lists.alpinelinux.org/ http://lists.alpinelinux.org/]
# Send an email to <mailing-list>+subscribe@lists.alpinelinux.org
# Wait for a reply from the <mailing-list>+help@lists.alpinelinux.org asking you to confirm your email address
# Send a reply to the given "Reply-To" address
# Receive a subscription confirmation from <mailing-list>+help@lists.alpinelinux.org with the subject line Welcome to <mailing-list>@lists.alpinelinux.org

There's also a button for subscribing in each mailing list's web UI, e.g. on [https://lists.alpinelinux.org/~alpine/users ~alpine/users] which will open your mail client for you.

== alpine-announce ==
Low-volume mailing list for release announcements (new versions of Alpine).
;Archives
:http://lists.alpinelinux.org/alpine-announce/
;Subscribe
:[mailto:alpine-announce+subscribe@lists.alpinelinux.org alpine-announce+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-announce+unsubscribe@lists.alpinelinux.org alpine-announce+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-announce+help@lists.alpinelinux.org alpine-announce+help@lists.alpinelinux.org]

== alpine-user ==
Mailing list for general user support.
;Archives
:http://lists.alpinelinux.org/alpine-user/
;Subscribe
:[mailto:alpine-user+subscribe@lists.alpinelinux.org alpine-user+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-user+unsubscribe@lists.alpinelinux.org alpine-user+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-user+help@lists.alpinelinux.org alpine-user+help@lists.alpinelinux.org]

== alpine-devel ==
Mailing list for Alpine Linux development.
;Archives
:http://lists.alpinelinux.org/alpine-devel/
;Subscribe
:[mailto:alpine-devel+subscribe@lists.alpinelinux.org alpine-devel+subscribe@lists.alpinelinux.org]
;Unsubscribe
:[mailto:alpine-devel+unsubscribe@lists.alpinelinux.org alpine-devel+unsubscribe@lists.alpinelinux.org]
;Help
:[mailto:alpine-devel+help@lists.alpinelinux.org alpine-devel+help@lists.alpinelinux.org]

== Other mailing lists ==

* [http://lists.alpinelinux.org/alpine-aports/ alpine-aports]
:Active mailing list with patches for packages (proposed for incorporating into aports package pools).

* [http://lists.alpinelinux.org/alpine-infra/ alpine-infra]
:Active mailing list discussing Alpine web infrastructure.

<div style="color:gray">

* [http://lists.alpinelinux.org/alpine-security/ alpine-security]
:Inactive mailing list.

* [http://lists.alpinelinux.org/alpine-acf/ alpine-acf]
:Inactive mailing list (only 3 messages since April 2013) about Alpine Configuration Framework.

* [http://lists.alpinelinux.org/alpine-build/ alpine-build]
:Inactive mailing list.

</div>

Creating patches

2020-03-07T11:51:46Z

Cogitri: Mention amending changes on Gitlab and rebasing

New aports should normally go into testing repository. After a reasonable testing period if the package is complete (e.g. it has an init script, it has a working and sane default configuration, etc.) and it has a maintainer it can be moved into community repository. Main repository is for packages that are either core of the linux system or are dependencies of other core packages. A package in main cannot have a dependency in community or testing and a package in community cannot have a dependency on packages in testing.

There are currently two ways to contribute to propose changes, via Gitlab and via the mailing list.

== Submitting patches via Gitlab ==

=== Setup ===

To submit patches on [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance] you first have to create an account for it [https://gitlab.alpinelinux.org/users/sign_in here]. It's recommended to set a SSH key now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that.

=== Creating a merge request ===

Now that you're all setup you have to fork the repository you want to contribute to, for example if you want to open a merge request for aports you would have to fork [https://gitlab.alpinelinux.org/alpine/aports alpine/aports], see the [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that. Other repositories belonging to Alpine Linux live in the [https://gitlab.alpinelinux.org/alpine Alpine organisation].
After forking you can clone the repository like so:

{{Cmd|git clone git@gitlab.alpinelinux.org:$USER/$REPO.git}}

Replace $USER with the nickname of your Gitlab account and $REPO with the repository you want to work on. Now you can change to another branch (e.g. the name of the package you want to edit) with:

{{Cmd|git checkout -b pkgname}}

Do your changes now and then push with:

{{Cmd|git push -u origin $branchname }}

Gitlab will print an URL to create a merge request in your terminal.

=== Amending changes to a merge request ===

If reviewers requested changes or if you noticed that something should be changed about your merge request's change you can simply amend your changes to the right commit and force push. So if you want to change the commit at the tip of your branch you can simply do:

{{Cmd|git commit --amend}}

If you want to change a commit that's not at the tip of your branch you can do:

{{Cmd|git commit --fixup $SHA1_OF_COMMIT_YOU_WANT_TO_FIX}}

Afterwards you have to force-push in order to update your merge request:

{{Cmd|git push -f origin}}

=== Rebasing against Alpine Linux's master ===

It's best to always stay up-to-date with the state of the upstream Alpine Linux repository to ensure that no merge conflicts happen later on. To do that you first have to add a new git remote which points to the upstream repository (instead of your fork):

{{Cmd|git remote add upstream https://gitlab.alpinelinux.org/alpine/$REPO}}

Now you can fetch all changes with:

{{Cmd|git fetch --all}}

And then you can rebase with:

{{Cmd|git rebase}}

== Submitting patches via the mailing list ==

Patches should be created with git and submitted to [mailto:alpine-aports@lists.alpinelinux.org alpine-aports] mailing list with ''git send-email'' (which needs the ''git-email'' Alpine package).

=== Only the last commit with 'git send-email' ===

To submit the last commit as a patch to [mailto:alpine-aports@lists.alpinelinux.org alpine-aports] mailing list:

{{Cmd|git send-email --to alpine-aports@lists.alpinelinux.org -1}}

{{Tip|You save the To-address (does not require '--to alpine-aports@lists.alpinelinux.org') in the git config with: {{Cmd|git config sendemail.to alpine-aports@lists.alpinelinux.org}}}}

The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows

<pre>
testing/packagename: new aport <- header

https://example.com/packagename <- body
wonderful package
</pre>

{{Note|The git send-email command is provided by the '''git-email''' package ('''git-perl''' in v2.7 and older). }}

See [[Development using git#Email_configuration]] on how configure SMTP Auth.

=== Multiple commits with 'git send-email' ===

If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.

{{Cmd|<nowiki>rm -Rf patches
mkdir patches
git format-patch -o patches origin
git send-email patches --compose --no-chain-reply-to --to alpine-aports@lists.alpinelinux.org</nowiki>}}

You can also format patches for the last x number of commits with:
{{Cmd|<nowiki>git format-patch -x -o patches</nowiki>}}

This will produce the patches for each local commit in the directory "patches" and send them.
Use '''--no-chain-reply-to''' to avoid that each patch is sent as a ''reply'' to the previous patch.

Eg.
* [PATCH 0/m]
** [PATCH 1/m]
*** [PATCH 2/m]
**** ...

With the option '''--no-chain-reply-to''' the patches will be sent as a reply to the first email, the ''cover letter'' (the [PATCH 0/m]) and will make the email thread nicer.
Like this:
* [PATCH 0/m]
** [PATCH 1/m]
** [PATCH 2/m]
** ..

=== Resend an updated patch ===
Sometimes patches are rejected due to minor issues in the patch. Do not send an incremental patch on top of your initial, bad, patch. Instead, recreate the patch and send a new, fixed version of your patch. (use ''git commit --amend'' to edit a local commit).

When you sending a second version of the patch use '''--subject-prefix "PATCH v2"''' to indicate that this is a new version of a previously sent patch. You may also use '''--in-reply-to <message-id>''' where <message-id> the the id of email requesting the resend.

You should also write a note on the what was changed. Use '''--annotate''' for this and write the comment under the three dashes "---" so the note is not included in the commit message. For example:
<pre>
...
Subject: [PATCH v2] testing/mypackage: new aport

https://example.com
Example package
---
Changes v1 -> v2:
- removed depends
- added zlib-dev to makedepends

testing/mypackage/APKBUILD | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 testing/mypackage/APKBUILD
...
</pre>

Note that the notes that are below the "---" will not be included in the commit message.
[[Category:Development]]
[[Category:Git]]

=== See also ===
* [[Patch Workflow]]

Creating patches

2020-03-07T11:21:40Z

Cogitri: Mention Gitlab

New aports should normally go into testing repository. After a reasonable testing period if the package is complete (e.g. it has an init script, it has a working and sane default configuration, etc.) and it has a maintainer it can be moved into community repository. Main repository is for packages that are either core of the linux system or are dependencies of other core packages. A package in main cannot have a dependency in community or testing and a package in community cannot have a dependency on packages in testing.

There are currently two ways to contribute to propose changes, via Gitlab and via the mailing list.

== Submitting patches via Gitlab ==

To submit patches on [https://gitlab.alpinelinux.org Alpine Linux' Gitlab instance] you first have to create an account for it [https://gitlab.alpinelinux.org/users/sign_in here]. It's recommended to set a SSH now, refer to the [https://docs.gitlab.com/ee/ssh/ Gitlab docs] for how to do that. Afterwards, you have to fork the repository you want to contribute to, for example if you want to open a merge request for aports you would have to fork [https://gitlab.alpinelinux.org/alpine/aports alpine/aports], see the [https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork Gitlab docs] if you're having problems with that. Other repositories belonging to Alpine Linux live in the [https://gitlab.alpinelinux.org/alpine Alpine organisation].
After forking you can clone the repository like so:

{{Cmd|git clone git@gitlab.alpinelinux.org:$USER/$REPO.git}}

Replace $USER with the nickname of your Gitlab account and $REPO with the repository you want to work on. Now you can change to another branch (e.g. the name of the package you want to edit) with:

{{Cmd|git checkout -b pkgname}}

Do your changes now and then push with:

{{Cmd|git push -u origin $branchname }}

Gitlab will print an URL to create a merge request in your terminal.

== Submitting patches via the mailing list ==

Patches should be created with git and submitted to [mailto:alpine-aports@lists.alpinelinux.org alpine-aports] mailing list with ''git send-email'' (which needs the ''git-email'' Alpine package).

=== Only the last commit with 'git send-email' ===

To submit the last commit as a patch to [mailto:alpine-aports@lists.alpinelinux.org alpine-aports] mailing list:

{{Cmd|git send-email --to alpine-aports@lists.alpinelinux.org -1}}

{{Tip|You save the To-address (does not require '--to alpine-aports@lists.alpinelinux.org') in the git config with: {{Cmd|git config sendemail.to alpine-aports@lists.alpinelinux.org}}}}

The first line in commit message will be ''subject'' and the long description (separated with empty line) will be the body in the email. The example below shows

<pre>
testing/packagename: new aport <- header

https://example.com/packagename <- body
wonderful package
</pre>

{{Note|The git send-email command is provided by the '''git-email''' package ('''git-perl''' in v2.7 and older). }}

See [[Development using git#Email_configuration]] on how configure SMTP Auth.

=== Multiple commits with 'git send-email' ===

If you have many commits you can create a directory with patches and send them with <tt>git send-email</tt>.

{{Cmd|<nowiki>rm -Rf patches
mkdir patches
git format-patch -o patches origin
git send-email patches --compose --no-chain-reply-to --to alpine-aports@lists.alpinelinux.org</nowiki>}}

You can also format patches for the last x number of commits with:
{{Cmd|<nowiki>git format-patch -x -o patches</nowiki>}}

This will produce the patches for each local commit in the directory "patches" and send them.
Use '''--no-chain-reply-to''' to avoid that each patch is sent as a ''reply'' to the previous patch.

Eg.
* [PATCH 0/m]
** [PATCH 1/m]
*** [PATCH 2/m]
**** ...

With the option '''--no-chain-reply-to''' the patches will be sent as a reply to the first email, the ''cover letter'' (the [PATCH 0/m]) and will make the email thread nicer.
Like this:
* [PATCH 0/m]
** [PATCH 1/m]
** [PATCH 2/m]
** ..

=== Resend an updated patch ===
Sometimes patches are rejected due to minor issues in the patch. Do not send an incremental patch on top of your initial, bad, patch. Instead, recreate the patch and send a new, fixed version of your patch. (use ''git commit --amend'' to edit a local commit).

When you sending a second version of the patch use '''--subject-prefix "PATCH v2"''' to indicate that this is a new version of a previously sent patch. You may also use '''--in-reply-to <message-id>''' where <message-id> the the id of email requesting the resend.

You should also write a note on the what was changed. Use '''--annotate''' for this and write the comment under the three dashes "---" so the note is not included in the commit message. For example:
<pre>
...
Subject: [PATCH v2] testing/mypackage: new aport

https://example.com
Example package
---
Changes v1 -> v2:
- removed depends
- added zlib-dev to makedepends

testing/mypackage/APKBUILD | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 testing/mypackage/APKBUILD
...
</pre>

Note that the notes that are below the "---" will not be included in the commit message.
[[Category:Development]]
[[Category:Git]]

=== See also ===
* [[Patch Workflow]]

Release Notes for Alpine 3.12.0

2020-03-02T09:53:06Z

Cogitri: Set a name for the ML link

== aports ==

===== Initial support for DLang =====

We've added initial support for the D language with this release. We now have GDC, the D compiler frontend using GCC, available on all arches but ppc64le and LDC, a D compiler using the LLVM backend, on x86_64. Most things are built against ldc and as such only available on x86_64 right now due to GDC shipping a rather outdated version of the Phobos, the D standard library.

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

===== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret =====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

===== Preferring enchant2 over enchant =====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

===== Firefox is now in community =====

Firefox finally left testing and will be in community, supported for 6 months.

===== moonjit is now luajit =====

Our luajit package switched to the alive moonjit fork which has, among other things, s390x support and actual development.

This [https://git.alpinelinux.org/aports/commit/?id=af7f776d08cf7c12c3dd62347829fe33e66dceaa commit] switched luajit over to moonjit, the following [https://git.alpinelinux.org/aports/commit/?id=a7d057d98859940cc3347dba011957f99291b1fa commit] removes our **HUGE** 46k s390x support patch which is now handled by upstream.

===== Support for YubiKeys =====

yubikey-manager and yubikey-manager-qt have been added to the community repos for using and managing your yubikeys. Installing yubikey-manager and enabling the pcscd service should make yubikeys functional.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

===== The "plain" buildtype for Meson and "None" buildtype for CMake are used now =====

We previously used the "release" or "debugoptimized" buildmode for Meson or "Release" or "RelWithDebInfo" for CMake. This caused Meson and CMake to ignore parts of our C{,XX}FLAGS, e.g. by setting -O2 or even -O3 instead of our default of -Os. We've changed to the "plain" buildtype and the "None" buildtype for CMake. This should result in smaller binaries since -Os is respected now. See [https://lists.alpinelinux.org/~alpine/devel/%3C2896c13070c508a49cbaa72c8fb7f34ea947358b.camel%40cogitri.dev%3E the respective mailing list post]

Release Notes for Alpine 3.12.0

2020-03-02T09:51:54Z

Cogitri: Mention the "plain"/"None" buildtype change.

== aports ==

===== Initial support for DLang =====

We've added initial support for the D language with this release. We now have GDC, the D compiler frontend using GCC, available on all arches but ppc64le and LDC, a D compiler using the LLVM backend, on x86_64. Most things are built against ldc and as such only available on x86_64 right now due to GDC shipping a rather outdated version of the Phobos, the D standard library.

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

===== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret =====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

===== Preferring enchant2 over enchant =====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

===== Firefox is now in community =====

Firefox finally left testing and will be in community, supported for 6 months.

===== moonjit is now luajit =====

Our luajit package switched to the alive moonjit fork which has, among other things, s390x support and actual development.

This [https://git.alpinelinux.org/aports/commit/?id=af7f776d08cf7c12c3dd62347829fe33e66dceaa commit] switched luajit over to moonjit, the following [https://git.alpinelinux.org/aports/commit/?id=a7d057d98859940cc3347dba011957f99291b1fa commit] removes our **HUGE** 46k s390x support patch which is now handled by upstream.

===== Support for YubiKeys =====

yubikey-manager and yubikey-manager-qt have been added to the community repos for using and managing your yubikeys. Installing yubikey-manager and enabling the pcscd service should make yubikeys functional.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

===== The "plain" buildtype for Meson and "None" buildtype for CMake are used now =====

We previously used the "release" or "debugoptimized" buildmode for Meson or "Release" or "RelWithDebInfo" for CMake. This caused Meson and CMake to ignore parts of our C{,XX}FLAGS, e.g. by setting -O2 or even -O3 instead of our default of -Os. We've changed to the "plain" buildtype and the "None" buildtype for CMake. This should result in smaller binaries since -Os is respected now. See https://lists.alpinelinux.org/~alpine/devel/%3C2896c13070c508a49cbaa72c8fb7f34ea947358b.camel%40cogitri.dev%3E for more information.

Release Notes for Alpine 3.12.0

2020-03-02T09:48:44Z

Cogitri: Mention yubikey support

Release Notes for Alpine 3.12.0

2020-03-01T22:18:34Z

Cogitri: Mention initial support for the D language.

== aports ==

==== Initial support for DLang ====

We've added initial support for the D language with this release. We now have GDC, the D compiler frontend using GCC, available on all arches but ppc64le and LDC, a D compiler using the LLVM backend, on x86_64. Most things are built against ldc and as such only available on x86_64 right now due to GDC shipping a rather outdated version of the Phobos, the D standard library.

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

==== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret ====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

==== Preferring enchant2 over enchant ====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

Release Notes for Alpine 3.12.0

2020-03-01T22:13:16Z

Cogitri: Add note about enchant2

== aports ==

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

==== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret ====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

==== Preferring enchant2 over enchant ====

All packages which support enchant2 have been moved over to it instead of using enchant(1). enchant2 now also supports nuspell, which is a faster drop-in replacement for hunspell, which utilizes hunspell's dictionaries.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

Release Notes for Alpine 3.12.0

2020-03-01T22:11:55Z

Cogitri: Add note about the dbus:org.freedesktop.Secret

== aports ==

===== py3-setuptools now uses system python3 modules instead of vendored dependencies =====

py3-setuptools now installs py3-packaging, py3-parsing, py3-appdirs, py3-six and py3-ordered-set from the system.

The following commits are the ones responsible for this change:

* [https://git.alpinelinux.org/aports/commit/?id=efca8852f37cb4028f234f92e2d035617f524820 py3-six] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=55e3496387ad3f2df387b2cf6bc84e85ef729833 py3-ordered-set] (new aport)
* [https://git.alpinelinux.org/aports/commit/?id=cc1636b08fba58b629501d525d658aed4bcbeab2 py3-ordered-set] (move from testing to main)
* [https://git.alpinelinux.org/aports/commit/?id=da743693eda54b9faf5086746b91506495fc689f py3-appdirs] (move from community to main)
* [https://git.alpinelinux.org/aports/commit/?id=60efe787954008af546a5bde839db09f11682102 py3-appdirs] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=a50097b40bcf80a9aec201fef73a722206f43a0d py3-packaging] (use distutils)
* [https://git.alpinelinux.org/aports/commit/?id=52ee5092c510657e9b1e8b4ae0104d405c9eac99 py3-parsing] (install manually)
* [https://git.alpinelinux.org/aports/commit/?id=33ea734e2d28d88a3d545500c96b4c72b3e78432 py3-setuptools] (use system component)

===== ncurses fixes =====

A few fixes trickled in relating exclusively to Alpine Linux that affect ncurses:

With this [https://git.alpinelinux.org/aports/commit/?id=762b9fd601983d8a6e6a60692158f3f22b1b60fe commit] the ncurses-lib package no longer depends on the ncurses-terminfo, which was too big at 7.5 MB, instead ncurses-lib now depends solely on the ncurses-terminfo-base package which weights at around 120 kB.

With this [https://git.alpinelinux.org/aports/commit/?id=56aa7795fecc48561deb095995abd335e16ba515 commit] the ncurses-terminfo-base now includes the most common terminfo databases like tmux, screen, xterm-256color and also databases for packaged terminals like gnome-terminal, vte, konsole, alacritty, kitty, putty. All other terminfo databases are now in ncurses-terminfo.

With this [https://git.alpinelinux.org/aports/commit/?id=1470a6c8e76491a8d059ebd4b7521c4bf20b837c commit] all terminals that have their terminfo databases provided by the ncurses-terminfo-base now depend on it.

===== python3 no longer provides pip3, use py3-pip from community =====

Python3 is now built with --without-ensurepip which removes pip3 and its libraries from it. Instead use the py3-pip pacakge which uses system components.

===== BPF JIT support =====

> TODO: Small preamble about BPF

So it (BPF JIT) has been enabled by default in [https://git.alpinelinux.org/aports/commit/?id=3bf2313adc57fe6b36bf459ddca6d65a392609db 3bf2313adc57fe6b36bf459ddca6d65a392609db], and unprivileged BPF JIT has been disabled in [https://git.alpinelinux.org/aports/commit/?id=4e286992d5ed751f6ca60eb18d77313bb0868513 4e286992d5ed751f6ca60eb18d77313bb0868513].

===== OpenRC now has a sane ordering of directories when configuring kernel parameters =====

Configuring kernel parameters is done by having configuration files in specific locations like <code>/etc/sysctl.conf</code> and files ending with <code>.conf</code> in certain directories like <code>/etc/sysctl.d</code>. Before 3.12.0 the ordering had no logical explanation and
surprised users that expected a hierarchy.

Starting with 3.12.0 the ordering is as follows:

# /lib/sysctl.d/*.conf
# /usr/lib/sysctl.d/*.conf
# /run/sysctl.d/*.conf
# /etc/sysctl.conf
# /etc/sysctl.d/*.conf

<code>/lib/sysctl.d</code> and <code>/usr/lib/sysctl.d</code> are to be used by the distribution and packages. Alpine Linux installs its default configuration file in <code>/lib/sysctl.d/00-alpine.conf</code>. Software installed via our package manager will install to either of those places.

<code>/run/sysctl.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or the location for run-time configuration from daemons/services, will cause the latter to not be read and applied by the <code>sysctl</code> service.

<code>/etc/sysctl.conf</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== OpenRC now has a sane ordering of directories when loading kernel modules =====

Loading kernel modules during boot is done with the <code>modules</code> OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.

Starting with 3.12.0 a more logical ordering is adopted for which configuration files to read and ignore:

# /lib/modules-load.d/*.conf
# /usr/lib/modules-load.d/*.conf
# /run/modules-load.d/*.conf
# /etc/modules
# /etc/modules-load.d/*.conf

<code>/lib/modules-load.d</code> and <code>/usr/lib/modules-load.d</code> are to be used by the distribution and packages. Software installed via our package manager will install to either of those places.

<code>/run/modules-load.d</code> holds configuration that is created at run-time by daemons/services or at very early-boot. Neither the distribution nor the packaged software will install configuration to it, primarily because /run is in temporary memory. Configuration in this location that matches names in the locations used by the distribution and packages will cause the latter not to be read and applied by the <code>modules</code> service.

<code>/etc/modules-load.d</code> holds configuration that is created and maintained by the local administrator, neither Alpine nor its packaged software will touch it, and configuration in that has the same name as in the location reserved for the distribution and packages, or locations reserved for the run-time configuration of daemons/services, will cause the latter to not be read and applied by the <code>modules</code> service.

<code>/etc/modules</code> is a historical location for this kind of configuration and is kept for the same reasons.

===== Telegram Desktop is now available in the community repo =====

See [https://git.alpinelinux.org/aports/commit/?id=184355fdc44bc2e12976d65518fe029d8a6e459d commit] that moved the package to the community repo for explanation.

===== efitools and sbsigntool are now in main/ =====

Those packages have lived in testing/ for a long time and have been successfully used by one of our developers to implement secure-boot in his system. They have been moved to main/ and will be available for others.

==== Packages which need libsecret's DBus API now depend a provider of its API via dbus:org.freedesktop.Secret ====

Previously it was possible to install a program which required the DBus API of libsecret (e.g. Fractal), but not install a secrets provider (e.g. gnome-keyring), so logins wouldn't be saved. This has been corrected and packages which require this API depend on the provider-package dbus:org.freedesktop:Secret now. It's provided by gnome-keyring, kwallet and keepassxc (in that order of importance, i.e. if none of these is pulled in gnome-keyring will be chosen by default). Right now we manually declared the provider for dbus:org.freedesktop.Secret, but eventually we should have an automatic detection for the DBus API packages provide to make this easier for other packages.

== abuild ==

===== Add default functions for subpackages that hold Bash, Zsh and Fish completion =====

abuild now provides default functions for $pkgname-bash-completion, $pkgname-zsh-completion and $pkgname-fish-completion subpackages.

Expected location of the completion files per shell:

* Bash -> <code>/usr/share/bash-completion/completions</code>
* Zsh -> <code>/usr/share/zsh/site-functions</code>
* Fish -> <code>/usr/share/fish/completions</code>

Files must be installed in the expected location in relation to '''$pkgdir''' in '''pacakge()'''.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/d5826968b713123a4f51d3dec1adb1225d0e194f d5826968b713123a4f51d3dec1adb1225d0e194f].

===== newapkbuild when called with CMake (-C) does out-of-source builds by default =====

When packaging with newapkbuild and using the -C switch to pre-fill the apkbuild with skeleton functions for CMake now:

* Adds <code>-B build</code> to the <code>cmake</code> call in '''build()'''.
* Adds <code>-C build</code> the <code>make</code> calls.

Doing out-of-source builds are recommended upstream to the point where warnings are printed when calling CMake on a project.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/e125a764896d884c69cc409e614b65cb336c15e8 e125a764896d884c69cc409e614b65cb336c15e8].

===== set CARGO_HOME to cache dependencies of rust packages =====

CARGO_HOME is now set to '''$SRCDEST/cargo''' and will cache all dependencies downloaded.

Introduced in [https://gitlab.alpinelinux.org/alpine/abuild/commit/af0c88e6abbb1e49224759f5c51b3068e6eab28b af0c88e6abbb1e49224759f5c51b3068e6eab28b].

Root on ZFS with native encryption

2020-01-10T16:10:33Z

Cogitri: Delete Debian installation medium specific setup now that we recommend Ubuntu

= Introduction =

This documentation describes how to set up Alpine Linux using ZFS with a pool that uses ZFS' native encryption capabilities, which have been recently introduced in ZFS on Linux (ZoL) 0.8.0.

Note that you must install the <code>/boot/</code> directory on an unencrypted partition (either an unencrypted ZFS pool or any other FS of your choosing, if it's compatible with your bootloader) to boot correctly.

== Requirements ==

You'll need a medium to put a live image on. You can use any live medium that supports ZoL >=0.8.x, but as of writing this it's easiest to use [https://ubuntu.com/download/desktop Ubuntu 19.10], which comes with ZFS pre-installed.

== Hard Disk Device Name ==

The following documentation uses the <code>/dev/sda</code> device as installation destination. If your environment uses a different device name for your hard disk, use the corresponding device names in the examples. It also uses <code>rpool</code> as name of the root pool, you can change this at will, but be sure to change it everywhere it's mentioned.

= Setting up Alpine Linux Using ZFS with native encryption =

To install Alpine Linux in a ZFS pool with encryption enable, you cannot use the [[Installation|official installation]] procedure, so follow along this guide.

== Creating the Partition Layout ==

Linux requires an unencrypted <code>/boot/</code> partition to boot. You can assign the remaining space for the encrypted ZFS pool.

* Start the <code>fdisk</code> utility to set up partitions:

# fdisk /dev/sda

:* Create the <code>/boot/</code> partition:
::* Enter <code>n</code> → <code>p</code> → <code>1</code> → <code>1</code> → <code>100m</code> to create a new 100 MB primary partition.

:* Set the <code>/boot/</code> partition active:
::* Enter <code>a</code> → <code>1</code>.

:* Create the ZFS partition:
::* Enter <code>n</code> → <code>p</code> → <code>2</code> to start creating the next partition. Press <code>Enter</code> to select the default start cylinder. Enter the size of partition. For example, <code>512m</code> for 512 MB or <code>5g</code> for 5 GB. Alternatively press <code>Enter</code> to set the maximum available size.

:* To verify the settings, press <code>p</code>. The output shows, for example:
<pre>
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 83 Linux
/dev/sda2 206848 41943039 41736192 19.9G 83 Linux
</pre>
* Press <code>w</code> to save the changes.

== Setting up the root pool ==

You can create your rootpool with the following command:

# zpool create -o ashift=12 \
-O acltype=posixacl -O canmount=off -O compression=lz4 \
-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
-O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase \
-O mountpoint=/ -R /mnt \
rpool /dev/sda2

You will have to enter your passphrase at this point. Choose wisely, as your passphrase is most likely [https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#5-security-aspects the weakest link in this setup].

A few notes on the options supplied to zpool:

* <code>ashift=12</code> is recommended here because many drives today have 4KiB (or larger) physical sectors, even though they present 512B logical sectors

* <code>acltype=posixacl</code> enables POSIX ACLs globally

* <code>normalization=formD</code> eliminates some corner cases relating to UTF-8 filename normalization. It also enables <code>utf8only=on</code>, meaning that only files with valid UTF-8 filenames will be accepted.

* <code>xattr=sa</code> vastly improves the performance of extended attributes, but is Linux-only. If you care about using this pool on other OpenZFS implementation don't specify this option.

After completing this, confirm that the pool has been created:

# zpool status

Should return something like:
<pre>
pool: rpool
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sda2 ONLINE 0 0 0

errors: No known data errors
</pre>

=== Creating the required datasets ===

# zfs create -o mountpoint=none -o canmount=off rpool/ROOT
# zfs create -o mountpoint=legacy rpool/ROOT/alpine
# mount -t zfs rpool/ROOT/alpine /mnt/

=== Creating optional datasets (feel free to add your own) ===

# zfs create -o mountpoint=/home rpool/HOME
# zfs create -o mountpoint=/var/log rpool/LOG

== Creating the <code>/boot</code> filesystem ==

# mkfs.ext4 /dev/sda1

== Mounting the <code>/boot</code> filesystem ==

* Create the <code>/mnt/boot/</code> directory and mount the <code>/dev/sda1</code> partition in this directory:

# mkdir /mnt/boot/
# mount -t ext4 /dev/sda1 /mnt/boot/

== Installing Alpine Linux ==

Please follow [[Installing_Alpine_Linux_in_a_chroot|Installing Alpine Linux in a chroot]] to setup a base install of Alpine Linux.

After you've followed that guide, you still have to do some additional setup for ZFS:

* As of the time of writing this ZFS 0.8.x is only available in [[Edge]], so you'll have to enable it in <code>/etc/apk/repositories</code>. Check [https://pkgs.alpinelinux.org/packages?name=zfs pkgs.alpinelinux.org] to see the status of this.

* Install the ZoL and linux-vanilla package: <code>apk add linux-vanilla zfs</code>

* Enable ZFS' services:

# rc-update add zfs-import sysinit
# rc-update add zfs-mount sysinit

* Edit the <code>/etc/mkinitfs/mkinitfs.conf</code> file and append <code>zfs</code> module to the <code>features</code> parameter:

features="ata base ide scsi usb virtio ext4 lvm <u>zfs</u>"

Be mindful to also include other modules which may be required for your setup, such as the <code>nvme</code> module.

* Rebuild the initial RAM disk:

# mkinitfs $(ls /lib/modules/)

* Edit the <code>/etc/update-extlinux.conf</code> file, set the root ZFS dataset and append the following kernel options to the <code>default_kernel_opts</code> parameter:

root=rpool/ROOT/alpine
default_kernel_opts="... <u>rootfstype=zfs</u>"

* Update extlinux's config (if you're not using a different bootloader)

# update-extlinux
# exit

: Ignore the errors the <code>update-extlinux</code> utility displays.

* Write the MBR to the <code>/dev/sda</code> device:

# dd bs=440 count=1 conv=notrunc if=/mnt/usr/share/syslinux/mbr.bin of=/dev/sda

== Unmounting the filesystems ==

* Unmount <code>/mnt/boot/</code>:

# umount /mnt/boot/

* Unmount all zfs filesystems:

# zfs unmount -a

* Reboot the system:

# reboot

== Booting the system ==

Right now mkinitfs doesn't support ZFS asking for passwords during boot, so it'll throw you into a rescue shell for you to enter the password during boot. You have to do the following things after pressing enter:

# zfs load-key -a
# mount -t zfs rpool/ROOT/alpine /sysroot
# exit

And your system should continue booting! :)

= Troubleshooting =

== General Procedure ==

In case your system fails to boot, you can verify the settings and fix incorrect configurations:

* [[#Preparing_the_Installation_Environment|Preparing the Installation Environment]]

* Load the ZFS kernel module:

# modprobe zfs

* [[#Mounting_the_File_Systems|Mount the file systems]]

# zpool import -R /mnt rpool
# mount -t ext4 /dev/sda1 /mnt/boot

* Verify that you run the steps described in the [[#Installing_Alpine_Linux|Installing Alpine Linux]] section correctly. Update the configuration if necessary.

[[Category:Storage]]
[[Category:Security]]

Root on ZFS with native encryption

2020-01-10T16:09:02Z

Cogitri: Recommend Ubuntu instead of Debian

= Introduction =

This documentation describes how to set up Alpine Linux using ZFS with a pool that uses ZFS' native encryption capabilities, which have been recently introduced in ZFS on Linux (ZoL) 0.8.0.

Note that you must install the <code>/boot/</code> directory on an unencrypted partition (either an unencrypted ZFS pool or any other FS of your choosing, if it's compatible with your bootloader) to boot correctly.

== Requirements ==

You'll need a medium to put a live image on. You can use any live medium that supports ZoL >=0.8.x, but as of writing this it's easiest to use [https://ubuntu.com/download/desktop Ubuntu 19.10], which comes with ZFS pre-installed.

== Hard Disk Device Name ==

The following documentation uses the <code>/dev/sda</code> device as installation destination. If your environment uses a different device name for your hard disk, use the corresponding device names in the examples. It also uses <code>rpool</code> as name of the root pool, you can change this at will, but be sure to change it everywhere it's mentioned.

= Setting up Alpine Linux Using ZFS with native encryption =

To install Alpine Linux in a ZFS pool with encryption enable, you cannot use the [[Installation|official installation]] procedure, so follow along this guide.

== Preparing the Installation Environment ==

This section assumes that you're using the previously mentioned Debian installation medium. If you're using a different medium feel free to skip this section.

After booting the Debian image you'll have to enable the <code>experimental</code> repos for the time being to be able to access ZFS 0.8. For this you'll have to edit <code>/etc/apt/sources.list</code>:

# sed 's/buster/experimental/' -i /etc/apt/sources.list
# echo 'deb http://deb.debian.org/debian experimental contrib' >> /etc/apk/repositories

Now install ZFS 0.8:

# apt update
# apt install libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-dkms zfsutils-linux zfs-zed

And load the ZFS module:

# modprobe zfs

== Creating the Partition Layout ==

Linux requires an unencrypted <code>/boot/</code> partition to boot. You can assign the remaining space for the encrypted ZFS pool.

* Start the <code>fdisk</code> utility to set up partitions:

# fdisk /dev/sda

:* Create the <code>/boot/</code> partition:
::* Enter <code>n</code> → <code>p</code> → <code>1</code> → <code>1</code> → <code>100m</code> to create a new 100 MB primary partition.

:* Set the <code>/boot/</code> partition active:
::* Enter <code>a</code> → <code>1</code>.

:* Create the ZFS partition:
::* Enter <code>n</code> → <code>p</code> → <code>2</code> to start creating the next partition. Press <code>Enter</code> to select the default start cylinder. Enter the size of partition. For example, <code>512m</code> for 512 MB or <code>5g</code> for 5 GB. Alternatively press <code>Enter</code> to set the maximum available size.

:* To verify the settings, press <code>p</code>. The output shows, for example:
<pre>
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 83 Linux
/dev/sda2 206848 41943039 41736192 19.9G 83 Linux
</pre>
* Press <code>w</code> to save the changes.

== Setting up the root pool ==

You can create your rootpool with the following command:

# zpool create -o ashift=12 \
-O acltype=posixacl -O canmount=off -O compression=lz4 \
-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
-O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase \
-O mountpoint=/ -R /mnt \
rpool /dev/sda2

You will have to enter your passphrase at this point. Choose wisely, as your passphrase is most likely [https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#5-security-aspects the weakest link in this setup].

A few notes on the options supplied to zpool:

* <code>ashift=12</code> is recommended here because many drives today have 4KiB (or larger) physical sectors, even though they present 512B logical sectors

* <code>acltype=posixacl</code> enables POSIX ACLs globally

* <code>normalization=formD</code> eliminates some corner cases relating to UTF-8 filename normalization. It also enables <code>utf8only=on</code>, meaning that only files with valid UTF-8 filenames will be accepted.

* <code>xattr=sa</code> vastly improves the performance of extended attributes, but is Linux-only. If you care about using this pool on other OpenZFS implementation don't specify this option.

After completing this, confirm that the pool has been created:

# zpool status

Should return something like:
<pre>
pool: rpool
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sda2 ONLINE 0 0 0

errors: No known data errors
</pre>

=== Creating the required datasets ===

# zfs create -o mountpoint=none -o canmount=off rpool/ROOT
# zfs create -o mountpoint=legacy rpool/ROOT/alpine
# mount -t zfs rpool/ROOT/alpine /mnt/

=== Creating optional datasets (feel free to add your own) ===

# zfs create -o mountpoint=/home rpool/HOME
# zfs create -o mountpoint=/var/log rpool/LOG

== Creating the <code>/boot</code> filesystem ==

# mkfs.ext4 /dev/sda1

== Mounting the <code>/boot</code> filesystem ==

* Create the <code>/mnt/boot/</code> directory and mount the <code>/dev/sda1</code> partition in this directory:

# mkdir /mnt/boot/
# mount -t ext4 /dev/sda1 /mnt/boot/

== Installing Alpine Linux ==

Please follow [[Installing_Alpine_Linux_in_a_chroot|Installing Alpine Linux in a chroot]] to setup a base install of Alpine Linux.

After you've followed that guide, you still have to do some additional setup for ZFS:

* As of the time of writing this ZFS 0.8.x is only available in [[Edge]], so you'll have to enable it in <code>/etc/apk/repositories</code>. Check [https://pkgs.alpinelinux.org/packages?name=zfs pkgs.alpinelinux.org] to see the status of this.

* Install the ZoL and linux-vanilla package: <code>apk add linux-vanilla zfs</code>

* Enable ZFS' services:

# rc-update add zfs-import sysinit
# rc-update add zfs-mount sysinit

* Edit the <code>/etc/mkinitfs/mkinitfs.conf</code> file and append <code>zfs</code> module to the <code>features</code> parameter:

features="ata base ide scsi usb virtio ext4 lvm <u>zfs</u>"

Be mindful to also include other modules which may be required for your setup, such as the <code>nvme</code> module.

* Rebuild the initial RAM disk:

# mkinitfs $(ls /lib/modules/)

* Edit the <code>/etc/update-extlinux.conf</code> file, set the root ZFS dataset and append the following kernel options to the <code>default_kernel_opts</code> parameter:

root=rpool/ROOT/alpine
default_kernel_opts="... <u>rootfstype=zfs</u>"

* Update extlinux's config (if you're not using a different bootloader)

# update-extlinux
# exit

: Ignore the errors the <code>update-extlinux</code> utility displays.

* Write the MBR to the <code>/dev/sda</code> device:

# dd bs=440 count=1 conv=notrunc if=/mnt/usr/share/syslinux/mbr.bin of=/dev/sda

== Unmounting the filesystems ==

* Unmount <code>/mnt/boot/</code>:

# umount /mnt/boot/

* Unmount all zfs filesystems:

# zfs unmount -a

* Reboot the system:

# reboot

== Booting the system ==

Right now mkinitfs doesn't support ZFS asking for passwords during boot, so it'll throw you into a rescue shell for you to enter the password during boot. You have to do the following things after pressing enter:

# zfs load-key -a
# mount -t zfs rpool/ROOT/alpine /sysroot
# exit

And your system should continue booting! :)

= Troubleshooting =

== General Procedure ==

In case your system fails to boot, you can verify the settings and fix incorrect configurations:

* [[#Preparing_the_Installation_Environment|Preparing the Installation Environment]]

* Load the ZFS kernel module:

# modprobe zfs

* [[#Mounting_the_File_Systems|Mount the file systems]]

# zpool import -R /mnt rpool
# mount -t ext4 /dev/sda1 /mnt/boot

* Verify that you run the steps described in the [[#Installing_Alpine_Linux|Installing Alpine Linux]] section correctly. Update the configuration if necessary.

[[Category:Storage]]
[[Category:Security]]

GNOME

2019-06-24T11:02:26Z

Cogitri: Update to new GNOME in Alpine v3.11 (edge)

= Initial setup =
Start by booting up Alpine (see [[Installation|these]] instructions on how to do that)<BR>
When you Alpine is up and running, do the initial setup.
{{Cmd|# setup-alpine}}
{{Cmd|# setup-xorg-base}}

= Installing packages =
Install basic desktop system and gnome packages. As of right now, these are in the testing repo.<BR>
This might take a few minutes depending on your network speed.
{{Cmd|# apk add gnome}}
<BR>

If you want to you can also install additional GNOME apps for a more complete GNOME experience with:<BR>
{{Cmd|# apk add gnome-apps}}
<BR>

== Setting up udev ==
You'll have to enable udev in order for GNOME to function properly.

{{Cmd|# apk add udev
# /etc/init.d/udev start && /etc/init.d/udev-trigger start && /etc/init.d/udev-settle start
# rc-update add udev sysinit
# rc-update add udev-trigger sysinit
# rc-update add udev-settle sysinit
}}

== Setting up Xorg ==
Even when using GNOME Wayland you'll still need a setup Xorg for XWayland.

=== Video packages ===

{{cmd|$ apk search xf86-video}}

Then install the driver matching to your card, e.g. if you have an Intel iGPU:

{{cmd|# apk add xf86-video-intel}}

=== Input packages ===

Usually libinput is the best choice, as it's integrated best with GNOME and offers advanced functionality (e.g. palm rejection for touchpads).

{{cmd|# apk add xf86-input-libinput}}

= Starting your desktop =
Start GDM and login with your user.
{{Cmd|rc-service gdm start}}

Once you have verified that it actually works you can make gdm start up at boot:
{{Cmd|rc-update add gdm}}

= Troubleshooting =
If you are unable to login, check /var/log/gdm/greeter.log, there may be output there from X to indicate failed modules, etc.

[[Category:Desktop]]

Tutorials and Howtos

2019-06-01T09:17:36Z

Cogitri: Add "Setting up ZFS with native encryption" to list

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

The tutorials are hands-on and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

Howtos are smaller articles explaining how to perform a particular task with Alpine Linux.

We encourage people to send in both complete articles as well as requesting topics to be covered. If you think you have the skills and knowledge to write an Alpine Linux related article please do so on this Wiki. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}
== Storage ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)'' 
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]

* [[Setting up disks manually]] 
* [[Setting up a software RAID array]]

* [[Raid Administration]]
* [[Setting up encrypted volumes with LUKS]]
* [[Setting up LVM on LUKS]]
* [[Setting up Logical Volumes with LVM]]
** [[Setting up LVM on GPT-labeled disks]]
** [[Installing on GPT LVM]]
* [[Filesystems|Formatting HD/Floppy/Other]] 

* [[Setting up iSCSI]]
** [[iSCSI Raid and Clustered File Systems]]
* [[Setting up NBD]]
* [[Setting up ZFS on LUKS]]
* [[Setting up ZFS with native encryption]]
* [[High performance SCST iSCSI Target on Linux software Raid]] ''(deprecated)'' 
* [[Linux iSCSI Target (TCM)]]
* [[Disk Replication with DRBD]] 

* [[Burning ISOs]] 
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* [[Create a bootable SDHC from a Mac]]
* [[Alpine on ARM]]

== Networking ==

* [[Configure Networking]]
* [[Connecting to a wireless access point]]
* [[Bonding]]
* [[Vlan]]
* [[Bridge]]
* [[OpenVSwitch]]
* [[How to configure static routes]]
* [[Configure a Wireguard interface (wg)]]

* [[Alpine Wall]] - [[How-To Alpine Wall]] - [[Alpine Wall User's Guide]] ''(a new firewall management framework)''

* [[PXE boot]]

* [[Using serial modem]]
* [[Using HSDPA modem]]
* [[Setting up Satellite Internet Connection]]
* [[Using Alpine on Windows domain with IPSEC isolation]]

* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)'' 
* [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[Setting up a OpenVPN server with Alpine]] ''(Allowing single users or devices to remotely connect to your network)''

* [[Experiences with OpenVPN-client on ALIX.2D3]] 

* [[Generating SSL certs with ACF]] 
* [[Setting up unbound DNS server]]
* [[Setting up nsd DNS server]]
* [[TinyDNS Format]]
* [[Fault Tolerant Routing with Alpine Linux]] 
* [[Freeradius Active Directory Integration]]
* [[Multi_ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[OwnCloud]] ''(Installing OwnCloud)''

* [[Seafile: setting up your own private cloud]]

== Post-Install ==


* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

** [[Comparison with other distros]]
* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]
* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
* [[Ansible]] ''(Configuration management)''

* [[Enable Serial Console on Boot]]

* [[How to get regular stuff working]] ''some notes on need-to-know topics''
* [[Installing Oracle Java]]
* [[Rsnapshot|Setting up periodic backups with <samp>rsnapshot</samp>]]

== Virtualization==

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen PCI Passthrough]]
* [[Xen LiveCD]]
* [[qemu]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[Docker]]
* [[Install_Alpine_on_VirtualBox]]

== Desktop Environment ==

* [[Awesome(wm) Setup]]
* [[dwm]] ''(dynamic window manager for X)''
* [[EyeOS]] ''(Cloud Computing Desktop)''
* [[Gnome Setup]]
* [[MATE|MATE Setup]]
* [[Oneye]] ''(Cloud Computing Desktop - Dropbox Alternative)''
* [[Owncloud]] ''(Cloud Computing Desktop - Dropbox Alternative)''
** (to be merged with [[OwnCloud]] ''(Your personal Cloud for storing and sharing your data on-line)'')
* [[Remote Desktop Server]]
* [[Suspend on LID close]]
* [[Sway]]
* [[XFCE Setup]] and [[Xfce Desktop|Desktop Ideas]]
* [[Installing Adobe flash player for Firefox]]
* [[Sound Setup]]
* [[Printer Setup]]
* [[Default applications]]

== Raspberry Pi ==

* [[Raspberry Pi|Raspberry Pi (Installation)]]
* [[Classic install or sys mode on Raspberry Pi]]
* [[RPI Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi Zero W - Installation]]

== PowerPC ==

* [[Ppc64le|Powepc64le (Installation)]]

== IBM Z (IBM z Systems) ==

* [[s390x|s390x (Installation)]]

== Applications ==

=== Telephony ===
* [[Setting up Zaptel/Asterisk on Alpine]]
** [[Setting up Streaming an Asterisk Channel]]
* [[Freepbx on Alpine Linux]]
* [[FreePBX_V3]] ''(FreeSWITCH, Asterisk GUI web acces tool)''
* [[2600hz]] ''(FreeSWITCH, Asterisk GUI web access tool)''
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

=== Mail ===
* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
** [[Hosting Web/Email services on Alpine]]
* [[ISP Mail Server HowTo]] 
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
** [[ISP Mail Server 3.x HowTo]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* [[Protecting your email server with Alpine]]
* [[Setting up clamsmtp]]
* [[Setting up dovecot with imap and ssl]]
* [[relay email to gmail (msmtp, mailx, sendmail]]

=== HTTP ===
* [[Lighttpd]]
** [[Lighttpd Https access]]
** [[Setting Up Lighttpd with PHP]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Cherokee]]
* [[Nginx]]
** [[Nginx_with_PHP#Nginx_with_PHP|Nginx with PHP]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]

* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)'' 

* [[Setting up Transparent Squid Proxy]] 
** [[SqStat]] ''(Script to look at active squid users connections)''
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[Setting up Explicit Squid Proxy]]

* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[WordPress]] ''(Web software to create website or blog)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[DokuWiki]]
* [[Darkhttpd]]
* [[Tomcat]]

=== Other Servers ===
* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''

* [[Setting up a nfs-server]]
* [[Setting up a samba-server]] ''(standard file sharing)''
* [[Setting up a samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Phpizabi]] ''(Social Networking Platform)''
* [[Statusnet]] ''(Microblogging Platform)''
* [[Pastebin]] ''(Pastebin software application)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request-Tracker]] ''(Ticket system)''
* [[OsTicket]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

* [[Cgit]]
** [[Setting up a git repository server with gitolite and cgit]] 
* [[Roundcube]] ''(Webmail system)''
* [[Glpi]] ''(Manage inventory of technical resources)''

* [[How to setup a Alpine Linux mirror]]
* [[Cups]]
* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''
* [[How To Setup Your Own IRC Network]] ''(Using {{Pkg|charybdis}} and {{Pkg|atheme-iris}})''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[Chrony and GPSD | Using chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Sending SMS using gnokii]]
* [[IPTV How To|Internet Protocol television (IPTV)]]
* [[UniFi_Controller]]
* [[DNSCrypt-Proxy]] ''Encrypt and authenticate DNS calls from your system''

=== Monitoring ===
* Setting up [[collectd]]
* [[Traffic monitoring]] 
* [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Setting up monitoring using rrdtool (and rrdcollect)]]
* [[Setting up Cacti|Cacti]] ''(Front-end for rrdtool networking monitor)''
* [[LTTng]] ''(Kernel and userspace tracing)''
* [[Setting up Zabbix|Zabbix]] ''(Monitor and track the status of network services and hardware)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting up Smokeping|Smokeping]] ''(Network latency monitoring)'' 
** [[Setting up MRTG and Smokeping to Monitor Bandwidth Usage and Network Latency]]
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance)'' 
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 

* [[IP Accounting]] 
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[SqStat]] ''(Script to look at active squid users connections)''

* [[Piwik]] ''(A real time web analytics software program)''
* [[Awstats]] ''(Free log file analyzer)''
* [[Intrusion Detection using Snort]]
** [[Intrusion Detection using Snort, Sguil, Barnyard and more]]
* [[Dglog]] ''(Log analyzer for the web content filter DansGuardian)''

* [[Webmin]] ''(A web-based interface for Linux system)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Linfo]]

* [[Setting up lm_sensors]]

* [[ZoneMinder video camera security and surveillance]]

== Misc ==

* [[:Category:Shell]]
* [[:Category:Programming]]
* [[Running glibc programs]]
* [[:Category:Drivers]]
* [[:Category:Multimedia]]
* [[Kernel Modesetting]]
* [[CPU frequency scaling]]

== Complete Solutions ==
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[High performance SCST iSCSI Target on Linux software Raid]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[Experiences with OpenVPN-client on ALIX.2D3]]
* [[Building a cloud with Alpine Linux]]

* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small_Office_Services]]

Root on ZFS with native encryption

2019-06-01T09:15:57Z

Cogitri: Initial Page

= Introduction =

This documentation describes how to set up Alpine Linux using ZFS with a pool that uses ZFS' native encryption capabilities, which have been recently introduced in ZFS on Linux (ZoL) 0.8.0.

Note that you must install the <code>/boot/</code> directory on an unencrypted partition (either an unencrypted ZFS pool or any other FS of your choosing, if it's compatible with your bootloader) to boot correctly.

== Requirements ==

You'll need a medium to put a live image on. You can use any live medium that supports ZoL >=0.8.x, but as of writing this it's easiest to use [https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/ Debian Buster's live images] for this.

== Hard Disk Device Name ==

The following documentation uses the <code>/dev/sda</code> device as installation destination. If your environment uses a different device name for your hard disk, use the corresponding device names in the examples. It also uses <code>rpool</code> as name of the root pool, you can change this at will, but be sure to change it everywhere it's mentioned.

= Setting up Alpine Linux Using ZFS with native encryption =

To install Alpine Linux in a ZFS pool with encryption enable, you cannot use the [[Installation|official installation]] procedure, so follow along this guide.

== Preparing the Installation Environment ==

This section assumes that you're using the previously mentioned Debian installation medium. If you're using a different medium feel free to skip this section.

After booting the Debian image you'll have to enable the <code>experimental</code> repos for the time being to be able to access ZFS 0.8. For this you'll have to edit <code>/etc/apt/sources.list</code>:

# sed 's/buster/experimental/' -i /etc/apt/sources.list
# echo 'deb http://deb.debian.org/debian experimental contrib'

Now install ZFS 0.8:

# apt update
# apt install libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-dkms zfsutils-linux zfs-zed

And load the ZFS module:

# modprobe zfs

== Creating the Partition Layout ==

Linux requires an unencrypted <code>/boot/</code> partition to boot. You can assign the remaining space for the encrypted ZFS pool.

* Start the <code>fdisk</code> utility to set up partitions:

# fdisk /dev/sda

:* Create the <code>/boot/</code> partition:
::* Enter <code>n</code> → <code>p</code> → <code>1</code> → <code>1</code> → <code>100m</code> to create a new 100 MB primary partition.

:* Set the <code>/boot/</code> partition active:
::* Enter <code>a</code> → <code>1</code>.

:* Create the ZFS partition:
::* Enter <code>n</code> → <code>p</code> → <code>2</code> to start creating the next partition. Press <code>Enter</code> to select the default start cylinder. Enter the size of partition. For example, <code>512m</code> for 512 MB or <code>5g</code> for 5 GB. Alternatively press <code>Enter</code> to set the maximum available size.

:* To verify the settings, press <code>p</code>. The output shows, for example:
<pre>
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 83 Linux
/dev/sda2 206848 41943039 41736192 19.9G 83 Linux
</pre>
* Press <code>w</code> to save the changes.

== Setting up the root pool ==

You can create your rootpool with the following command:

# zpool create -o ashift=12 \
-O acltype=posixacl -O canmount=off -O compression=lz4 \
-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
-O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase \
-O mountpoint=/ -R /mnt \
rpool /dev/sda2

You will have to enter your passphrase at this point. Choose wisely, as your passphrase is most likely [https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#5-security-aspects the weakest link in this setup].

A few notes on the options supplied to zpool:

* <code>ashift=12</code> is recommended here because many drives today have 4KiB (or larger) physical sectors, even though they present 512B logical sectors

* <code>acltype=posixacl</code> enables POSIX ACLs globally

* <code>normalization=formD</code> eliminates some corner cases relating to UTF-8 filename normalization. It also enables <code>utf8only=on</code>, meaning that only files with valid UTF-8 filenames will be accepted.

* <code>xattr=sa</code> vastly improves the performance of extended attributes, but is Linux-only. If you care about using this pool on other OpenZFS implementation don't specify this option.

After completing this, confirm that the pool has been created:

# zpool status

Should return something like:
<pre>
pool: rpool
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sda2 ONLINE 0 0 0

errors: No known data errors
</pre>

=== Creating the required datasets ===

# zfs create -o mountpoint=none -o canmount=off rpool/ROOT
# zfs create -o mountpoint=legacy rpool/ROOT/alpine
# mount -t zfs rpool/ROOT/alpine /mnt/

=== Creating optional datasets (feel free to add your own) ===

# zfs create -o mountpoint=/home rpool/HOME
# zfs create -o mountpoint=/var/log rpool/LOG

== Creating the <code>/boot</code> filesystem ==

# mkfs.ext4 /dev/sda1

== Mounting the <code>/boot</code> filesystem ==

* Create the <code>/mnt/boot/</code> directory and mount the <code>/dev/sda1</code> partition in this directory:

# mkdir /mnt/boot/
# mount -t ext4 /dev/sda1 /mnt/boot/

== Installing Alpine Linux ==

Please follow [[Installing_Alpine_Linux_in_a_chroot|Installing Alpine Linux in a chroot]] to setup a base install of Alpine Linux.

After you've followed that guide, you still have to do some additional setup for ZFS:

* As of the time of writing this ZFS 0.8.x is only available in [[Edge]], so you'll have to enable it in <code>/etc/apk/repositories</code>. Check [https://pkgs.alpinelinux.org/packages?name=zfs pkgs.alpinelinux.org] to see the status of this.

* Install the ZoL and linux-vanilla package: <code>apk install linux-vanialla zfs</code>

* Enable ZFS' services:

# rc-update add zfs-import sysinit
# rc-update add zfs-mount sysinit

* Edit the <code>/etc/mkinitfs/mkinitfs.conf</code> file and append <code>zfs</code> module to the <code>features</code> parameter:

features="ata base ide scsi usb virtio ext4 lvm <u>zfs</u>"

Be mindful to also include other modules which may be required for your setup, such as the <code>nvme</code> module.

* Rebuild the initial RAM disk:

# mkinitfs $(ls /lib/modules/)

* Edit the <code>/etc/update-extlinux.conf</code> file, set the root ZFS dataset and append the following kernel options to the <code>default_kernel_opts</code> parameter:

root=rpool/ROOT/alpine
default_kernel_opts="... <u>rootfstype=zfs</u>"

* Update extlinux's config (if you're not using a different bootloader)

# update-extlinux
# exit

: Ignore the errors the <code>update-extlinux</code> utility displays.

* Write the MBR to the <code>/dev/sda</code> device:

# dd bs=440 count=1 conv=notrunc if=/mnt/usr/share/syslinux/mbr.bin of=/dev/sda

== Unmounting the filesystems ==

* Unmount <code>/mnt/boot/</code>:

# umount /mnt/boot/

* Unmount all zfs filesystems:

# zfs unmount -a

* Reboot the system:

# reboot

== Booting the system ==

Right now mkinitfs doesn't support ZFS asking for passwords during boot, so it'll throw you into a rescue shell for you to enter the password during boot. You have to do the following things after pressing enter:

# zfs load-key -a
# mount -t zfs rpool/ROOT/alpine /sysroot
# exit

And your system should continue booting! :)

= Troubleshooting =

== General Procedure ==

In case your system fails to boot, you can verify the settings and fix incorrect configurations:

* [[#Preparing_the_Installation_Environment|Preparing the Installation Environment]]

* Load the ZFS kernel module:

# modprobe zfs

* [[#Mounting_the_File_Systems|Mount the file systems]]

# zpool import -R /mnt rpool
# mount -t ext4 /dev/sda1 /mnt/boot

* Verify that you run the steps described in the [[#Installing_Alpine_Linux|Installing Alpine Linux]] section correctly. Update the configuration if necessary.

[[Category:Storage]]
[[Category:Security]]