aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2020-06-19T19:57:15Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11669dhcp packet causes invalid mac address for host in arp cache, in virtualbox o...2020-06-19T19:57:15ZGKdhcp packet causes invalid mac address for host in arp cache, in virtualbox on natnetwork, can't ssh host/cifs
Unsure if this affects alpine only or in general to busybox
Its not clear to me what OS should do when a host and DHCP server share an ip-address but have different MAC-address. Fedora/gparted seems resilient to this issue as it has n...
Unsure if this affects alpine only or in general to busybox
Its not clear to me what OS should do when a host and DHCP server share an ip-address but have different MAC-address. Fedora/gparted seems resilient to this issue as it has not be encountered before with them
## Setup
* alpine-3.12 guest in Virtualbox-6.10 in Win 10 (2020.4) host
- VBOX-emulated NAT (10.1.WW.x) with VBOX emulated NAT services, (1 eth0).
This is not the "NAT" adapter but the "NATNetwork" adaptor. The "NAT Network" name is "NatNetworkWW". Then "NatNetworkWW" is configured for host forwarding in VBOX common tools preferences/network.
- smb/cifs shared folder from host, mounted using cifs-utils in alpine
- VBOX emulated network card (intel-pro/virtio-net) does not matter
- kernel linux-lts/linux-virt does not matter
## Symptom
Guest terminal is accessed via VBOX GUI.
* ssh to host from inside guest stops working. Also, new ssh connections cannot be made.
* CIFS/SMB df command, freezes for ~2min on the line of cifs-mount, omits/skips line of the mount
* ls /mnt/sharedir command freeze for ~2min without output
* The invalid arp entry uses a Virtualbox internal MAC address 08:00:27.x.y.z, hinting at a VBOX service such as DHCP-server
Virtualbox, by default, emulates a gateway on 10.1.WW.1, host on 10.1.WW.2, dhcp-server on 10.1.WW.2, first issued IP address is 10.1.WW.15
## Resolution
* one way resolve the problem is to issue "arp -d 10.1.WW.2" and retry commands/connection. After the entry is purged, the issue is temporarily resolved. The spoilt arp/issue reappears within a few minutes.
* final resolution:
The solution was to modify C:\Users\Admin\\.Virtualbox\Virtualbox.xml and change the emulated DHCP address from 10.1.WW.2 to a different IP 10.1.WW.5 and the DHCP range lower-IP-setting to 10.1.WW.15
### debug logs when ssh to host/smb working
```
# # notice that below the arp MAC-Adresses are the same
# arp -a
zzzhost (10.1.WW.2) at 52:XX:54:XX:35:00 [ether] on eth0
? (10.1.WW.1) at 52:XX:54:XX:35:00 [ether] on eth0
# ip route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.WW.1 0.0.0.0 UG 202 0 0 eth0
10.1.WW.0 * 255.255.255.0 U 0 0 0 eth0
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether ZZ:ZZ:9c:b5:2c:14 brd ff:ff:ff:ff:ff:ff
inet 10.1.WW.15/24 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::13:9cff:feb5:xxxx/64 scope link
valid_lft forever preferred_lft forever
```
### debug logs when ssh to host/smb NOT working
```
# # notice the spurious MAC-Adress for host
zzzhost (10.1.WW.2) at 08:00:27:f9:07:98 [ether] on eth0
? (10.1.WW.1) at 52:XX:54:XX:35:00 [ether] on eth0
# ip route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.WW.1 0.0.0.0 UG 202 0 0 eth0
10.1.WW.0 * 255.255.255.0 U 0 0 0 eth0
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether ZZ:ZZ:9c:b5:2c:14 brd ff:ff:ff:ff:ff:ff
inet 10.1.WW.15/24 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::13:9cff:feb5:xxxx/64 scope link
valid_lft forever preferred_lft forever
```
### debug logs after resolution
notice the the dhcp-server mac has its own ip-address 10.1.WW.5
```
# arp -a
? (10.1.WW.1) at 52:XX:54:XX:35:00 [ether] on eth0
? (10.1.WW.5) at 08:00:27:9e:52:85 [ether] on eth0
zzzhost (10.1.WW.2) at 52:XX:54:XX:35:00 [ether] on eth0
```
* on boot/login, MAC entry for zzzhost 10.1.WW.2 exists from the beginning
* the MAC entry for gateway 10.1.WW.1 appears after a wget of any webpage
* the MAC entry for dhcpserver 10.1.WW.5 appears after a few minutes
* CIFS/ssh is unaffected no matter the uptime
Also created vbox ticket
https://www.virtualbox.org/ticket/19675
https://gitlab.alpinelinux.org/alpine/aports/-/issues/11673main/grub: grub.trigger fails after apk add2020-06-22T04:37:48Zc705main/grub: grub.trigger fails after apk addHi, running latest edge release "from ram" i.e: from a live iso:
```
Linux alpine 5.4.47-0-lts #1-Alpine SMP Thu, 18 Jun 2020 14:54:31 UTC x86_64 Linux
3.12.0
```
Been having this problem for a week or so now
```
76bc[~]$ sudo apk del...Hi, running latest edge release "from ram" i.e: from a live iso:
```
Linux alpine 5.4.47-0-lts #1-Alpine SMP Thu, 18 Jun 2020 14:54:31 UTC x86_64 Linux
3.12.0
```
Been having this problem for a week or so now
```
76bc[~]$ sudo apk del grub ; sudo apk add grub
(1/1) Purging grub (2.04-r2)
Executing busybox-1.31.1-r21.trigger
OK: 1589 MiB in 484 packages
(1/1) Installing grub (2.04-r2)
Executing busybox-1.31.1-r21.trigger
Executing grub-2.04-r2.trigger
/usr/sbin/grub-probe: error: failed to get canonical path of `tmpfs'.
ERROR: grub-2.04-r2.trigger: script exited with error 1
OK: 1601 MiB in 485 packages
```
Seems the post trigger is borked:
Workaround:
```
76bc[~]$ sudo apk add --no-scripts grub
(1/1) Installing grub (2.04-r2)
OK: 1601 MiB in 485 packages
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/11683cross-compile rust2020-06-24T14:14:44ZAriadne Conillariadne@ariadne.spacecross-compile rustThis issue is tracking discussion & whatever we need to do to make rust cross-compile using the `$CTARGET` variable.
cc @CogitriThis issue is tracking discussion & whatever we need to do to make rust cross-compile using the `$CTARGET` variable.
cc @Cogitrihttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11718main/ldb: test failures on ppc64le2020-07-17T04:52:56ZKevin Daudtmain/ldb: test failures on ppc64leAfter upgrading to [v2.1.4](4f5db102), ldb has [test failures](https://build.alpinelinux.org/buildlogs/build-edge-ppc64le/main/ldb/ldb-2.1.4-r0.log) on ppc64le
```
Failed to connect to 'mdb://lmdb_free_list_test.ldb' with backend 'mdb':...After upgrading to [v2.1.4](4f5db102), ldb has [test failures](https://build.alpinelinux.org/buildlogs/build-edge-ppc64le/main/ldb/ldb-2.1.4-r0.log) on ppc64le
```
Failed to connect to 'mdb://lmdb_free_list_test.ldb' with backend 'mdb': Unable to load ltdb cache records for backend 'ldb_mdb backend'
Could not run test: 0x1 != 0
[..]
Could not run test: 0x1 != 0
[ LINE ] --- ../../tests/ldb_lmdb_free_list_test.c:165: error: Failure!Test setup failed
```LeoLeohttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11738Package mariadb scripts have bash shebang2020-07-17T11:11:22ZGhost UserPackage mariadb scripts have bash shebangHi,
the following by package mariadb provided scripts have a **bash shebang**.
The package doesn't have a bash dependency.
usr/bin/wsrep_sst_mariabackup
usr/bin/wsrep_sst_mysqldump
usr/bin/wsrep_sst_rsync
usr/bin/wsrep_sst_rsyn...Hi,
the following by package mariadb provided scripts have a **bash shebang**.
The package doesn't have a bash dependency.
usr/bin/wsrep_sst_mariabackup
usr/bin/wsrep_sst_mysqldump
usr/bin/wsrep_sst_rsync
usr/bin/wsrep_sst_rsync_wan
What do you mostly do? Add a **bash dependency** or change the shebang to **/bin/sh and fixing bashism**?
Markushttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11834Supporting Multiboot USB Thumb drives2020-08-11T10:53:26ZJerome Landsman Supporting Multiboot USB Thumb drivesProjects like [GLIM](https://github.com/thias/glim/) enable users to create a
MultiBoot USB stick which boot into any one of several distros chosen by the
user.
It work by having the user place one or more Bootable ISOs in a special
dir...Projects like [GLIM](https://github.com/thias/glim/) enable users to create a
MultiBoot USB stick which boot into any one of several distros chosen by the
user.
It work by having the user place one or more Bootable ISOs in a special
directory. Then, GRUB2 scripts provided (by GLIM for example) dynamically
generate menus for the available ISO files. It's extremely convenient for
creating rescue thumb drives, or just keeping all the distros you care about
easily accessible.
Practically all major distros are supported by such projects, including
Ubuntu, Debian, Fedora, Mint, and Arch, etc'. Alpine Linux is currently
missing some simple pieces needed to support it.
To be supported, a distro must expose some basic boot param so that grub can
tell the init process where the ISO file is located. The init script of course
also has to handle this case when the boot param is provided.
I've created a customized init script which implements this. The changes are
quite small. I've tested it by replacing the init script inside
`alpine-standard-3.12.0-x86.iso` and adding a grub script to GLIM which adds
support for Alpine.
The changes from the alpine side cinsist of two new boo params `img_dev` and `img_file` (same as Arch). When passed by grub on the kernel command line, th e init scripts mounts `img_dev` and then loop
mount the `img_file` iso file on it. So, for example, I have
`img_dev=/dev/usbdisk` and `img_file=/boot/iso/alpine/alpine-standard-3.12.0-x86.iso`.
Included are:
1) The modified init script. Changed are marked by `XXX` (3 locations).
2) The grub2 script, for use with GLIM
3) A .png icon for use with GLIM's theme.
only (1) is relevant to Alpine developers, but since users may be interested
in reproducing this immediately, I've included the GLIM files as well.
Attached:
1. [init V3](/uploads/ad8b4c576fef14fa9c361d33c815bfdc/init)
2. [inc-alpine.cfg](/uploads/018fbfcc10abf6e1c6cddc6284174424/inc-alpine.cfg)
3. [alpine.png](/uploads/d20ebb72382f17fd85ce597ee77eb712/alpine.png)https://gitlab.alpinelinux.org/alpine/aports/-/issues/11837cfengine incosistent config dir names2020-08-11T14:24:33ZEleksircfengine incosistent config dir namesThere are 2 dirs that contains cfengine configs: cfengine and libntech.
```
root@cfe-client1:/var/lib# ls -l
total 20
drwxr-xr-x 2 root root 4096 May 29 17:20 apk
drwxr-xr-x 9 root root 4096 Aug 10 22:58 ...There are 2 dirs that contains cfengine configs: cfengine and libntech.
```
root@cfe-client1:/var/lib# ls -l
total 20
drwxr-xr-x 2 root root 4096 May 29 17:20 apk
drwxr-xr-x 9 root root 4096 Aug 10 22:58 cfengine
drwxr-xr-x 11 root root 4096 Aug 10 23:00 libntech
drwxr-xr-x 2 root root 4096 May 29 17:20 misc
drwxr-xr-x 2 root root 4096 May 29 17:20 udhcpd
```
In many installs there is only one dir here **/var/cfengine** (or /var/lib/cfengine) and no /var/lib/libntech. And because of specific way how cfengine handles its configs and evaluate it' variables on agent side i'm unable to run server, say, on centos7 or slackware and manage alpine boxes as clients for this server. In some random places of "promises" where evaluation happen on client side i've got an errors. So cfengine package on alpine can be considered as broken.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11842feat: plank: a simple dock2020-08-14T06:47:47Zsaltedcoffiifeat: plank: a simple dockPlease make and add apk files for plank, plank-docklets and dependences. Plank is a simple dock. Currently incompatible with wayland.
https://github.com/ricotz/plank
https://launchpad.net/plank
Plank requires dependencies some of whi...Please make and add apk files for plank, plank-docklets and dependences. Plank is a simple dock. Currently incompatible with wayland.
https://github.com/ricotz/plank
https://launchpad.net/plank
Plank requires dependencies some of which don't have apk files. I've identified one, bamf:
https://git.launchpad.net/bamf
https://launchpad.net/bamf
Thank you :)https://gitlab.alpinelinux.org/alpine/aports/-/issues/11867testing/perl-io-socket-timeout: test failures on x86, armv72020-08-18T16:35:16ZKevin Daudttesting/perl-io-socket-timeout: test failures on x86, armv7This package has test failures on armv7 and x86
```
# Failed test 'No tests run for subtest "test with no delays and no timeouts"'
# at t/timeout_setsockopt.t line 30.
setsockopt(SO_RCVTIMEO): Invalid argument at /home/buildozer/apo...This package has test failures on armv7 and x86
```
# Failed test 'No tests run for subtest "test with no delays and no timeouts"'
# at t/timeout_setsockopt.t line 30.
setsockopt(SO_RCVTIMEO): Invalid argument at /home/buildozer/aports/testing/perl-io-socket-timeout/src/IO-Socket-Timeout-0.32/blib/lib/IO/Socket/Timeout.pm line 46.
```
It has been disabled for now.
See: https://build.alpinelinux.org/buildlogs/build-edge-x86/testing/perl-io-socket-timeout/perl-io-socket-timeout-0.32-r0.loghttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11907weston: system freeze on launch2020-09-01T13:34:45Zshumweston: system freeze on launch`Alpine Edge, x86_64`
Weston freezes the system upon launch with `weston-launch`.
Steps to reproduce:
1. `apk add weston weston-backend-drm weston-shell-desktop weston-xwayland weston-clients`
2. `addgroup $(whoami) weston-launch`
3. D...`Alpine Edge, x86_64`
Weston freezes the system upon launch with `weston-launch`.
Steps to reproduce:
1. `apk add weston weston-backend-drm weston-shell-desktop weston-xwayland weston-clients`
2. `addgroup $(whoami) weston-launch`
3. Do not forget to [set XDG_RUNTIME_DIR](https://wiki.alpinelinux.org/wiki/Wayland).
4. Logout from your session and log back in.
5. Run `weston-launch 2> 1.log` from TTY.
After this, system just hangs. To unfreeze the system, one can switch to another TTY and kill the weston process.
The thing is – `sway` starts perfectly fine.
Here is a log file from fifth step: [1.log](/uploads/d89952d72c7d8bc6217787e1731082f2/1.log)https://gitlab.alpinelinux.org/alpine/aports/-/issues/11911Asterisk-16.7.0 crash if 'pjsip set logger on'2020-09-01T19:45:30ZHenrikAsterisk-16.7.0 crash if 'pjsip set logger on'I've experienced an issue where Asterisk exists/crashes when 'pjsip set logger on' is set in the Asterisk CLI. This happens with the asterisk-16.7.0 in alpine:3.12.0 and asterisk-15.7.4 in alpine:3.9.3. The problem occurs when the above ...I've experienced an issue where Asterisk exists/crashes when 'pjsip set logger on' is set in the Asterisk CLI. This happens with the asterisk-16.7.0 in alpine:3.12.0 and asterisk-15.7.4 in alpine:3.9.3. The problem occurs when the above is set and asterisk receives a new call. It works fine if the above is not set.
The same happens if PJSIP tries to parse a call with a faulty SIP-header so I guess it might be related. There is no error unfortunately but this is the output I get while calling to it with 'pjsip set logger on' set.
```
/ # asterisk -vvvvvvvvvvvvvvvvvvvvr
Asterisk 16.7.0, Copyright (C) 1999 - 2018, Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 16.7.0 currently running on HP-EliteBook (pid = 8)
HP-EliteBook*CLI> pjsip set logger on
PJSIP Logging enabled
HP-EliteBook*CLI>
HP-EliteBook*CLI>
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":34,"callid":""},"logmsg":{"location":{"filename":"res_pjsip_logger.c","function":"logging_on_rx_msg","line":104},"level":"VERBOSE","message":"<--- Received SIP request (474 bytes) from UDP:127.0.0.1:5061 --->\nINVITE sip:echo-bot-se@127.0.0.1:5060 SIP/2.0\r\nVia: SIP/2.0/UDP 127.0.0.1:5061\r\nFrom: sipp <sip:sipp@127.0.0.15061>;tag=1\r\nTo: echo-bot <sip:echo-bot-se@127.0.0.1:5060>\r\nCall-ID: 1-7@127.0.0.1\r\nCseq: 1 INVITE\r\nContact: sip:sipp@127.0.0.1:5061\r\nMax-Forwards: 70\r\nSubject: Performance Test\r\nContent-Type: application/sdp\r\nContent-Length: 129\r\n\r\nv=0\r\no=user1 53655765 2353687637 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\nc=IN IP4 127.0.0.1\r\nm=audio 6000 RTP/AVP 8\r\na=rtpmap:8 PCMA/8000\r\n\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":35,"callid":""},"logmsg":{"location":{"filename":"pbx_variables.c","function":"pbx_builtin_setvar_helper","line":1115},"level":"VERBOSE","message":"Setting global variable 'SIPDOMAIN' to '127.0.0.1'\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":35,"callid":""},"logmsg":{"location":{"filename":"res_pjsip_logger.c","function":"logging_on_tx_msg","line":83},"level":"VERBOSE","message":"<--- Transmitting SIP response (263 bytes) to UDP:127.0.0.1:5061 --->\nSIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP 127.0.0.1:5061;rport=5061;received=127.0.0.1\r\nCall-ID: 1-7@127.0.0.1\r\nFrom: \"sipp\" <sip:sipp@127.0.0.15061>;tag=1\r\nTo: \"echo-bot\" <sip:echo-bot-se@127.0.0.1>\r\nCSeq: 1 INVITE\r\nServer: Asterisk PBX 16.7.0\r\nContent-Length: 0\r\n\r\n\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":59,"callid":"[C-00000001]"},"logmsg":{"location":{"filename":"pbx.c","function":"pbx_extension_helper","line":2940},"level":"VERBOSE","message":"Executing [echo-bot-se@inbound:1] NoOp(\"PJSIP/anonymous-00000000\", \"\") in new stack\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":59,"callid":"[C-00000001]"},"logmsg":{"location":{"filename":"pbx.c","function":"pbx_extension_helper","line":2940},"level":"VERBOSE","message":"Executing [echo-bot-se@inbound:2] EAGI(\"PJSIP/anonymous-00000000\", \"main\") in new stack\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:01","identifiers":{"lwp":59,"callid":"[C-00000001]"},"logmsg":{"location":{"filename":"res_agi.c","function":"launch_script","line":2296},"level":"VERBOSE","message":"Launched AGI Script /var/lib/asterisk/agi-bin/main\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:02","identifiers":{"lwp":35,"callid":""},"logmsg":{"location":{"filename":"res_rtp_asterisk.c","function":"ast_rtp_remote_address_set","line":8051},"level":"VERBOSE","message":"0x557ec287c020 -- Strict RTP learning after remote address set to: 127.0.0.1:6000\n"}}
{"hostname":"","timestamp":"Sep 1 14:49:02","identifiers":{"lwp":35,"callid":""},"logmsg":{"location":{"filename":"res_pjsip_logger.c","function":"logging_on_tx_msg","line":83},"level":"VERBOSE","message":"<--- Transmitting SIP response (693 bytes) to UDP:127.0.0.1:5061 --->\nSIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 127.0.0.1:5061;rport=5061;received=127.0.0.1\r\nCall-ID: 1-7@127.0.0.1\r\nFrom: \"sipp\" <sip:sipp@127.0.0.15061>;tag=1\r\nTo: \"echo-bot\" <sip:echo-bot-se@127.0.0.1>;tag=mLJYvgSGETo4B9HLu57UOS6WrQNXN3QK\r\nCSeq: 1 INVITE\r\nServer: Asterisk PBX 16.7.0\r\nContact: <sip:127.0.0.1:5060>\r\nAllow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER\r\nSupported: 100rel, timer, replaces, norefersub\r\nContent-Type: application/sdp\r\nContent-Length: 173\r\n\r\nv=0\r\no=- 53655765 2353687639 IN IP4 127.0.0.1\r\ns=Asterisk\r\nc=IN IP4 127.0.0.1\r\nt=0 0\r\nm=audio 15670 RTP/AVP 8\r\na=rtpmap:8 PCMA/8000\r\na=ptime:20\r\na=maxptime:150\r\na=sendrecv\r\n\n
HP-EliteBook*CLI>
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups
```
With:
```
HP-EliteBook*CLI> pjsip show version
PJPROJECT version currently running against: 2.9
```Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11956vte package messes with shell config2020-09-19T19:16:28ZRich Felkervte package messes with shell configThe `vte` package installs a file in `/etc/profile.d` that switches bash from using a normal prompt to a `PROMPT_COMMAND` when `TERM` begins with `xterm` or `vte`. This is a configuration change, not something that should happen just by ...The `vte` package installs a file in `/etc/profile.d` that switches bash from using a normal prompt to a `PROMPT_COMMAND` when `TERM` begins with `xterm` or `vte`. This is a configuration change, not something that should happen just by virtue of having a package installed.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11966keymap configuration: greek keymap is broken2020-09-23T21:25:12Zcharlkeymap configuration: greek keymap is brokenAfter installing alpine with `setup-alpine` or setting up keymap during post-install with `setup-keymap` and choosing gr keymap, I'm unable to login because all I can type is Greek. There is no way to switch to English.
Looking at the s...After installing alpine with `setup-alpine` or setting up keymap during post-install with `setup-keymap` and choosing gr keymap, I'm unable to login because all I can type is Greek. There is no way to switch to English.
Looking at the setup-keymap source I see it installs `kbd-bkeymaps` which are keymaps [generated with](https://git.alpinelinux.org/aports/tree/main/kbd/APKBUILD)
```
ckbcomp "$layout" "$variant" | gzip > "$pkgdir$_xmapdir"/"$layout"-"$variant".map.gz || exit 1
```
The way I managed to get a working gr keymap was to install `kbd-legacy` and then `loadkeys /usr/share/keymaps/legacy/i386/qwerty/gr.map.gz`
This way I can type in english, switch to greek with alt+shift and accents work.
I'm also trying to generate a valid binary keymap so I can use it with busybox's `loadkmap`. This is what I tried so far:
```
foo:~/keymaps# kbd_mode
The keyboard is in Unicode (UTF-8) mode
foo:~/keymaps# setfont ter-712n
foo:~/keymaps# loadkeys /usr/share/keymaps/legacy/i386/qwerty/gr.map.gz
foo:~/keymaps# # can type in greek, accents work and can switch to en/gr with alt+shift
foo:~/keymaps# # τεστ ά έ ό ή
foo:~/keymaps# dumpkmap > gr.bmap
foo:~/keymaps# loadkeys -c us # clear compose table from kernel before trying the new bmap
foo:~/keymaps# loadkmap < gr.bmap
foo:~/keymaps# # can type in english but I get caps lock WHEN I TRY TO ALT+SHIFT
```
If I use loadkeys to generate the binary keymap, I can switch to greek with alt+shift but accents don't seem to work
```
foo:~/keymaps# loadkeys -ub /usr/share/keymaps/i386/qwerty/gr.map.gz>gr.bmap
foo:~/keymaps# loadkeys -c us
foo:~/keymaps# loadkmap < gr.bmap
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/11634community/firefox: asks to be set as default browser on every startup on KDE ...2020-10-07T20:34:19ZBart Ribberscommunity/firefox: asks to be set as default browser on every startup on KDE PlasmaEven if I tell it that it's allowed, it never actually sets itself as the default so just asks again at next startup.
I know I can stop it from asking entirely in it's settings, but I rather have it fixed so it actually knows how to set...Even if I tell it that it's allowed, it never actually sets itself as the default so just asks again at next startup.
I know I can stop it from asking entirely in it's settings, but I rather have it fixed so it actually knows how to set itself as the default.
Might this be DE related? I'm using KDE, not sure if it applies on GNOME as well.https://gitlab.alpinelinux.org/alpine/aports/-/issues/4018Package request: Pacemaker, Corosync, PCS2020-10-08T16:49:39ZVadym CheninPackage request: Pacemaker, Corosync, PCSPacemaker is an Open Source, High Availability resource manager suitable
for both small and large clusters.
http://clusterlabs.org/
The Corosync Cluster Engine is a Group Communication System with
additional features for implementing ...Pacemaker is an Open Source, High Availability resource manager suitable
for both small and large clusters.
http://clusterlabs.org/
The Corosync Cluster Engine is a Group Communication System with
additional features for implementing high availability within
applications.
http://corosync.github.io/corosync/
PCS - Pacemaker/Corosync configuration system
https://github.com/feist/pcs
*(from redmine: issue id 4018, created on 2015-03-24)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/12002setup-disk does not support sys install on rpi2020-10-12T15:46:17ZNatanael Copasetup-disk does not support sys install on rpiInstalling alpine on rpi as `sys` install does not work. Special care is needed for the rpi bootloader and kernel needs to be on fat.Installing alpine on rpi as `sys` install does not work. Special care is needed for the rpi bootloader and kernel needs to be on fat.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12006raspberry ttyAMA0 permissions2020-10-13T13:41:12ZObbartraspberry ttyAMA0 permissionsHi, i have to make the serial port ttyAMA0 accessible to non root user to run a python application that uses it.
I changed the /dev/mdev.conf file adding `ttyAMA0 root:tty 0660` right above the `ttyUSB...` line.
After committing and reb...Hi, i have to make the serial port ttyAMA0 accessible to non root user to run a python application that uses it.
I changed the /dev/mdev.conf file adding `ttyAMA0 root:tty 0660` right above the `ttyUSB...` line.
After committing and rebooting the changes seems not to take effect unless i run `mdev -s` manually.
Once i start the python application, the serial port reverts to `root:root 0640` permission automatically crashing the app.
Am I missing something in the mdev confguration? Thanks for supporthttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10947feat package cryfs2020-10-16T20:03:20ZJackson Rezendefeat package cryfsCryFS encrypts your files, so you can safely store them anywhere. It works well together with cloud services like Dropbox, iCloud, OneDrive and others.
https://www.cryfs.org/
Source: github.com/cryfs/cryfsCryFS encrypts your files, so you can safely store them anywhere. It works well together with cloud services like Dropbox, iCloud, OneDrive and others.
https://www.cryfs.org/
Source: github.com/cryfs/cryfshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11670targetcli does not succesfully restore config2020-11-09T13:35:25ZAlain van Hooftargetcli does not succesfully restore configAfter configuring targetcli and saving config, config is not restored after a reboot, or when loaded via commandline. Both due to this error:
targetcli restoreconfig
restore_from_file() takes from 1 to 4 positional arguments but 5 were ...After configuring targetcli and saving config, config is not restored after a reboot, or when loaded via commandline. Both due to this error:
targetcli restoreconfig
restore_from_file() takes from 1 to 4 positional arguments but 5 were given
Note: "targetctl restore" does work.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11809telegram-desktop hard crashes looking at certain sticker previews2020-11-10T15:59:08ZEllietelegram-desktop hard crashes looking at certain sticker previewstelegram-desktop hard crashes for me when I look at certain sticker combinations in the preview panel when writing a single emoji which will show a live-mix of "fitting" stickers based on recent usage to go with that emoji. This seems to...telegram-desktop hard crashes for me when I look at certain sticker combinations in the preview panel when writing a single emoji which will show a live-mix of "fitting" stickers based on recent usage to go with that emoji. This seems to happen 100% depending on the exact sticker set shown, which makes me wonder if this is a musl-libc issue? (E.g. stack blown when rendering certain more complex animated ones in combination?)
Edit: this is on the PinePhone using postmarketOS stable based on Alpine 3.12 with telegram-desktop 2.1.11-r1