alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2023-02-02T23:07:16Zhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549Make ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILE2023-02-02T23:07:16ZRogério da Silva YokomizoMake ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILEOn `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab...On `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-disk.in#L866
It would be nice to be able to set `ERASE_DISK` via `USEANSERFILE`.
```
setup-alpine -f ANSWERS
# ANSWERS file
ERASE_DISK=/dev/sda # <---- Does not pass through from setup-alpine into setup-disk
DISKOPTS="-m sys /dev/sda"
```
Since it is possible to define `DISKOPTS` via `USEANSERFILE`, I see no reason why `ERASE_DISK` could not be exported/forwarded. I could send a patch for this.
relevant lines:
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L72
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L263https://gitlab.alpinelinux.org/alpine/aports/-/issues/14565[PDNS] [3.17 & Edge] - could not open certificate file "/root/.postgresql/pos...2024-01-30T14:14:22ZTuran Asikoglu[PDNS] [3.17 & Edge] - could not open certificate file "/root/.postgresql/postgresql.crt": Permission deniedSince updating to Alpine 3.17 from 3.16, PowerDNS is not able to connect to my Postgres backend via SSL causing it to retry using cleartext which also fails due to our db denying cleartext connectivity.
```
Caught an exception instantia...Since updating to Alpine 3.17 from 3.16, PowerDNS is not able to connect to my Postgres backend via SSL causing it to retry using cleartext which also fails due to our db denying cleartext connectivity.
```
Caught an exception instantiating a backend: Unable to launch gpgsql connection: Unable to connect to database, connect string: dbname='<HIDDEN>' user='<HIDDEN>' host='<HIDDEN>' port='5432' password=<HIDDEN>: connection to server at "<HIDDEN>" (<HIDDEN>), port <HIDDEN> failed: could not open certificate file "/root/.postgresql/postgresql.crt": Permission denied
connection to server at "<HIDDEN>" (<HIDDEN>), port <HIDDEN> failed: FATAL: pg_hba.conf rejects connection for host "<HIDDEN>", user "<HIDDEN>", database "<HIDDEN>", no encryption
```
An educated guess is that in an update to libpq an exception is now generated if it unable to determine if client authentication is needed (by verifying the path "/root/.postgresql/postgresql.crt"). As PowerDNS runs as pdns user, it can not access this folder and SSL connectivity will fail.
A workaround has been to set PGSSLCERT envar in the dockerfile to override the default to a folder the pdns user has access to (such as /tmp).
https://www.postgresql.org/docs/current/libpq-envars.htmlPeter van DijkPeter van Dijkhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14563[GNOME] [pipewire] noise-cancellation with xiph rnnoise - pipewire fails2023-01-18T06:43:07ZBigB[GNOME] [pipewire] noise-cancellation with xiph rnnoise - pipewire failsHi!
I encouraged a bug on desktop (graphical setup) while trying to enroll xiph rnnoise noise-cancellation for video-conferencing with pipewire (and pipewire-pulse)
- Alpine: `3.17`
- Kernel: `5.15.88-0-lts`
- Gnome: `43.2`
- pipewire,...Hi!
I encouraged a bug on desktop (graphical setup) while trying to enroll xiph rnnoise noise-cancellation for video-conferencing with pipewire (and pipewire-pulse)
- Alpine: `3.17`
- Kernel: `5.15.88-0-lts`
- Gnome: `43.2`
- pipewire, pipewire-pulse: `libpipewire 0.3.60`
- Apparmor enabled: `yes`
According to https://github.com/werman/noise-suppression-for-voice I installed `rnnoise` package using apk. Then I copied and corrected my working OpenSUSE configs.
When I run pipewire as current user it fails with:
```bash
[W][01060.900867] mod.rt | [ module-rt.c: 297 translate_error()] RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
[W][01060.900885] mod.rt | [ module-rt.c: 622 set_nice()] could not set nice-level to -11: No such file or directory
[E][01060.904616] pw.module | [ impl-module.c: 279 pw_context_load_module()] No module "libpipewire-module-x11-bell" was found
[W][01060.905451] default | [ ladspa_plugin.c: 214 ladspa_handle_load_by_path()] cannot find descriptor function in '/usr/lib/librnnoise.so.0': Symbol not found: ladspa_descriptor
[E][01060.905466] default | [ ladspa_plugin.c: 272 load_ladspa_plugin()] failed to load plugin '/usr/lib/librnnoise.so.0': Function not implemented
[E][01060.905475] mod.filter-chain | [module-filter-ch: 2293 pipewire__module_init()] can't load graph: Function not implemented
[E][01060.905495] pw.conf | [ conf.c: 594 load_module()] 0x7fe7dc26e040: could not load mandatory module "libpipewire-module-filter-chain": Function not implemented
[E][01060.905797] default | [ pipewire.c: 125 main()] failed to create context: Function not implemented
```
If I remember correctly, I had similar bug on Void Linux.
Could you help me?
Here is my: `~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf`
```conf
context.modules = [
{ name = libpipewire-module-filter-chain
args = {
node.description = "Noise Canceling source"
media.name = "Noise Canceling source"
filter.graph = {
nodes = [
{
type = ladspa
name = rnnoise
plugin = /usr/lib/librnnoise.so.0
label = noise_suppressor_mono
control = {
"VAD Threshold (%)" = 50.0
"VAD Grace Period (ms)" = 200
"Retroactive VAD Grace (ms)" = 0
}
}
]
}
capture.props = {
node.name = "capture.rnnoise_source"
node.passive = true
audio.rate = 48000
}
playback.props = {
node.name = "rnnoise_source"
media.class = Audio/Source
audio.rate = 48000
}
}
}
]
```
Here is my: `/etc/pipewire/pipewire-pulse.conf`
```conf
# PulseAudio config file for PipeWire version "0.3.49" #
#
# Copy and edit this file in /etc/pipewire for system-wide changes
# or in ~/.config/pipewire for local changes.
#
# It is also possible to place a file with an updated section in
# /etc/pipewire/pipewire-pulse.conf.d/ for system-wide changes or in
# ~/.config/pipewire/pipewire-pulse.conf.d/ for local changes.
#
context.properties = {
## Configure properties in the system.
#mem.warn-mlock = false
#mem.allow-mlock = true
#mem.mlock-all = false
#log.level = 2
#default.clock.quantum-limit = 8192
}
context.spa-libs = {
audio.convert.* = audioconvert/libspa-audioconvert
support.* = support/libspa-support
}
context.modules = [
{ name = libpipewire-module-rt
args = {
nice.level = -11
#rt.prio = 88
#rt.time.soft = -1
#rt.time.hard = -1
}
flags = [ ifexists nofail ]
}
{ name = libpipewire-module-protocol-native }
{ name = libpipewire-module-client-node }
{ name = libpipewire-module-adapter }
{ name = libpipewire-module-metadata }
{ name = libpipewire-module-protocol-pulse
args = {
# contents of pulse.properties can also be placed here
# to have config per server.
}
}
]
# Extra modules can be loaded here. Setup in default.pa can be moved here
context.exec = [
{ path = "pactl" args = "load-module module-always-sink" }
#{ path = "pactl" args = "load-module module-switch-on-connect" }
#{ path = "/usr/bin/sh" args = "~/.config/pipewire/default.pw" }
]
stream.properties = {
#node.latency = 1024/48000
#node.autoconnect = true
resample.quality = 15
#channelmix.normalize = false
#channelmix.mix-lfe = false
#channelmix.upmix = true
#channelmix.upmix-method = simple # none, psd
#channelmix.lfe-cutoff = 120
#channelmix.fc-cutoff = 6000
#channelmix.rear-delay = 12.0
#channelmix.stereo-widen = 0.1
#channelmix.hilbert-taps = 0
}
pulse.properties = {
# the addresses this server listens on
server.address = [
"unix:native"
#"unix:/tmp/something" # absolute paths may be used
#"tcp:4713" # IPv4 and IPv6 on all addresses
#"tcp:[::]:9999" # IPv6 on all addresses
#"tcp:127.0.0.1:8888" # IPv4 on a single address
#
#{ address = "tcp:4713" # address
# max-clients = 64 # maximum number of clients
# listen-backlog = 32 # backlog in the server listen queue
# client.access = "restricted" # permissions for clients
#}
]
#pulse.min.req = 256/48000 # 5ms
#pulse.default.req = 960/48000 # 20 milliseconds
#pulse.min.frag = 256/48000 # 5ms
#pulse.default.frag = 96000/48000 # 2 seconds
#pulse.default.tlength = 96000/48000 # 2 seconds
#pulse.min.quantum = 256/48000 # 5ms
#pulse.default.format = F32
#pulse.default.position = [ FL FR ]
default.clock.rate = 48000
default.clock.allowed-rates = [ 44100 48000 88200 96000 192000 ]
# These overrides are only applied when running in a vm.
vm.overrides = {
pulse.min.quantum = 1024/48000 # 22ms
}
}
# client/stream specific properties
pulse.rules = [
{
matches = [
{
# all keys must match the value. ~ starts regex.
#client.name = "Firefox"
#application.process.binary = "teams"
#application.name = "~speech-dispatcher.*"
}
]
actions = {
update-props = {
#node.latency = 512/48000
}
# Possible quirks:"
# force-s16-info forces sink and source info as S16 format
# remove-capture-dont-move removes the capture DONT_MOVE flag
#quirks = [ ]
}
}
{
# skype does not want to use devices that don't have an S16 sample format.
matches = [
{ application.process.binary = "teams" }
{ application.process.binary = "skypeforlinux" }
]
actions = { quirks = [ force-s16-info ] }
}
{
# firefox marks the capture streams as don't move and then they
# can't be moved with pavucontrol or other tools.
matches = [ { application.process.binary = "firefox" } ]
actions = { quirks = [ remove-capture-dont-move ] }
}
{
# speech dispatcher asks for too small latency and then underruns.
matches = [ { application.name = "~speech-dispatcher*" } ]
actions = {
update-props = {
pulse.min.req = 1024/48000 # 21ms
pulse.min.quantum = 1024/48000 # 21ms
}
}
}
]
```
Thanks for creating Alpine Linux, I love it on desktop, mobile (postmarketOS) and server :heart: !https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10870Cannot install packages with symlinks to FAT32 filesystems2023-01-16T17:14:39ZPatrycja Rosaalpine@ptrcnull.meCannot install packages with symlinks to FAT32 filesystemsin my specific case, having EFI system partition mounted at `/boot` and installing a package like `main/xen-hypervisor` fails on `symlinkat("xen-4.17.0.gz", 3, "boot/.apk...") = -1 EPERM` called from [here][1]
*technically* that's not a...in my specific case, having EFI system partition mounted at `/boot` and installing a package like `main/xen-hypervisor` fails on `symlinkat("xen-4.17.0.gz", 3, "boot/.apk...") = -1 EPERM` called from [here][1]
*technically* that's not an issue with apk itself - the package literally has a symlink and apk is just trying to do its job - but it would be nice if there was some kind of a workaround for it (or maybe a more helpful error message)
[1]: https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/v2.12.10/src/io_archive.c#L382https://gitlab.alpinelinux.org/alpine/aports/-/issues/14556main/nodejs: consider unbundling shared js builtins2023-01-15T19:39:43ZJakub Jirutkamain/nodejs: consider unbundling shared js builtinsSee https://github.com/nodejs/node/pull/44376See https://github.com/nodejs/node/pull/44376Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/10090Move config directory to $XDG_CONFIG_HOME2023-01-12T11:08:15ZNatanael CopaMove config directory to $XDG_CONFIG_HOMEWe should move the `~/.abuild` to `~/.config/abuild`. (using `$XDG_CONFIG_HOME`)
We should also have a fallback to `~/.abuild` with a deprecation warning, but we should not auto-migrate it for the user.
If both exists, the deprecated `...We should move the `~/.abuild` to `~/.config/abuild`. (using `$XDG_CONFIG_HOME`)
We should also have a fallback to `~/.abuild` with a deprecation warning, but we should not auto-migrate it for the user.
If both exists, the deprecated `~/.abuild` should be ignored, with a warning.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14552community/ltunify, testing/solaar: conflicting udev rules file2023-06-03T21:28:59ZPatrycja Rosaalpine@ptrcnull.mecommunity/ltunify, testing/solaar: conflicting udev rules filea4b0bd510f88d8a7d6d07614d20a667b0c51e0e1 moved Solaar udev rules to /lib/udev, which is already the location of rules from ltunify; currently installing both packages on edge results in a conflict
@antoni.aloytorrens as a maintainer of ...a4b0bd510f88d8a7d6d07614d20a667b0c51e0e1 moved Solaar udev rules to /lib/udev, which is already the location of rules from ltunify; currently installing both packages on edge results in a conflict
@antoni.aloytorrens as a maintainer of ltunify, i suggest moving the rules to a separate package in community (`logitech-udev`? looks like some packages already use that naming scheme) or making solaar depend on a subpackage separated from ltunify, like `ltunify-udev`. what do you think about this?https://gitlab.alpinelinux.org/alpine/aports/-/issues/14549Cannot configure IPv6 route2023-01-17T05:36:57Zsaur0nCannot configure IPv6 routeTo reproduce the error, add IPv6 configuration to /etc/network/interfaces:
```
auto eth0
iface eth0 inet6 static
address 2606:8001:c845:9c54::1/112
gateway 2606:8001:c845::1
```
Note that IPs in the listing above are fictional.
...To reproduce the error, add IPv6 configuration to /etc/network/interfaces:
```
auto eth0
iface eth0 inet6 static
address 2606:8001:c845:9c54::1/112
gateway 2606:8001:c845::1
```
Note that IPs in the listing above are fictional.
On `service networking start` the following error happens, and networking is not started:
```
RTNETLINK answers: Host is unreachable
```
The problem was not solved by installing `iproute2-minimal`, because the root reason of the problem is inside `ifup`.
The error happend because `ifup` tries to add default route with command `ip -6 route add default via 2606:8001:c845::1 metric 1 dev eth0`, however route for gateway does not exist. As a result, Linux kernel rejects this command. To fix this behaviour, command `ip -6 route add 2606:8001:c845::1 dev eth0` should be executed by ifup before adding default route.
The buggy script is located here: https://github.com/ifupdown-ng/ifupdown-ng/blob/main/executor-scripts/linux/statichttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14548KDE plasma-nm keeps displaying disconnected icon2023-01-30T19:37:42ZJan JacobsKDE plasma-nm keeps displaying disconnected iconI am trying to setup Wireless networking as per: https://wiki.alpinelinux.org/wiki/NetworkManager
However, plasma-nm keeps showing there is no network connected. It also won't show any wifi networks to connect to. nmtui shows its connec...I am trying to setup Wireless networking as per: https://wiki.alpinelinux.org/wiki/NetworkManager
However, plasma-nm keeps showing there is no network connected. It also won't show any wifi networks to connect to. nmtui shows its connected just fine. I tried networkmanager/wpa_supplicant as well as networkmanager/iwd, but nothing seems to work. The wiki mentions if everything works i can disable networking in rc, however when i do: "rc-update del networking boot" then i wont be able to connect anymore.
I have the following networkmanager packages installed:
networkmanager-wwan, networkmanager-qt, network-extras, networkmanager, networkmanager-cli, networkmanager-bluetooth, networkmanager-common, networkmanager-elogind, networkmanager-initrd-generator, networkmanager-lang, networkmanager-openrc, networkmanager-tui, networkmanager-wifi, wpa_supplicanthttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14545Package request: Apache Directory Studio2023-01-10T13:08:39ZPatrycja Rosaalpine@ptrcnull.mePackage request: Apache Directory StudioEclipse-based LDAP browser and directory client
https://directory.apache.org/studio/Eclipse-based LDAP browser and directory client
https://directory.apache.org/studio/https://gitlab.alpinelinux.org/alpine/aports/-/issues/14541udhcpc clears out static IPs2023-01-13T14:01:30ZSam Dieckudhcpc clears out static IPsI have a backup server at home with multiple IP addresses as follows:
```
auto eth0
iface eth0 inet dhcp
auto eth0:0
iface eth0:0 inet static
address 192.168.2.2/24
```
I works most of the time, but every once in a while the static...I have a backup server at home with multiple IP addresses as follows:
```
auto eth0
iface eth0 inet dhcp
auto eth0:0
iface eth0:0 inet static
address 192.168.2.2/24
```
I works most of the time, but every once in a while the static IP is not present, I think its because udhcpc is flushing the static ip.
Also running something like `udhcpc -i eth0` flushes the static ip, which I think its happening on dhcp renew.
What is the recomended way to reliably keep a static address along-side the dhcp config?
Thanks!Sören TempelSören Tempelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14535[Package Request] Onlyoffice Desktop Editors2023-01-08T15:49:49ZShubham[Package Request] Onlyoffice Desktop EditorsOnlyoffice is a famous office suite for linux.
link to the project: https://github.com/ONLYOFFICE/DesktopEditorsOnlyoffice is a famous office suite for linux.
link to the project: https://github.com/ONLYOFFICE/DesktopEditorshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14531[Feature request] Add broadcom-wl driver to installer image2023-01-07T16:10:52ZCoco Liliacecoco@liliace.dev[Feature request] Add broadcom-wl driver to installer imageThe early 2015 model of MacBook Air uses the `14e4:43a0 BCM4360` firmware, which is [not supported by the b43/b43legacy driver](http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/). It requires the [broadcom-wl](https://github.co...The early 2015 model of MacBook Air uses the `14e4:43a0 BCM4360` firmware, which is [not supported by the b43/b43legacy driver](http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/). It requires the [broadcom-wl](https://github.com/antoineco/broadcom-wl) driver.
I've been trying to add it into the installer image myself but to no avail. It'd be really helpful if it could be added upstream to help us MacBook users.
I've tried using another usb stick during installation and copying the driver to `/lib/modules/$(uname -r)/kernal/drivers/net/wireless/broadcom/wl.ko` but I got a "file system is readonly" error.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14525Problem with rxvt-unicode after upgrade to 9.31-r02023-01-21T17:54:47ZMogens JensenProblem with rxvt-unicode after upgrade to 9.31-r0After upgrading rxvt-unicode to 9.31-r0, several empty lines are now present at the top when opening a new terminal:
```
mogensj@localhost:~$
```
Normally no empty lines are present:
```
mogensj@localhost:~$
```
This is on the dwm ...After upgrading rxvt-unicode to 9.31-r0, several empty lines are now present at the top when opening a new terminal:
```
mogensj@localhost:~$
```
Normally no empty lines are present:
```
mogensj@localhost:~$
```
This is on the dwm window manager.
Anyone have an idea what could cause this?https://gitlab.alpinelinux.org/alpine/aports/-/issues/14521Alpine LXC USB passthrough no user assigned2023-06-22T21:54:36ZDavid HabernigAlpine LXC USB passthrough no user assignedI want to use an alpine-LXC on my Proxmox-Homeserver to serve CUPS in my Home-Nework.
Alpine runs as an unprivileged LXC, the Printer is attached via USB.
Proxmox is configured as follows:
```
root@pve:~# lsusb
Bus 001 Device 007: ID 03...I want to use an alpine-LXC on my Proxmox-Homeserver to serve CUPS in my Home-Nework.
Alpine runs as an unprivileged LXC, the Printer is attached via USB.
Proxmox is configured as follows:
```
root@pve:~# lsusb
Bus 001 Device 007: ID 03f0:142a HP, Inc HP LaserJet 400 MFP M425dn
root@pve:~# exa -lgTh /dev/bus/
Permissions Size User Group Date Modified Name
drwxr-xr-x - root root 9 Dec 2022 /dev/bus
drwxr-xr-x - root root 9 Dec 2022 └── usb
drwxr-xr-x - root root 4 Jan 13:43 ├── 001
crw-rw-r-- 189,6 root lp 4 Jan 13:43 │ └── 007
root@pve:~# tail -n 4 /etc/pve/lxc/105.conf
unprivileged: 1
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/bus/usb dev/bus/usb none bind,optional,create=dir
lxc.mount.entry: /dev/usb/lp0 dev/usb/lp0 none bind,optional,create=file
```
For the Alpine-LXC config, i have more or less followed the wiki [https://wiki.alpinelinux.org/wiki/Printer_Setup](https://wiki.alpinelinux.org/wiki/Printer_Setup).
When entering the Container, the Printer is visible but doesn't have the right ownership.
```
~ # lsusb
Bus 001 Device 007: ID 03f0:142a Hewlett-Packard HP LaserJet 400 MFP M425dn
~ # exa -lgTh /dev/bus/
Permissions Size User Group Date Modified Name
drwxr-xr-x - root root 4 Jan 15:18 /dev/bus
drwxr-xr-x - nobody nobody 9 Dec 2022 └── usb
drwxr-xr-x - nobody nobody 4 Jan 12:43 ├── 001
crw-rw-r-- 189,6 nobody nobody 4 Jan 12:43 │ └── 007
~ # exa -lgTh /dev/usb/
Permissions Size User Group Date Modified Name
drwxr-xr-x - root root 4 Jan 15:18 /dev/usb
crw-rw---- 180,0 nobody nobody 4 Jan 12:43 └── lp0
```
As you can see, the mounted devices are owned by *nobody*, thus unreachable for CUPS.
As in the wiki, I have added the following lines to */etc/mdev.conf*:
```
~ # grep 'root:lp' /etc/mdev.conf
SUBSYSTEM=usb;PRODUCT=3f0/142a/100;.* root:lp 660 */lib/mdev/usbdev
```
which didn't change the ownership issue.
Can anyone more familiar with Containers and/or mdev help me?https://gitlab.alpinelinux.org/alpine/aports/-/issues/14510openrc: cache update issue (clock skew)2023-01-02T00:01:09Zvoroskoiopenrc: cache update issue (clock skew)Hi,
I would like to start containers with podman at system startup. I have more or less followed this tutorial: https://virtualzone.de/posts/openrc-podman-kube-play/
After reboot, the services do not start. I have noticed, that openrc ...Hi,
I would like to start containers with podman at system startup. I have more or less followed this tutorial: https://virtualzone.de/posts/openrc-podman-kube-play/
After reboot, the services do not start. I have noticed, that openrc does not even pick up my services at all. When I run `rc-status default` the scripts are missing from the list.
Running `doas openrc default` give clock skew error. I think that is the root cause of this issue. When I force updating the cache with `rc-update -u` the services pop up in the status list and I can start them without any problem. Unfortunately restarting makes the cache update go away.
Can I force an `rc-update -u` on every startup, or is there a better way of solving this clock skew issue?
This is a rpi4 (aarch64 Alpine Edge) with swclock service enabled at boot level.
Thanks,https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10089Output for "not available for the target architecture" missing the relevant p...2022-12-29T09:58:49ZraksliceOutput for "not available for the target architecture" missing the relevant package name`abuild` output for the `not available for the target architecture` case is missing the name of the relevant package leading to confusing output.
e.g.
```
$ scripts/bootstrap.sh x86
[... snip ...]
>>> curl: Package is up to date
>>> pcr...`abuild` output for the `not available for the target architecture` case is missing the name of the relevant package leading to confusing output.
e.g.
```
$ scripts/bootstrap.sh x86
[... snip ...]
>>> curl: Package is up to date
>>> pcre: Package is up to date
>>> libssh2: Package is up to date
>>> libxml2: Package is up to date
>>> pax-utils: Package is up to date
>>> llvm14: Package is up to date
Package not available for the target architecture (x86). Aborting.
>>> llvm15: Package is up to date
>>> rust: Building community/rust 1.66.0-r0 (using abuild 3.10.0-r0) started Thu, 29 Dec 2022 09:31:50 +0000
[... snip ...]
```
The package not available for the target architecture here is actually `ghc` (which isn't mentioned, but I can figure it out in this case by reading the `for` loop in `bootstrap.sh`). This output is confusing.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14506Package request: dkimpy-milter2023-09-27T04:05:37ZJeremy SakladPackage request: dkimpy-milterhttps://launchpad.net/dkimpy-milter
OpenDKIM and DKIMProxy both seem to be abandoned, and neither is capable of signing with ed25519 and RSA simultaneously as recommended by [RFC 8463](https://www.rfc-editor.org/rfc/rfc8463). dkimpy-mil...https://launchpad.net/dkimpy-milter
OpenDKIM and DKIMProxy both seem to be abandoned, and neither is capable of signing with ed25519 and RSA simultaneously as recommended by [RFC 8463](https://www.rfc-editor.org/rfc/rfc8463). dkimpy-milter is the best option I've found that is actually capable of doing this.Simon Fsimon-alpine@fraho.euSimon Fsimon-alpine@fraho.euhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14505acpid echoes "?" to console with any KEY_BRIGHTNESSUP or KEY_BRIGHTNESSDOWN p...2022-12-28T05:24:13ZPaul W. Rankinhello@paulwrankin.comacpid echoes "?" to console with any KEY_BRIGHTNESSUP or KEY_BRIGHTNESSDOWN press`acpid(man page missing)` echoes "?" to console with any `KEY_BRIGHTNESSUP` or `KEY_BRIGHTNESSDOWN` press.
Provided a minimal `/etc/acpi.map`:
```
# FORMAT: "<EV_XXX>" <type> "<input.h name>" <keycode> <value> <script under /etc/acpi>
...`acpid(man page missing)` echoes "?" to console with any `KEY_BRIGHTNESSUP` or `KEY_BRIGHTNESSDOWN` press.
Provided a minimal `/etc/acpi.map`:
```
# FORMAT: "<EV_XXX>" <type> "<input.h name>" <keycode> <value> <script under /etc/acpi>
# hint: "evtest /dev/input/eventX" is very helpful!
"EV_KEY" 0x01 "KEY_BRIGHTNESSUP" 225 1 dummy
"EV_KEY" 0x01 "KEY_BRIGHTNESSDOWN" 224 1 dummy
```
With contents of `/etc/acpi/dummy`:
```
#!/bin/sh
true
```
On each keypress, console will echo "?". Annoying.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14503Problem creating a custom ISO with a custom kernel2022-12-27T18:24:13ZfijamProblem creating a custom ISO with a custom kernelI'm having trouble creating a custom bootable ISO with a custom kernel.
Steps taken:
1. Started an aarch64 Alpine EC2 instance
2. Cloned aports, followed the steps in https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package#Setup_yo...I'm having trouble creating a custom bootable ISO with a custom kernel.
Steps taken:
1. Started an aarch64 Alpine EC2 instance
2. Cloned aports, followed the steps in https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package#Setup_your_system_and_account
3. Checked out 3.17 branch
4. Modified lts.aarch64.config, bumped pkgrel to 1, updated checksums, built the new kernel with the required modules with abuild
5. Run
```
./aports/scripts/mkimage.sh --arch aarch64 --outdir ~/build --profile standard --repository /home/alpine/packages/main --re
pository http://dl-cdn.alpinelinux.org/alpine/v3.17/main --hostkeys --tag v3.17
```
I would expect the script to pull the updated kernel (with pkgrel=1) from the local repository and the other required apks from the remote repo (this is what https://wiki.alpinelinux.org/wiki/How_to_make_a_custom_ISO_image_with_mkimage suggests) but that's not what happens - all the files including the kernel (with pkgrel=0)are pulled from the remote repo instead.
Did I miss a step somewhere?