aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2024-03-15T02:07:31Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15859KDE6 update aftermath2024-03-15T02:07:31ZPatrycja Rosaalpine@ptrcnull.meKDE6 update aftermatha bit more than a week after !61432 landed in master, countless fixes, at least 15 KF5 packages restored, and one somewhat critical fix still waiting for upstreaming (!61929), here's the current state of aports:
- [ ] 18 packages (x86_64...a bit more than a week after !61432 landed in master, countless fixes, at least 15 KF5 packages restored, and one somewhat critical fix still waiting for upstreaming (!61929), here's the current state of aports:
- [ ] 18 packages (x86_64, varies on others) dependent on KF5 stuff, unable to build due to missing build dependencies ( down from over 70 ) ([link][1])
- [ ] 20 packages (see above) still missing dependent libraries ([link][2])
- [ ] armv7 still choking on packages depending (transitively as well) on qt6-qtwebengine
[1]: https://tpaste.us/a1eM
[2]: https://dev.alpinelinux.org/~ptrc/errors20240311.svg
opening this mostly in hopes of getting more people to help in either upgrading apps to (KF|Qt)6 ( such as in !61851 ), or fixing those that still depend on KF5, so that they don't have missing dependencieshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15857community/firefox: Speech Dispatcher library is missing2024-03-18T14:30:32ZPatrycja Rosaalpine@ptrcnull.mecommunity/firefox: Speech Dispatcher library is missing![image](/uploads/4d4685bf0ab2ef14d58b59fef32c6d62/image.png)
not sure yet *which* speech library it wants though![image](/uploads/4d4685bf0ab2ef14d58b59fef32c6d62/image.png)
not sure yet *which* speech library it wants thoughPatrycja Rosaalpine@ptrcnull.mePatrycja Rosaalpine@ptrcnull.mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15856community/gdm - Xorg sessions cant start on /dev/tty72024-03-10T21:06:16ZLassebqcommunity/gdm - Xorg sessions cant start on /dev/tty7Attempting to run an Xorg session from GDM will throw you right back to the login screen.
This happens because Xorg server started by user does not have permission to access /dev/tty7 as the logs mention:
[Xorg.1.log](/uploads/22d18b3e57...Attempting to run an Xorg session from GDM will throw you right back to the login screen.
This happens because Xorg server started by user does not have permission to access /dev/tty7 as the logs mention:
[Xorg.1.log](/uploads/22d18b3e57e6f56614292f108bae66c9/Xorg.1.log)
Workarounds:
- Switch to a VT2 and run `chown user /dev/tty7` as root
And another side note: This does not happen with lightdm since it starts session on the same tty as the DM, and (maybe) even reuses DM's Xorg server.
- Run a Wayland session and logout prior to logging in an Xorg session (/dev/tty7 remains owned by user after logout)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15855community/gdm - ~/.profile doesn't get sourced by Xorg sessions and by Waylan...2024-03-10T21:04:21ZLassebqcommunity/gdm - ~/.profile doesn't get sourced by Xorg sessions and by Wayland sessions other than GNOMEWhile `~/.profile` does get sourced by GNOME Wayland session, other sessions don't use environment from login shells, but instead inherit environment variables from GDM.
To verify, I use GNOME's run menu (Alt + F2 by default) and run `k...While `~/.profile` does get sourced by GNOME Wayland session, other sessions don't use environment from login shells, but instead inherit environment variables from GDM.
To verify, I use GNOME's run menu (Alt + F2 by default) and run `kgx -- sh` and run `env` in the opened terminal window.
You can also notice MOZ_ENABLE_WAYLAND missing in firefox when running firefox through app launcher.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15854$PATH set in .zshenv gets overwritten by /etc/profile2024-03-13T20:57:57ZLassebq$PATH set in .zshenv gets overwritten by /etc/profileThanks to the mention of `/etc/profile` in !6563 I was able to identify cause of `.zshenv` not appending my paths by the login shell
Apparently Alpine's default /etc/profile sets PATH instead of appending to it.
I did not have such issue...Thanks to the mention of `/etc/profile` in !6563 I was able to identify cause of `.zshenv` not appending my paths by the login shell
Apparently Alpine's default /etc/profile sets PATH instead of appending to it.
I did not have such issue on Arch Linux since their /etc/profile looks like this:
```sh
# Append "$1" to $PATH when not already in.
# This function API is accessible to scripts in /etc/profile.d
append_path () {
case ":$PATH:" in
*:"$1":*)
;;
*)
PATH="${PATH:+$PATH:}$1"
esac
}
# Append our default paths
append_path '/usr/local/sbin'
append_path '/usr/local/bin'
append_path '/usr/bin'
# Force PATH to be environment
export PATH
# Load profiles from /etc/profile.d
if test -d /etc/profile.d/; then
for profile in /etc/profile.d/*.sh; do
test -r "$profile" && . "$profile"
done
unset profile
fi
# Unload our profile API functions
unset -f append_path
```
What makes Arch Linux's approach more convenient is that append_path function is exposed to all files in `/etc/profile.d/`. It also gets utilized by certain packages on Arch Linux (such as java's bin being appended to path)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15852gdm keyboard layout cannot be changed2024-03-13T17:15:27Zviba1gdm keyboard layout cannot be changed**Issue Description**
After installing GNOME on Alpine Linux and setting up the display manager to use GDM3, it has been observed that the login screen is set to QWERTY keyboard layout by default. This makes it impossible for users who d...**Issue Description**
After installing GNOME on Alpine Linux and setting up the display manager to use GDM3, it has been observed that the login screen is set to QWERTY keyboard layout by default. This makes it impossible for users who do not have a QWERTY keyboard or prefer another layout (such as AZERTY) to log in at first attempt. The problem persists even when trying to change the layout from the login screen, which does not provide any option to switch to an alternative keyboard layout.
**Steps to reproduce:**
Install gnome on alpine : [https://wiki.alpinelinux.org/wiki/GNOME](https://wiki.alpinelinux.org/wiki/GNOME)
Attempt to log in with non-QWERTY keyboard layout.
**Expected result:**
The GDM3 interface should allow users to choose their preferred keyboard layout during initial login before entering their password, regardless of whether they are using a QWERTY, AZERTY, DVORAK, or other keyboard layout.
**Actual result:**
GDM3 defaults to QWERTY keyboard layout without providing options to change it at the login screen, making it difficult or impossible for some users to enter their credentials correctly and complete the login process successfully.
**Additional information:**
Once a user logs in and opens their desktop session, GDM3 considers the correct keyboard layout configured in GNOME. However, upon reboot or disconnection of the user, the error recurs where only the QWERTY keyboard layout is available at the GDM3 login screen. Investigation is needed to address why GDM3 fails to remember the last used keyboard layout across boots or disconnects.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15851testing/android-translation-layer: link against gcompat...?2024-03-09T22:51:21ZPatrycja Rosaalpine@ptrcnull.metesting/android-translation-layer: link against gcompat...?most android apps use bionic libc symbols, which seem to also exist in glibc, but not in musl, like `__openat_2` or `strtoull_l`
i feel like linking libandroid.so.0 against gcompat would be the easiest solution, but then, that doesn't q...most android apps use bionic libc symbols, which seem to also exist in glibc, but not in musl, like `__openat_2` or `strtoull_l`
i feel like linking libandroid.so.0 against gcompat would be the easiest solution, but then, that doesn't quite work correctly for mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15850py3-bind package missing in 3.17+2024-03-10T20:02:45ZRon Chinnpy3-bind package missing in 3.17+I recently upgraded a name server from Alpine Linux 3.16 to 3.18. The py3-bind subpackage was removed in 3.17 and there are no references to Python in the APKBUILD file now. This package provided support for communicating with rndc fr...I recently upgraded a name server from Alpine Linux 3.16 to 3.18. The py3-bind subpackage was removed in 3.17 and there are no references to Python in the APKBUILD file now. This package provided support for communicating with rndc from Python. Can this package be added again in a future release?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15849bind package missing JSON support2024-03-09T21:05:57ZRon Chinnbind package missing JSON supportI recently upgraded a name server from Alpine Linux 3.16 to 3.18. Several changes were made to the bind package in 3.17 and up that remove functionality that was present in 3.16. One of these changes is the removal of JSON support for...I recently upgraded a name server from Alpine Linux 3.16 to 3.18. Several changes were made to the bind package in 3.17 and up that remove functionality that was present in 3.16. One of these changes is the removal of JSON support for the bind statistics channel. JSON support depends on the "--with-libjson" argument when building bind, but this is missing in 3.18. See https://kb.isc.org/docs/aa-01123 for details about this option.Mike Crutemike@crute.usMike Crutemike@crute.ushttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15846bemenu with wayland backend broken on phosh2024-03-24T07:57:45ZArnav Singhbemenu with wayland backend broken on phosh[bemenu v0.6.20 wants `zwlr_layer_shell_v1` v3](https://github.com/Cloudef/bemenu/commit/6bcffe408c1519834ed00abec4030b9d49f9a52c) but [phoc v0.36.0 only provides v2.](https://gitlab.gnome.org/World/Phosh/phoc/-/blob/v0.36.0/src/desktop....[bemenu v0.6.20 wants `zwlr_layer_shell_v1` v3](https://github.com/Cloudef/bemenu/commit/6bcffe408c1519834ed00abec4030b9d49f9a52c) but [phoc v0.36.0 only provides v2.](https://gitlab.gnome.org/World/Phosh/phoc/-/blob/v0.36.0/src/desktop.c?ref_type=tags#L57) (Newer phoc v0.37.0 or even its main branch also only provide v2.)
```sh
$ printf 'asd\nqwe\n' | WAYLAND_DEBUG=1 bemenu
[2920359.323] wl_registry@2.global(9, "zwlr_layer_shell_v1", 2)
[2920359.393] -> wl_registry@2.bind(9, "zwlr_layer_shell_v1", 3, new id [unknown]@6)
[2920362.814] wl_display@1.error(wl_registry@2, 0, "invalid version for global zwlr_layer_shell_v1 (9): have 2, wanted 3")
wl_registry@2: error 0: invalid version for global zwlr_layer_shell_v1 (9): have 2, wanted 3
```Sören TempelSören Tempelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15843Pix - "org.kde.kquickimageeditor" is not installed2024-03-18T14:31:43ZJulian GroßPix - "org.kde.kquickimageeditor" is not installedUpgrading from Plasma Mobile 5 to 6, Pix doesn't start anymore.
Running it from command line has it complain about "org.kde.kquickimageeditor" not being installed. The kquickimageeditor package is installed, however. [pmOS-Edge-Pix_not_s...Upgrading from Plasma Mobile 5 to 6, Pix doesn't start anymore.
Running it from command line has it complain about "org.kde.kquickimageeditor" not being installed. The kquickimageeditor package is installed, however. [pmOS-Edge-Pix_not_starting-2024-03-08.log](/uploads/6fa243ae5bbc5e704ab89c94fceeef25/pmOS-Edge-Pix_not_starting-2024-03-08.log)
This is on postmarketOS Edge.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15841Inconsistencies in busybox .initd2024-03-19T17:10:42ZFxzx micInconsistencies in busybox .initdI found some inconsistencies in busybox .initd:
| file | name | variables |
|------|------|-----------|
| acpid.initd | acpid | no |
| crond.initd | crond | $RC_SVCNAME and $SVCNAME |
| dnsd.initd | dnsd | $RC_SVCNAME and $SVCNAME |
| h...I found some inconsistencies in busybox .initd:
| file | name | variables |
|------|------|-----------|
| acpid.initd | acpid | no |
| crond.initd | crond | $RC_SVCNAME and $SVCNAME |
| dnsd.initd | dnsd | $RC_SVCNAME and $SVCNAME |
| httpd.initd | httpd | $RC_SVCNAME and $SVCNAME |
| inetd.initd | inetd | $RC_SVCNAME and $SVCNAME |
| klogd.initd | klogd | no |
| ntpd.initd | ntpd | $RC_SVCNAME and $SVCNAME |
| syslog.initd | syslog | no |
| udhcpd.initd | udhcpd | $RC_SVCNAME and $SVCNAME |
| watchdog.initd | watchdog | no |
Should we unify these and set a standard? Also, should `syslog` be renamed to `syslogd`?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15840unbound config file2024-03-10T15:44:39ZDave Akersunbound config fileThe unbound conf.d/ini.d script has a variable for a config file but doesn't add `-c $cfgfile` to $command_argsThe unbound conf.d/ini.d script has a variable for a config file but doesn't add `-c $cfgfile` to $command_argsJakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15839TeXLive — t4ht tex4ht binaries missing; never included, since day one2024-03-14T00:10:16ZCarlos eTeXLive — t4ht tex4ht binaries missing; never included, since day oneThis issue has been going
this issue hwas been going on for over a year. heck, since day one for that matter, currently I'm not using the prepackageg texlive, and thought someone would come across first, and at the very least bring it u...This issue has been going
this issue hwas been going on for over a year. heck, since day one for that matter, currently I'm not using the prepackageg texlive, and thought someone would come across first, and at the very least bring it up, hence, saving myself the time to do it instead, but no.
back in whenever, when 7 years ago @maribu was kind enough by putting together this package, the assumption was to follow the same model used by arch linux , and before you knew it, it was put in place. Everyone agreed in a consentual fashion and thought it best to do it that way, https://gitlab.alpinelinux.org/alpine/aports/-/issues/4514#note_20958
but this arch linux way of doing things, may not have been the most appropriate to follow at least not for these binaries anyway
And the problem with this is that tex4ht has been part of texlive since the stoneage wheen all those folks were young fellas and not unlike now all those grumpy old guys. Anyway. All the binaries related to this program are missing: tex4ht t4ht htlatex,and so forth
And Karl Berry had personally given me some compressed files that included both binaries and luckily it did worked. But recently it did not cut it as before.
and I also tried (as before) the binaries from arch linux — which I had done over a year ago — but this time it didn't work.
even with all the binaries that one could think of in place, errors such as
`sh: tex4ht: not found
[FATAL] make4ht-lib: Fatal error. Command tex4ht returned exit code 127` kept coming upMarian BuschsiewekeMarian Buschsiewekehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15837package request: prometheus-podman-exporter2024-03-15T17:18:22ZNavid Yaghoobipackage request: prometheus-podman-exporterPrometheus exporter for podman environments exposing containers, pods, images, volumes and networks information.
https://github.com/containers/prometheus-podman-exporterPrometheus exporter for podman environments exposing containers, pods, images, volumes and networks information.
https://github.com/containers/prometheus-podman-exporterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15836Package request: flatpak-builder-tools2024-03-06T22:02:42ZAngelo Verlain ShemaPackage request: flatpak-builder-toolshttps://github.com/flatpak/flatpak-builder-tools
From the repo: "This repository contains a collection of various scripts to aid in using flatpak-builder."
It provides tools that work with `flatpak-builder`. It allows generating source...https://github.com/flatpak/flatpak-builder-tools
From the repo: "This repository contains a collection of various scripts to aid in using flatpak-builder."
It provides tools that work with `flatpak-builder`. It allows generating sources for cargo, npm, yarn and others and make building flatpak packages that depend on said build tools easier.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15832thin-provisioning-tools package is missing for s390x in Alpine 3.182024-03-21T12:25:56ZPrabhav Thalithin-provisioning-tools package is missing for s390x in Alpine 3.18thin-provisioning-tools package is not present for alpine v3.18.
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/s390x/APKINDEX.tar.gz
ERROR: unable to select packages:
thin-provisioning-tools (no such package):
required ...thin-provisioning-tools package is not present for alpine v3.18.
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/s390x/APKINDEX.tar.gz
ERROR: unable to select packages:
thin-provisioning-tools (no such package):
required by: world[thin-provisioning-tools]
```
Looks like the build is disabled for s390x (Ref: [link](https://gitlab.alpinelinux.org/alpine/aports/-/commit/d62aa7ba18f3ef9360799c79c341237db2c084be)). Could you please provide more details about the same?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15830Please Package A Build of River With No XWayland Support i.e. river-noxwayland2024-03-04T19:49:13ZVehementHamPlease Package A Build of River With No XWayland Support i.e. river-noxwaylandI do not need XWayland, and it is extremely bloated. Please package a build that does not requrie it (don't build with `-Dxwayland` flag). The package could be called `river-noxwayland`. A package like this exists in the AUR.I do not need XWayland, and it is extremely bloated. Please package a build that does not requrie it (don't build with `-Dxwayland` flag). The package could be called `river-noxwayland`. A package like this exists in the AUR.Anjandev MomiAnjandev Momihttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15829sub-package request: texlive-context (& possibly texmf-dist-context?)2024-03-03T23:50:03Zomniomni+alpine@hack.orgsub-package request: texlive-context (& possibly texmf-dist-context?)The last alpinelinux release where `/usr/bin/context` and `/usr/bin/mtxrun` etc is available is 3.17
- https://pkgs.alpinelinux.org/contents?file=context&path=&name=&branch=v3.17
- https://pkgs.alpinelinux.org/contents?file=mtxrun&path=...The last alpinelinux release where `/usr/bin/context` and `/usr/bin/mtxrun` etc is available is 3.17
- https://pkgs.alpinelinux.org/contents?file=context&path=&name=&branch=v3.17
- https://pkgs.alpinelinux.org/contents?file=mtxrun&path=&name=&branch=v3.17
I'm guessing that they got lost after an upgrade of `texlive` and `texmf-dist`.Marian BuschsiewekeMarian Buschsiewekehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15828nftables counters added to the default table don't save2024-03-04T06:26:24ZDave Akersnftables counters added to the default table don't saveI've recently starting experimenting with using alpine as a home router. The nftables init script has an option to save counters to a state file. However if you add a counter to the default table in /etc/nftables.nft the counter will be ...I've recently starting experimenting with using alpine as a home router. The nftables init script has an option to save counters to a state file. However if you add a counter to the default table in /etc/nftables.nft the counter will be saved but not reloaded. This is because the state file is included at the end of /etc/nftables.nft and the counters are already defined.
If the state file is included at the beginning of /etc/nftables.nft then the counters will be reloaded and adding new counters to the default table works as expected.
Another alternative would be to move the default table in /etc/nftables.nft to a file in /etc/nftables.d/... then the include order would work as expected. A benefit of moving the default table to nftables.d is to provide an example to the user as to how to use the .d directory.Francesco ColistaFrancesco Colista