Alpine Linux - User contributions [en]

Release Notes for Alpine 3.23.0

2025-12-02T02:40:55Z

Aqaqland: remove ircservices

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

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

== Important changes ==

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

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

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

For more information, take a look at the release notes of apk v3: TODO

=== /usr merge ===

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

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

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

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

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

== Significant changes ==

=== Static binaries are built as PIE ===

{{Note|TODO: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17294#note_524739}}

=== LLVM metapackage ===

{{Note|TODO}}

=== nftrules ===

{{Note|TODO: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/67137}}

=== curl HTTP/3 ===

{{Note|TODO: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/89382}}

== Note-worthy updates ==

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

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

=== GCC 15 ===

=== LLVM 21 ===

=== ifupdown-ng 0.13 ===

{{Note|TODO}}

=== GNOME 49 ===

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

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

=== ffmpeg 8 ===

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

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

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

=== ifstate 2 ===

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

== Significant removals ==



=== More Qt5 removals ===

{{Note|TODO}}

=== ffmpeg4 ===

{{Note|TODO}}

=== LLVM 17 ===

=== rssh ===

rssh package has been removed due to the dead upstream.

=== ircservices ===

unmaintained upstream for years

<hr><center>[[Release Notes for Alpine 3.22.0|← Previous page: Release Notes for Alpine 3.22.0]]</center>

Release Notes for Alpine 3.23.0

2025-07-29T12:57:51Z

Aqaqland: /* Significant removals */

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

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

{{Note|We're beginning to work on the roadmap for Alpine Linux v3.23. To view the upcoming changes, see {{Issue|17294}}.}}

== Important changes ==

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

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

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

For more information, take a look at the release notes of apk v3: TODO

=== /usr merge ===

New installations are now /usr-merged, and people are encouraged to merge their systems after upgrade. See the [https://alpinelinux.org/posts/2025-09-01-usr-merge.html| official announcement] for more details

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

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

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

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

== Significant changes ==

=== Static binaries are built as PIE ===

{{Note|TODO: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17294#note_524739}}

=== LLVM metapackage ===

{{Note|TODO}}

== Note-worthy updates ==

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

* BIRD TODO
* busybox TODO
* Deno TODO
* GCC TODO
* GNOME TODO
* Go TODO
* ISC BIND TODO
* KDE Plasma TODO
* Linux TODO
* LLVM TODO
* LXQt TODO
* nginx TODO
* NodeJS TODO (LTS)
* PHP TODO
* Qt TODO
* Ruby TODO
* Rust TODO
* wlroots TODO
* zigbee2mqtt TODO

== Significant removals ==



=== rssh ===

rssh package has been removed due to the dead upstream.

Release Notes for Alpine 3.22.0

2025-05-20T13:17:05Z

Aqaqland: remove meilisearch

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

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

== Important changes ==

== Significant changes ==

=== apk-tools ===

This release is the last release using apk-tools v2.14. The next Alpine v3.23 will include apk-tools v3. The packages and index format are still using the legacy v2 format.

There are a number of new changes in the new apk-tools release. To test apk-tools v3, [https://wiki.alpinelinux.org/wiki/Upgrading_Alpine_Linux_to_a_new_release_branch#Upgrading_to_Edge upgrade to Alpine edge, enable the testing repository] and install {{pkg|apk-tools3}}.

{{Note|TODO: if edge upgrades to apk-tools 3, remove the testing repo and apk-tools3 package mention}}

=== KDE Plasma ===

The X11 session for KDE Plasma has been removed. If you had {{pkg|plasma-workspace-x11|branch=v3.21|arch=}} installed make sure to remove it from {{path|/etc/apk/world}}. Wayland is the only available option now.

=== SDL ===

{{pkg|sdl3}} and {{pkg|sdl2-compat}} were moved to the community repository and are now the default SDL provider. To force the installation of {{pkg|sdl2}}, use <code>apk add sdl2</code>.

=== Adwaita Fonts ===

As a result of [https://release.gnome.org/48/#new-fonts GNOME's switch] to {{pkg|adwaita-fonts}}, the default font for GTK-based applications (e.g. {{pkg|vte3}} or {{pkg|libadwaita}} Applications) was changed. If you want to revert or override the fonts, you can use:

<pre>
$ apk add font-cantarell font-adobe-source-code-pro
$ gsettings set org.gnome.desktop.interface font-name 'Cantarell 11'
$ gsettings set org.gnome.desktop.interface monospace-font-name 'Source Code Pro 11'
</pre>

{{pkg|adwaita-fonts}} is pulled in as a dependency of some packages since it broke the default behaviour for various applications.

=== GeoClue ===

Since Mozilla Location Services (MLS), which were used as the geolocation service in geoclue, [https://discourse.mozilla.org/t/retiring-the-mozilla-location-service/128693 has been retired by Mozilla], Alpine switched to [https://beacondb.net/ beaconDB] as the default geolocation provider. {{MR|76764}}

=== BIRD Routing Daemon ===

The {{pkg|bird|repo=community}} routing daemon package has been upgrade to version 3 which introduces a new multi-threaded architecture. A side effect of this change is [https://trubka.network.cz/pipermail/bird-users/2024-December/017973.html significantly increased memory consumption] of the daemon. This update is configuration-compatible with BIRD v2 but there are some behavioral backwards incompatibilities. Users should read the [https://gitlab.nic.cz/labs/bird/-/blob/stable-v3.0/doc/migration-bird3.md migration guide]. Notably the format of <tt>show route all</tt> has changed as has the format of the logs, which may impact scripts and automation that consume those outputs. Users who require BIRD v2 should install the {{pkg|bird2|repo=community}} package instead.

== Note-worthy updates ==

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

* Linux TODO
* busybox TODO
* GCC TODO
* LLVM TODO
* Go TODO
* Rust TODO
* PHP TODO
* GNOME TODO
* KDE Plasma TODO
* LXQt TODO
* Qt TODO
* wlroots TODO
* ISC BIND 9.20.TODO
* BIRD 3.1.TODO

=== LLVM ===

LLVM 20 is available as {{pkg|llvm}}/{{pkg|clang}} (or {{pkg|llvm20}}/{{pkg|clang20}} explictly) additionally to LLVM 19, 18, 17, 16 and 15. ({{MR|80901}}, {{MR|82502}})

LLD is now also splitted per version and is available as {{pkg|lld20}} (default for {{pkg|lld}}), {{pkg|lld19}} and {{pkg|lld18}}. ({{MR|81774}})

== Significant removals ==

=== LXD ===

LXD was moved to the testing repository and is therefore not available on Alpine Linux 3.22. It was deprecated in favor of {{pkg|incus}} and {{pkg|incus-feature}} (feature branch).

Take a look at the [https://linuxcontainers.org/incus/docs/main/howto/server_migrate_lxd/ Migration Guide] on how to migrate from LXD to Incus using the {{pkg|incus-conversion}} or {{pkg|incus-feature-conversion}} package.

=== Qt 5 ===

On 26th of May 2025, Qt 5 will be unmaintained upstream. Therefore we're removing unused libraries from our repositories and are migrating the remaining packages to Qt 6.

Applications that still use Qt 5 libraries won't be removed, but libraries without consumers in our repository will.

For more information, see Issue {{Issue|17114}}.

=== Meilisearch ===

Meilisearch in aports has not been maintained for a long time.

How to make a cross architecture chroot

2025-02-06T06:43:13Z

Aqaqland: /* Troubleshooting */

If you have an ARM computer, you will find that some software is only available for x86_64. One possible solution is to have a full x86_64 virtual machine, but that has quite a lot of overhead from having to emulate the entire system. Fortunately, there is [https://qemu-project.gitlab.io/qemu/user/main.html QEMU User space emulation] which still uses the host kernel, so there is less overhead. This guide will show you how to make a chroot and enable transparent x86_64 binary execution using qemu and binfmt_misc.

== Prerequisites ==

You should be familiar with the Linux command line.

This guide is written assuming you have Alpine as the main install as well as putting Alpine in the chroot.

Also, the commands shown assume you have '''root''' privileges. Either use <code>sudo/doas</code> as needed (or <code>su</code> first).

== Installing necessary software ==

'''[[Repositories#Managing_repositories| Enable the Community Repository]]''' and install the '''qemu''' user mode binaries for the architectures you want to use, in this case x86_64 and i386:

{{Cmd|# apk add {{Pkg|qemu-x86_64}} {{Pkg|qemu-i386}} {{Pkg|qemu-openrc}}}}

Please note there are the <code>qemu-system-*</code> packages, you don't want those since they are used for full virtual machine emulation.

== Enable the <code>qemu-binfmt</code> service and start it ==

The qemu-binfmt script is an OpenRC init script that registers the binfmt_misc handlers when the service starts and unregisters them when the service stops. Add the service to the default runlevel and start it immediately:

{{Cmd|# rc-update add qemu-binfmt default
# rc-service qemu-binfmt start}}

== Make the chroot folder ==

To keep it simple, we're just going to use the apk repositories specified on the host system. This guide assumes the <code>$CHROOT</code> environment variable holds the directory where you want to make the chroot. Make the chroot directory and the <code>etc/apk</code> subdirectory (which we'll copy the apk repositories file to):

{{Cmd|# mkdir -p $CHROOT/etc/apk/}}

Now copy the host's apk repositories into the chroot folder:

{{Cmd|# cp /etc/apk/repositories $CHROOT/etc/apk/}}

You'll also need to copy the <code>resolv.conf</code> file into the chroot so it can have internet access:

{{Cmd|# cp /etc/resolv.conf $CHROOT/etc/}}

== Install <code>alpine-base</code> into the chroot folder ==

The {{Pkg|alpine-base}} meta package is all that's needed to have a fully working alpine system. The apk invocation used here has a few more options than what you might be used to:

{{Cmd|# apk add -p $CHROOT --initdb -U --arch x86_64 --allow-untrusted alpine-base}}

Here's what all the options do:

*<code>-p $CHROOT</code>: Sets the root of the install to <code>$CHROOT</code> instead of <code>/</code>
*<code>--initdb</code>: Initialize a new package database.
*<code>-U</code>: Alias for <code>--cache-max-age 1</code>. Basically means don't install from cache.
*<code>--arch x86_64</code>: Install x86_64 packages instead of native packages. Replace this with whichever architecture you want to emulate instead (e.g. <code>--arch x86</code>).
*<code>--allow-untrusted</code>: Install packages with untrusted signature or no signature. (This is needed since the keys for different architectures are different than what will be on your host. If you have the correct keys, you can copy them into the <code>$CHROOT/etc/apk/keys/</code> directory and remove this flag).

== Mount the virtual file systems into the chroot ==

{{Cmd|# mount -t proc proc $CHROOT/proc/
# mount -t sysfs sys $CHROOT/sys/
# mount -o bind /dev/ $CHROOT/dev/
# mount -o bind /dev/pts/ $CHROOT/dev/pts/
# mount -o bind /run $CHROOT/run/}}

==The exciting part: Enter the chroot==

If you've followed all the steps, this part should be uneventful. The <code>chroot</code> invocation uses the special command of <code>ash -l</code> to run as a login shell and source <code>/etc/profile</code>:

{{Cmd|# chroot $CHROOT/ ash -l}}

==Troubleshooting==

If you get a <code>ERROR: ${package_name}.post-install: script exited with error 127</code> while trying to add the alpine-base, that normally means that qemu binfmt_misc hasn't been setup properly. Check if the <code>qemu-$arch</code> package has been installed and see if the binfmt_misc service is running. Remember to restart the service after adding a new architecture.

{{Cmd|# rc-service qemu-binfmt restart}}

You can also see if there is a <code>qemu-$arch</code> entry in <code>/proc/sys/fs/binfmt_misc/</code>.

Programs that use [https://en.wikipedia.org/wiki/Netlink Netlink] (e.g. <code>ip addr</code>) don't seem to work properly since qemu doesn't emulate the Netlink protocol properly.

==References==

* [https://archive.is/ldO0C Transparently running binaries from any architecture in Linux with QEMU and binfmt_misc] (see the section titled <code>Emulating full ARM rootfs</code>)

[[Category:System Administration]]

Release Notes for Alpine 3.21.0

2024-09-27T10:19:39Z

Aqaqland: bats changes

== Highlights ==

* Rust 1.81
* GNOME 47
* KDE Plasma 6.1.5

== GNOME 47 ==

GNOME 47 made it into Alpine 3.21. Everything should work as expected. Make sure you read the GNOME 47 release notes: https://release.gnome.org/47/

== Jellyfin ==

Jellyfin now uses the recommended fork of ffmpeg called `jellyfin-ffmpeg` by default. If you want to change that, take a look at the `ffmpegpath` variable in `/etc/conf.d/jellyfin`. (!69924)

== Bats ==

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

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

Sircbot

2024-03-08T02:29:15Z

Aqaqland: Add sending message with lua library

Sircbot is a Minimalistic IRC bot based in Lua script.

== Install sircbot ==

{{Cmd|# apk add {{Pkg|sircbot}} {{Pkg|lua-sircbot}}}}

== Configure sircbot daemon ==

Edit the configuration file located at {{Path|/etc/conf.d/sircbot}} and change the name, server, and channel:

{{Cat|/etc/conf.d/sircbot|...
sircbot_opts{{=}}"-n NICK -s SERVER"
sircbot_channels{{=}}"#channel"
...}}

It is the same to run sirbot directly.

{{Cmd|$ sircbot -s SERVER -n NICK '#channel'}}

Sircbot would act as "daemon" joining server and channels thus do the following response.

== Sending messages ==

There are two ways to send messages, channel need be specified first in sirbot daemon.

=== sircbot-send ===

{{Cmd|<nowiki>$ echo "$MESSAGE" | sircbot-send '#channel'</nowiki>}}

=== sircbot lua library ===

{{Cat|lua_script|<nowiki>local sircbot = require('sircbot')
local client = sircbot.connect('#channel')

client:send("hello")</nowiki>}}

== Create sircbot scripts folders and files ==

Sircbot will use an folder for the channel where is logged in. The folder path is: {{Path|/etc/sircbot.d/#channel}}

For every message that goes to the channel, sircbot will run all scripts in /etc/sircbot.d/#channel/ with sender, message and channel name as arguments.[https://git-old.alpinelinux.org/hosted/sircbot/about/]

== Example ==

Lets see an example:

Our bot will be named ''kumquat'' and we will join at the #test channel in the irc.ddd.ddd server.

{{Cat|/etc/conf.d/sircbot|sircbot_opts{{=}}"-n kumquat -s irc.ddd.ddd"
sircbot_channels{{=}}"#test"}}

Create folder bot.

{{Cmd|# mkdir /etc/sircbot.d/#test -p}}

Create the Lua script file for our bot.

{{Cat|/etc/sircbot.d/#test/commands|<nowiki>#!/usr/bin/lua

-- Scripts for kumquat in Lua

args={...}

sender=args[1] -- is the nickname of running the command on IRC
message=args[2] -- is the message or command typed
channel=args[3] -- is the channel name

os.execute("sleep " .. tonumber(1))

-- This command will show: What can i do for you "nickname"?
local kumquatresult = string.find(message, "kumquat")
if kumquatresult ~= nil then
command="echo 'What can i do for you '"..sender.."'?' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show: Hello there, amigo "nickname"
local kumquatresult = string.find(message, "hi")
if kumquatresult ~= nil then
command="echo 'Hello there, amigo '"..sender.."'' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show the current UTC date and time
local kumquatresult = string.find(message, "date")
if kumquatresult ~= nil then
command="date -u | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a search for a alpine linux package
local kumquatresult = string.find(message, "apk search:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 12))
command="apk search"..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will resolve a host name and ip
local kumquatresult = string.find(message, "host:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="host "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a 3 times ping to a server or ip address
local kumquatresult = string.find(message, "ping:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="ping -c 3 "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end</nowiki>}}

Make the script to be executable

{{Cmd|# chmod +x /etc/sircbot.d/#test/commands}}

== Giving life to the bot ==

Starting sircbot daemon and adding service to boot.

{{Cmd|# rc-service sircbot start && rc-update add sircbot default}}

== Troubleshooting ==

If your bot is not responding as expected, an easy way to troubleshoot is to manually execute the script in /etc/sircbot.d/<#channelname>/<scriptname> with the three agruments.

{{Cmd|$ /etc/sircbot.d/<#channelname>/<scriptname> username hi '<#channelname>'}}

If your bot responds as expected, then you know that your script works. The problem is that sircbot is not executing the script. Here are two likely causes:

# Sircbot is case-sensitive when looking for the channel directory for a script to execute. For example, if you have a channel named "#Alpine", sircbot will look for /etc/sircbot.d/#Alpine/*. If that pathway isn't exactly right, then sircbot will skip that folder. In our example, if you have /etc/sircbot.d/#alpine/script, sircbot will not execute anything in that folder. To fix, simply rename the folder to /etc/sircbot.d/#Alpine/
# Sircbot doesn't execute scripts that have a '.' in the name. For example a script named 'listen.lua' will not be executed. Simply rename the script to 'listen'.

[[Category:Networking]]

Sircbot

2024-03-07T12:36:52Z

Aqaqland: /* Create sircbot scripts folders and files */

Sircbot is a Minimalistic IRC bot based in Lua script.

== Install sircbot ==

{{Cmd|# apk add {{Pkg|sircbot}} {{Pkg|lua-sircbot}}}}

== Configure sircbot ==

Edit the configuration file located at {{Path|/etc/conf.d/sircbot}} and change the name, server, and channel:

{{Cat|/etc/conf.d/sircbot|...
sircbot_opts{{=}}"-n name -s server"
sircbot_channels{{=}}"#channel"
...}}

== Create sircbot scripts folders and files ==

Sircbot will use an folder for the channel where is logged in. Lets say we will use it at the "test" channel.
The folder path is: {{Path|/etc/sircbot.d/#<channel>}}

== Example ==

Lets see an example:

Our bot will be named ''kumquat'' and we will join at the #test channel in the irc.ddd.ddd server.

{{Cat|/etc/conf.d/sircbot|sircbot_opts{{=}}"-n kumquat -s irc.ddd.ddd"
sircbot_channels{{=}}"#test"}}

Create folder bot.

{{Cmd|# mkdir /etc/sircbot.d/#test -p}}

Create the Lua script file for our bot.

{{Cat|/etc/sircbot.d/#test/commands|<nowiki>#!/usr/bin/lua

-- Scripts for kumquat in Lua

args={...}

sender=args[1] -- is the nickname of running the command on IRC
message=args[2] -- is the message or command typed
channel=args[3] -- is the channel name

os.execute("sleep " .. tonumber(1))

-- This command will show: What can i do for you "nickname"?
local kumquatresult = string.find(message, "kumquat")
if kumquatresult ~= nil then
command="echo 'What can i do for you '"..sender.."'?' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show: Hello there, amigo "nickname"
local kumquatresult = string.find(message, "hi")
if kumquatresult ~= nil then
command="echo 'Hello there, amigo '"..sender.."'' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show the current UTC date and time
local kumquatresult = string.find(message, "date")
if kumquatresult ~= nil then
command="date -u | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a search for a alpine linux package
local kumquatresult = string.find(message, "apk search:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 12))
command="apk search"..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will resolve a host name and ip
local kumquatresult = string.find(message, "host:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="host "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a 3 times ping to a server or ip address
local kumquatresult = string.find(message, "ping:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="ping -c 3 "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end</nowiki>}}

Make the script to be executable

{{Cmd|# chmod +x /etc/sircbot.d/#test/commands}}

== Giving life to the bot ==

Starting bot service and adding to boot.

{{Cmd|# rc-service sircbot start && rc-update add sircbot default}}

== Troubleshooting ==

If your bot is not responding as expected, an easy way to troubleshoot is to manually execute the script in /etc/sircbot.d/<#channelname>/<scriptname> with the three agruments.

{{Cmd|$ /etc/sircbot.d/<#channelname>/<scriptname> username hi '<#channelname>'}}

If your bot responds as expected, then you know that your script works. The problem is that sircbot is not executing the script. Here are two likely causes:

# Sircbot is case-sensitive when looking for the channel directory for a script to execute. For example, if you have a channel named "#Alpine", sircbot will look for /etc/sircbot.d/#Alpine/*. If that pathway isn't exactly right, then sircbot will skip that folder. In our example, if you have /etc/sircbot.d/#alpine/script, sircbot will not execute anything in that folder. To fix, simply rename the folder to /etc/sircbot.d/#Alpine/
# Sircbot doesn't execute scripts that have a '.' in the name. For example a script named 'listen.lua' will not be executed. Simply rename the script to 'listen'.

[[Category:Networking]]

Include:AbuildRootBld

2024-01-12T16:06:16Z

Aqaqland: abuild rootbld tips

Install package <code>abuild-rootbld</code>:

{{Cmd|apk add abuild-rootbld}}

You may now build your packages from source in an unprivileged sandbox based on [https://github.com/containers/bubblewrap bubblewrap] with the command: {{Cmd|abuild rootbld}}

<code>rootbld</code> assumes your APKBUILD file is in the <code>~/aports</code> whose structure like [https://gitlab.alpinelinux.org/alpine/aports aports] or you need to set environment variable <code>APORTSDIR</code> to current directory.
If the build process needs network access there has to bet set the '''net''' option in [[APKBUILD_Reference#options|APKBUILD]].

Note that using <code>rootbld</code> inside a docker container requires [[Build_with_abuild_rootbld_in_Docker_container|additional configuration]].

[[category: Package Manager]]