alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2024-03-09T22:51:21Zhttps://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/15848community/neochat: module "org.kde.prison" is not installed2024-03-27T19:29:01ZHugo Barreracommunity/neochat: module "org.kde.prison" is not installed```con
> neochat
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
QQmlApplicationEngine failed to load component...```con
> neochat
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
QQmlApplicationEngine failed to load component
qrc:/org/kde/neochat/qml/main.qml:22:5: Type RoomPage unavailable
qrc:/org/kde/neochat/qml/RoomPage.qml:305:9: Type UserDetailDialog unavailable
qrc:/org/kde/neochat/qml/UserDetailDialog.qml:12:1: module "org.kde.prison" is not installed
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15847[lists/~alpine-devel] shadow 4.14 build errors on Alpine Linux2024-03-11T02:16:11ZKevin Daudt[lists/~alpine-devel] shadow 4.14 build errors on Alpine Linux[Forwarded from ~alpine/devel]
Hi,
I've noticed both Alpine Linux has a patch
<fix-undefined-reference.patch> for shadow, and that Void Linux
considered picking it.
The most likely reason for that patch was the bug reported by Gentoo:...[Forwarded from ~alpine/devel]
Hi,
I've noticed both Alpine Linux has a patch
<fix-undefined-reference.patch> for shadow, and that Void Linux
considered picking it.
The most likely reason for that patch was the bug reported by Gentoo:
<https://github.com/shadow-maint/shadow/issues/791>
and fixed in 4.14.1:
<https://github.com/shadow-maint/shadow/pull/792>
<https://github.com/shadow-maint/shadow/pull/794>
We never knew why it failed. It was an obscure problem with the
autotools-based build system. But we fixed it with the big hammer.
Please drop that patch, since the issue has been fixed upstream. And
please report any build errors upstream.
Have a lovely day!
Alex
---
See the release annotations, which document the fix:
$ git show 4.14.1
tag 4.14.1
Tagger: Alejandro Colomar <alx@kernel.org>
Date: Mon Sep 25 18:00:29 2023 +0200
shadow-4.14.1 (Casín) - shadow utils
Bugfix release. Changes since shadow-4.14.0:
shadow-4.14.1:
- Build system:
> - Merge libshadow and libmisc into a single libshadow. This fixes
> problems in the linker, which were reported at least in Gentoo.
And also documented in 4.15.0:
$ git show 4.15.0
tag 4.15.0
Tagger: Serge Hallyn <serge@hallyn.com>
Date: Fri Mar 8 16:06:06 2024 -0600
Release 4.14.0: dubliner
- libshadow:
- Use utmpx instead of utmp. This fixes a regression introduced in
4.14.0.
- Fix build error (parameter name omitted).
- Build system:
- Link correctly with libdl.
- Install pam configs for chpasswd(8) and newusers(8) when using
`./configure --with-libpam --disable-account-tools-setuid`.
> - Merge libshadow and libmisc into a single libshadow. This fixes
> problems in the linker, which were reported at least in Gentoo.
- Fix build with musl libc.
- Support out of tree builds
- useradd(8):
- Set proper SELinux labels for def_usrtemplate
--
<https://www.alejandro-colomar.es/>
[signature.asc](/uploads/e7bf8580ccd2978bdce2f71fd42fe63e/signature.asc)Stuart CardallStuart Cardallhttps://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/15845superd-services swww.service uses unsupported value causing panic2024-03-27T19:29:01Z1.11e-1f64superd-services swww.service uses unsupported value causing panicIn the package superd-services, it adds a service file called "swww.service"
this causes a panic when running 'superd'
`unsupported value for "Before=|After=": graphical-session.target
panic: swww: unsupported value for "Before=|After...In the package superd-services, it adds a service file called "swww.service"
this causes a panic when running 'superd'
`unsupported value for "Before=|After=": graphical-session.target
panic: swww: unsupported value for "Before=|After=": graphical-session.target
goroutine 1 [running]:
main.main()
sr.ht/~craftyguy/superd/cmd/superd/main.go:136 +0x88f`
the fix is to remove swww.service and it lets superd run againHugo BarreraHugo Barrerahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15844Cannot open HEIC files on KDE2024-03-12T13:14:58ZJulian GroßCannot open HEIC files on KDEI cannot open any HEIC files (Apple specific format using H265 for pictures) on postmarketOS Edge.
From what I read online, KDE Frameworks should have HEIC support since 5.80.
On 5.113, these files don't open in Pix or Okular.
On 6.0.0, ...I cannot open any HEIC files (Apple specific format using H265 for pictures) on postmarketOS Edge.
From what I read online, KDE Frameworks should have HEIC support since 5.80.
On 5.113, these files don't open in Pix or Okular.
On 6.0.0, these files don't open in Koko or Okular. (Pix is currently broken)
Maybe KDE Frameworks is built without HEIC support? Other packages like ImageMagick apparently needed this to be enabled: https://gitlab.alpinelinux.org/alpine/aports/-/commit/0ac585f438686c5c720343fd8b019ed86d905bf2https://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/15842docker stats: no cpu, mem and io stats2024-03-26T22:04:13ZMark Porembadocker stats: no cpu, mem and io statsHi,
I have an Alpine system 3.19 running in a lxc container on Proxmox 8.1.4. I installed docker and docker-compose which are running currently 13 containers.
Now I want to setup a monitoring for the container. Running `docker stats` the...Hi,
I have an Alpine system 3.19 running in a lxc container on Proxmox 8.1.4. I installed docker and docker-compose which are running currently 13 containers.
Now I want to setup a monitoring for the container. Running `docker stats` the value for CPU, Mem and Block IO for all container is 0.
After some research I think the setup of cgroups is the issue. If I activate cgroups V1 in `/etc/rc.conf` (`rc_cgroup_mode="legacy"`) I get values for CPU, but Mem and Block IO remains at 0.
If cgroups V2 is activated in `/etc/rc.conf` (`rc_cgroup_mode="unified"`) all values for CPU, Mem and Block IO are 0. The file `/sys/fs/cgroup/cgroup.subtree_control` is empty so that no values will be monitored for containers.
Every time I found the hint to add the cmdline parameters `group_enable=cpuset cgroup_enable=memory cgroup_memory=1` but I do not find the file `cmdline.txt` which I should edit. Most of the times I find the hint for systemd like
```
$ cat <<EOF | sudo tee /etc/systemd/system/user@.service.d/delegate.conf
[Service]
Delegate=cpu cpuset io memory pids
```
Is this the correct way to activate the delegation of the cgroup values for container? Where can I find the file `cmdline.txt` or something similar?
Thanks for the help!
Kind regardshttps://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/apk-tools/-/issues/10977`apk add` tries to set directory permissions when running as non-root user2024-03-11T13:54:53Zleso-kn`apk add` tries to set directory permissions when running as non-root userFrom the apk-tools documentation:
> ```
> --no-chown
> Do not change file owner or group. By default apk will manage the file
> ownership when running as root. However, this option is turned on when
> running as non-root user, a...From the apk-tools documentation:
> ```
> --no-chown
> Do not change file owner or group. By default apk will manage the file
> ownership when running as root. However, this option is turned on when
> running as non-root user, as changing file ownership is not permitted
> by the system then.
> ```
#### Reproducing the error
```bash
# as a non-root user
$ mkdir -p test-sysroot/etc/apk/keys
$ uname -m > test-sysroot/etc/apk/arch
$ cp /etc/apk/repositories test-sysroot/etc/apk
# let's try to install vim
$ apk --root=$PWD/test-sysroot add --initdb --allow-untrusted vim
(1/6) Installing vim-common (9.1.0-r1)
(2/6) Installing musl (1.2.5-r0)
(3/6) Installing xxd (9.1.0-r1)
(4/6) Installing ncurses-terminfo-base (6.4_p20231125-r0)
(5/6) Installing libncursesw (6.4_p20231125-r0)
(6/6) Installing vim (9.1.0-r1)
ERROR: 71 errors updating directory permissions
OK: 32 MiB in 6 packages
```
#### Expected behaviour
After vim is installed `apk` should not try to set any permissions, as `--no-chown` is implicitly passed by running as a non-root user.
**Note:** Passing `--no-chown` explicitly results in the same behaviour.
#### Actual behaviour
`apk` tries to set to set directory permissions despite the `--no-chown` flag in [database.c:2101](https://gitlab.alpinelinux.org/alpine/apk-tools/-/blob/6cd7f31d9bde79bb6361f2d2cbe37bfbafa342ea/src/database.c#L2101).https://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/15838community/tokodon: fails to launch2024-03-15T08:10:48ZMarco Schrödercommunity/tokodon: fails to launchTokodon does not launch.
The following is printed in the log:
```
QQmlApplicationEngine failed to load component
qrc:/qt/qml/org/kde/tokodon/content/ui/Main.qml: module "org.kde.desktop" is not installed
```
System information:
- postm...Tokodon does not launch.
The following is printed in the log:
```
QQmlApplicationEngine failed to load component
qrc:/qt/qml/org/kde/tokodon/content/ui/Main.qml: module "org.kde.desktop" is not installed
```
System information:
- postmarketOS edge
- tokodon 24.02.0-r0https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10817Latest development not updated anymore2024-03-06T19:20:53ZJ0WILatest development not updated anymoreThe newest commit shown in the «Latest development» section is from 2024-02-04The newest commit shown in the «Latest development» section is from 2024-02-04https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/issues/20Latest development not updated anymore2024-03-06T19:20:14ZJ0WILatest development not updated anymoreThe newest commit shown in the «Latest development» section is from 2024-02-04The newest commit shown in the «Latest development» section is from 2024-02-04https://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/15835appstream and appstream0 still conflict with each other2024-03-06T21:50:55ZClayton Craftappstream and appstream0 still conflict with each otherI think this actually shows 2 issues:
```
(434/817) Installing appstream (1.0.2-r1)
ERROR: appstream-1.0.2-r1: trying to overwrite usr/lib/girepository-1.0/AppStream-1.0.typelib owned by appstream0-0.16.3-r1.
ERROR: appstream-1.0.2-r1: ...I think this actually shows 2 issues:
```
(434/817) Installing appstream (1.0.2-r1)
ERROR: appstream-1.0.2-r1: trying to overwrite usr/lib/girepository-1.0/AppStream-1.0.typelib owned by appstream0-0.16.3-r1.
ERROR: appstream-1.0.2-r1: trying to overwrite usr/share/metainfo/org.freedesktop.appstream.cli.metainfo.xml owned by appstream0-0.16.3-r1.
ERROR: appstream-1.0.2-r1: trying to overwrite usr/share/metainfo/org.freedesktop.appstream.compose.metainfo.xml owned by appstream0-0.16.3-r1.
Executing appstream-1.0.2-r1.post-install
lib/apk/exec/appstream-1.0.2-r1.post-install: line 4: /usr/bin/appstreamcli: not found
```
1. there's still a file conflict with appstream and appstream0 preventing both from being installed at the same time
2. `appstream` depends on its subpackage, `appstream-cli`
I'm not sure how to resolve each of these...
Also see:
- https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/61709
- https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/61707
- https://gitlab.alpinelinux.org/alpine/aports/-/issues/15834
cc @pabloyoyoista @PureTryOut