alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2022-11-26T14:08:22Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14380bsdmainutils2022-11-26T14:08:22Zn cbsdmainutilsThis is a package request for bsdmainutils
https://packages.debian.org/source/sid/bsdmainutils
https://helpmanual.io/packages/apt/bsdmainutils/
It's the tools such as calendar that come from bsd. It's already packaged in debian and it...This is a package request for bsdmainutils
https://packages.debian.org/source/sid/bsdmainutils
https://helpmanual.io/packages/apt/bsdmainutils/
It's the tools such as calendar that come from bsd. It's already packaged in debian and it would be very nice to have it accessible from Alpine as well.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14386Kaidan Crashes Plasma (X11)2022-11-27T18:55:10ZSJ SJKaidan Crashes Plasma (X11)Kaidan Crashes Plasma when clicking on start button.
Using alpine-extended-3.17.0-x86_64.isoKaidan Crashes Plasma when clicking on start button.
Using alpine-extended-3.17.0-x86_64.isohttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14397Package request: AssaultCube2022-11-29T01:49:06ZSJ SJPackage request: AssaultCubeIt's an FPS action game based on Cube and is similar to [Sauerbraten](http://sauerbraten.org/).
Significant differences:
- Player image is of human image.
- Package weight is only ~50MB.
Due to its smaller size, it will probably be a g...It's an FPS action game based on Cube and is similar to [Sauerbraten](http://sauerbraten.org/).
Significant differences:
- Player image is of human image.
- Package weight is only ~50MB.
Due to its smaller size, it will probably be a game of choice for handheld Linux users (i.e. postmarketOS).
Link: https://assault.cubers.net/https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10085rpath tracing/warning prints ERROR: even when not2022-12-03T03:14:00ZGhost Userrpath tracing/warning prints ERROR: even when notthis is because of
```
real_so_path "$1" /usr/lib /lib $rpaths || return 1
```
which does
```
error "$so: path not found"
return 1
```
this looks confusing to most people, as it's not actually an error (no build failure). per...this is because of
```
real_so_path "$1" /usr/lib /lib $rpaths || return 1
```
which does
```
error "$so: path not found"
return 1
```
this looks confusing to most people, as it's not actually an error (no build failure). perhaps it should warn instead?
it is also quite hard sometimes to find which file even causes the issue - perhaps the file currently being checked should be printed? (the one that has its needed' list iterated)https://gitlab.alpinelinux.org/alpine/aports/-/issues/14400What does pypy3 need to come out of testing?2023-01-15T20:41:09ZldeluigiWhat does pypy3 need to come out of testing?I'm an Alpine user and a potential user of the pypy3 compiler for Python.
Given that the package is in _testing_, I need to use apline:edge in order to install it, but I'm not able to replace the Alpine stable version with edge unfortuna...I'm an Alpine user and a potential user of the pypy3 compiler for Python.
Given that the package is in _testing_, I need to use apline:edge in order to install it, but I'm not able to replace the Alpine stable version with edge unfortunately.
I'm wondering if pypy3 is in the process of becoming unmantained/purged or is it on its way to the main or community branches?
Nevertheless, I tested the installation on Docker using apline:edge and everything worked fine for me.Thomas Liskeliske@ibh.deThomas Liskeliske@ibh.dehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14401NetworkManager prevents unbound from starting2022-12-04T23:49:06ZKrassy Boykinovkboykinov@teamcentrixx.comNetworkManager prevents unbound from startingHello,
after activating NetworkManager with rc-update unbound would not start for me. I have tried a lot. Both boot and default runlevels cause this. I use alpine on bare metal with setup-desktop gnome. After replacing networkmanager wi...Hello,
after activating NetworkManager with rc-update unbound would not start for me. I have tried a lot. Both boot and default runlevels cause this. I use alpine on bare metal with setup-desktop gnome. After replacing networkmanager with networking service, everything works again.
I run edge with latest updates.
Thank you for your help.
[rc-status.txt](/uploads/95cd7b5e1aebdc64bf8307cf0032fe1d/rc-status.txt)
[rc.log](/uploads/941e4a973a2576c2d7cf542b308c18f1/rc.log)https://gitlab.alpinelinux.org/alpine/aports/-/issues/14407Installer: installer not booting in Apple's Virtualization.framework virtual ...2023-03-26T04:23:32ZCatherine KellyInstaller: installer not booting in Apple's Virtualization.framework virtual machines## Description
The installer does not boot in virtual machines built with macOS Virtualization.framework.
## Version
3.17.0 Virt, 3.17.0 Standard
## Arch
Aarch64
## Host OS
macOS 13.0.1 (aarch64)
## Expected behavior
The installer bo...## Description
The installer does not boot in virtual machines built with macOS Virtualization.framework.
## Version
3.17.0 Virt, 3.17.0 Standard
## Arch
Aarch64
## Host OS
macOS 13.0.1 (aarch64)
## Expected behavior
The installer booted successfully.
## Actual behavior
After selecting "Linux virt" in GRUB, the screen freezes.
## Possibly related to
https://gitlab.alpinelinux.org/alpine/aports/-/issues/13120
## Additional information
RHEL / CentOS / Alma Linux, Fedora, Arch Linux ARM, Ubuntu installer boots.
The `virtio_console`, `virtio_gpu` kernel modules are not included in the installer.
`virtio_blk` and `virtio_dma_buf` are not loaded upon boot.
The CPU usage goes to 100%. (possibly the kernel panicked?)
A sample Virtualization.framework project can be found at [Running GUI Linux in a virtual machine on a Mac](https://developer.apple.com/documentation/virtualization/running_gui_linux_in_a_virtual_machine_on_a_mac).Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10867Documentation on cmd:PATTERN, so:PATTERN etc. missing from apk-search.82022-12-26T13:28:50ZPaul W. Rankinhello@paulwrankin.comDocumentation on cmd:PATTERN, so:PATTERN etc. missing from apk-search.8I'm not sure where I learnt that `apk-search(8)` could accept `cmd:PATTERN` but it seems it was not the man page.
Upon trying to learn which prefixes are available the documentation is missing.I'm not sure where I learnt that `apk-search(8)` could accept `cmd:PATTERN` but it seems it was not the man page.
Upon trying to learn which prefixes are available the documentation is missing.backloghttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14414Add something to the ssh login banner like on Ubuntu that announces a new rel...2023-01-28T09:24:53ZEllieAdd something to the ssh login banner like on Ubuntu that announces a new releaseOn my server machine running Alpine on the bare host, I regularly miss new Alpine releases. This means I obviously miss out on the security updates too, so this seems like a big deal to me. I just occasionally notice that apparently, som...On my server machine running Alpine on the bare host, I regularly miss new Alpine releases. This means I obviously miss out on the security updates too, so this seems like a big deal to me. I just occasionally notice that apparently, some weeks ago there was a new release and I didn't know.
Therefore, I'm suggesting that like the default configuration for Ubuntu Server, the ssh login banner should include the output of some program that tells me if there is a new stable Alpine release out that is newer than the one I'm currently running so that as soon as I touch the server login I immediately will be aware if an upgrade is to be done. On Ubuntu, that has helped me greatly not miss the upgrades which I think would be a win for everyone, since you get earlier adoption and I get more up-to-date patches for security.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14416Package request: cockpit2023-12-05T02:20:13ZA. KlitzingPackage request: cockpitA WebUI management for qemu/kvm.
https://cockpit-project.org/
https://archlinux.org/packages/?q=cockpitA WebUI management for qemu/kvm.
https://cockpit-project.org/
https://archlinux.org/packages/?q=cockpithttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/10086default_doc: Does not compress info pages2022-12-04T11:29:13ZSören Tempeldefault_doc: Does not compress info pagesWhile cleaning up the -doc subpackage of `community/emacs`, I noticed that abuild's `default_doc` function does compress man pages but doesn't deal with the compression of GNU info pages. We don't have a lot of packages which ship info p...While cleaning up the -doc subpackage of `community/emacs`, I noticed that abuild's `default_doc` function does compress man pages but doesn't deal with the compression of GNU info pages. We don't have a lot of packages which ship info pages but I think it might be worthwhile to ensure that they are also compressed by abuild and that abuild performs a sanity check (similar to the existing one for man pages) which ensures that no uncompressed info pages are shipped in a `-doc` subpackage.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10544setup-desktop: run automatically during setup-alpine2023-12-01T15:18:44ZPatrycja Rosaalpine@ptrcnull.mesetup-desktop: run automatically during setup-alpinecurrently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an ...currently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an option to not install any desktop at allhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14435Missing ASAN with clang for s390x2022-12-09T22:04:26ZGleb MazovetskiyMissing ASAN with clang for s390xclang has supported ASAN with musl since https://reviews.llvm.org/D93848.
The Alpine package is missing the necessary files:
```
/usr/bin/ld: cannot find /usr/lib/clang/15.0.6/lib/linux/libclang_rt.asan_static-s390x.a: No such file or d...clang has supported ASAN with musl since https://reviews.llvm.org/D93848.
The Alpine package is missing the necessary files:
```
/usr/bin/ld: cannot find /usr/lib/clang/15.0.6/lib/linux/libclang_rt.asan_static-s390x.a: No such file or directory
/usr/bin/ld: cannot find /usr/lib/clang/15.0.6/lib/linux/libclang_rt.asan-s390x.a: No such file or directory
/usr/bin/ld: cannot find /usr/lib/clang/15.0.6/lib/linux/libclang_rt.asan_cxx-s390x.a: No such file or directory
```https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10087rootbld fails if abuild.conf is symbolic link2022-12-09T13:20:20ZSean Enckrootbld fails if abuild.conf is symbolic linkWhen running `abuild rootbld` it appears to fail if my `$HOME/.abuild/abuild.conf` is a symbolic link (e.g. for me it links to `$HOME/.env/abuild.conf`).
Looking through the source for `abuild` it looks like `abuild-sign --installed` is...When running `abuild rootbld` it appears to fail if my `$HOME/.abuild/abuild.conf` is a symbolic link (e.g. for me it links to `$HOME/.env/abuild.conf`).
Looking through the source for `abuild` it looks like `abuild-sign --installed` is checked (before entering `bwrap`) and confirms my key is setup but once we're in the chroot, the link probably no longer resolves and therefore my config/key can't be found.
I'm just doing some simple, local packaging - I've attached the log for reference though the only warning/error is the failed signing. I've locally resolved this by making my `abuild.conf` a regular file
[log.txt](/uploads/1e4202fa8a96e173a0fc1ceb7d83837a/log.txt)https://gitlab.alpinelinux.org/alpine/aports/-/issues/14440knot: Enable XDP and DoQ2024-03-27T19:28:32ZJeremy Sakladknot: Enable XDP and DoQAlpine Linux 3.17 supports XDP, which has the potential to be much more performant than normal network traffic. However, Knot DNS is currently not compiled with support for it enabled.
This can be seen by looking at the [recent build lo...Alpine Linux 3.17 supports XDP, which has the potential to be much more performant than normal network traffic. However, Knot DNS is currently not compiled with support for it enabled.
This can be seen by looking at the [recent build log](https://build.alpinelinux.org/buildlogs/build-3-17-x86_64/main/knot/knot-3.2.2-r0.log#line=313,314;md5=9e1736e43204f79c0630218508bb470a). That will also show that it does not have support for DNS-over-QUIC included: I am also looking to use that, and would like it enabled as well.Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14443community/prismlauncher: Minecraft 1.19.3 and above do not launch2023-02-05T14:52:40Zknuxifycommunity/prismlauncher: Minecraft 1.19.3 and above do not launchRelated issue: https://github.com/PolyMC/PolyMC/issues/779, where older LWJGL versions would not launch with gcompat installed due to some missing instructions. This is a new issue, started when LWJGL 3.3.1 was introduced.
So far, it wa...Related issue: https://github.com/PolyMC/PolyMC/issues/779, where older LWJGL versions would not launch with gcompat installed due to some missing instructions. This is a new issue, started when LWJGL 3.3.1 was introduced.
So far, it was enough to revert to LWJGL 3.2.2 to get Minecraft to run. **This no longer works starting from Minecraft 1.19.3**, and Minecraft will complain about a missing method:
```
java.lang.NoSuchMethodError: 'org.lwjgl.glfw.GLFWImage$Buffer org.lwjgl.glfw.GLFWImage.malloc(int, org.lwjgl.system.MemoryStack)'
at net.minecraft.class_1041.method_4491(class_1041.java:157)
at net.minecraft.class_310.<init>(class_310.java:497)
at net.minecraft.client.main.Main.method_44604(Main.java:205)
at net.minecraft.client.main.Main.main(Main.java:51)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:461)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.prismlauncher.impl.OneSixLauncher.invokeMain(OneSixLauncher.java:104)
at org.prismlauncher.impl.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:176)
at org.prismlauncher.impl.OneSixLauncher.launch(OneSixLauncher.java:186)
at org.prismlauncher.EntryPoint.listen(EntryPoint.java:144)
at org.prismlauncher.EntryPoint.main(EntryPoint.java:74)
```
Switching to LWJGL 3.3.1 instead results in a SIGSEGV. A crash log has been attached below:
[hs_err_pid20065.log](/uploads/d63de28991f32c34387fb56c69555e16/hs_err_pid20065.log)
I also observed the following error when trying LWJGL 3.3.1 on 1.18.2 with mods (but not without mods):
```
...
Caused by: java.lang.UnsatisfiedLinkError: /tmp/lwjglknuxify/3.3.1-build-7/liblwjgl_stb.so: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /tmp/lwjglknuxify/3.3.1-build-7/liblwjgl_stb.so)
```
## What now?
This isn't a Prism issue as much as it's an LWJGL issue. I'm filing it under community/prismlauncher because it's directly affected (and I'm the maintainer of that package).
Some of the issues with linking to glibc libraries would be solved by rebuilding LWJGL under a Musl system. I'm not sure what to do about the crash in the provided crash log, though. Nonetheless, fixing it would likely involve forking LWJGL and figuring out how to build and patch it.
I've tried to make an LWJGL3 package, and my work can be found here: https://gitlab.alpinelinux.org/knuxify/aports/-/blob/lwjgl/testing/lwjgl3/
However, this is an incredibly janky solution, as many of the modules in LWJGL link against forks of various libraries - see the repositories in https://github.com/LWJGL-CI. My package tries to link to some system libraries, but this probably isn't how LWJGL was meant to be built.
The more correct option would be to build all of the forked libraries and LWJGL itself separately, upload the resulting .jar files to a server somewhere, then modify Prism to load a modified version of https://github.com/PrismLauncher/meta-launcher/blob/master/org.lwjgl3/3.3.1.json which downloads the musl packages instead (or figure out how the OS is detected here, add a "musl" target and add the links upstream).
There might also be the option of asking upstream LWJGL to consider adding musl builds, but I'm not sure if there's enough of an userbase for them to consider it.
I'm opening this issue in case anybody would like to look into this. I currently don't really have the time for it, but might try to do it over the christmas break.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14457[3.16] Routing issues due to 'throw' routes appearing2022-12-14T19:19:53ZKevin Daudt[3.16] Routing issues due to 'throw' routes appearingOn a ppc64le host, after upgrading to Alpine Linux 3.16, there are issues with inserting certain routes.
Output from `ip route` (partial):
```
throw 172.16.0.254 proto static
172.16.0.254 dev gre1 proto zebra scope link metric 20
throw...On a ppc64le host, after upgrading to Alpine Linux 3.16, there are issues with inserting certain routes.
Output from `ip route` (partial):
```
throw 172.16.0.254 proto static
172.16.0.254 dev gre1 proto zebra scope link metric 20
throw 172.16.0.255 proto static
172.16.0.255 dev gre1 proto zebra scope link metric 20
```
These throw routes prevent traffic reaching those destinations, and also can prevent routes being installed (probably due to routes for those prefixes already existing). This happens for example with docker and lxc. I need to manually remove these routes and add the expected routes.
This host is running dmvpn. A possible cause may be strongswan, which searching online seems to make use of `throw` routes. a1ece8d enabled `bypass-lan`, but a build without that option does not appear to fix it.
Kernel: 5.15.76-0-lts, trying an older kernel does not fix it.https://gitlab.alpinelinux.org/alpine/aports/-/issues/14460/sbin/bootchartd missed in initramfs-rpi42022-12-15T15:40:35Zyf liu/sbin/bootchartd missed in initramfs-rpi4Dear expert,
When started with `chart` in `cmdline.txt` on rpi4b device using `alpine-rpi-v3.16.3.tar.gz`, I noticed errors like:
```
/init: line 397: /sbin/bootchartd: not found
```
please teach how to fix it?
Regards,
yfDear expert,
When started with `chart` in `cmdline.txt` on rpi4b device using `alpine-rpi-v3.16.3.tar.gz`, I noticed errors like:
```
/init: line 397: /sbin/bootchartd: not found
```
please teach how to fix it?
Regards,
yfhttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/10088Versions not complying with the rules in APKBUILD2024-03-06T11:55:52ZRex PVersions not complying with the rules in APKBUILDThere are multiple packages with versions that seem to be invalid according to the APKBUILD.5.scd documentation.
For example
- `libretls` on Alpine v3.14 has a pkgver=3.3.3p1
- `sudo` on Alpine v3.12 - v3.15 has a pkgver=1.9.5p2
- `open...There are multiple packages with versions that seem to be invalid according to the APKBUILD.5.scd documentation.
For example
- `libretls` on Alpine v3.14 has a pkgver=3.3.3p1
- `sudo` on Alpine v3.12 - v3.15 has a pkgver=1.9.5p2
- `opensmtpd` on Alpine v3.11 - v3.16 has pkgver=6.6.2p1
They all seem to be missing the `_` between `p` and the number before it. Is the APKBUILD.5.scd documentation outdated and these version should be allowed, or are these all typos and invalid versions?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 Tempel