alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2024-03-25T15:53:51Zhttps://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10816Store package filename in database2024-03-25T15:53:51ZPaul SpoorenStore package filename in databaseCurrently the filename of packages is automatically generated based on the following structure:
```
<name>-<version>.apk
```
In OpenWrt, we currently use the structure below:
```
<name>_<version>-<arch>.ipk
```
We even use script for...Currently the filename of packages is automatically generated based on the following structure:
```
<name>-<version>.apk
```
In OpenWrt, we currently use the structure below:
```
<name>_<version>-<arch>.ipk
```
We even use script for cleaning up outdated packages that specifically look for the underscore (`<name>_`) in filenames.
I'm wondering if we could simply store the filename inside the index instead of enforcing a specific structure. For example, if I only provide a single package in multiple architectures, I could just fill a single folder with `<package>-<version>-<arch>.apk` instead of maintaining a variety of subfolders.
Thoughts?v3.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/15878Freezing on "Loading hardware drivers"2024-03-25T14:18:05ZGianmichele TrottaFreezing on "Loading hardware drivers"Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someon...Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someone can help me. Thanks everyone in advance.https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10985can't read --protected-paths from pipe2024-03-25T10:06:54ZSertonixcan't read --protected-paths from pipe`apk audit --protected-paths /dev/stdin` doesn't read stdin at all.
The reason seems to be that the `apk_blob_from_file` function doesn't handle pipes/fifos.`apk audit --protected-paths /dev/stdin` doesn't read stdin at all.
The reason seems to be that the `apk_blob_from_file` function doesn't handle pipes/fifos.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15881font-dejavu not properly installed2024-03-24T23:55:28Zcristian_cifont-dejavu not properly installed## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not ...## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not properly installed on Xorg. If I run `xlsfonts` (built from [sources](https://gitlab.freedesktop.org/xorg/app/xlsfonts)) command, it doesn't list dejavu font. As a result, applications that rely on it do not find the font in the right path, for some reason. I've tried to compare package() functions in archilinux's [PKGBUILD](https://gitlab.archlinux.org/archlinux/packaging/packages/ttf-dejavu/-/blob/main/PKGBUILD) and alpine's [APKBUILD](https://git.alpinelinux.org/aports/tree/main/font-dejavu/APKBUILD).
When I remove and reinstall the package, I get:
```
alpine-test:~$ doas apk del font-dejavu
(1/1) Purging font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 314 MiB in 958 packages
alpine-test:~$
```
```
alpine-test:~$ doas apk add font-dejavu
(1/1) Installing font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 324 MiB in 959 packages
alpine-test:~$
```
So, I've compared also [fontconfig](https://git.alpinelinux.org/aports/tree/main/fontconfig/fontconfig.trigger) and [mkfontscale](https://git.alpinelinux.org/aports/tree/main/mkfontscale/mkfontscale.trigger) triggers with the respective archlinux's hooks.
Still, I can't figure out why the path is wrong and is not listed by xlsfonts, after font-dejavu installation.
While at it, I noticed that font-dejavu's APKBUILD doesn'install the [LICENSE](https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE) file into `/usr/share/licenses`, unlike archlinux's PKGBUILD (likely that's not required by alpine)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15912ipv6 config issue?2024-03-24T23:51:35ZPikuZhengipv6 config issue?I need to get ipv6 ip from RA while configuring static ip like windows:
```
连接特定的 DNS 后缀 . . . . . . . : lan
IPv6 地址 . . . . . . . . . . . . : 2408:832e:.................<-------------from RA
IPv6 地址 . . . . . . . . . . . . : fd...I need to get ipv6 ip from RA while configuring static ip like windows:
```
连接特定的 DNS 后缀 . . . . . . . : lan
IPv6 地址 . . . . . . . . . . . . : 2408:832e:.................<-------------from RA
IPv6 地址 . . . . . . . . . . . . : fd00::8 <-------------static IP
本地链接 IPv6 地址. . . . . . . . : fe80::......................<-------------auto privice ip
IPv4 地址 . . . . . . . . . . . . : 172.17.2.8
子网掩码 . . . . . . . . . . . . : 255.255.255.0
默认网关. . . . . . . . . . . . . : fe80::4e5e:................<-------------from RA
172.17.2.96
```
Unfortunately I can't achieve it on alpine. If I install dhcpcd, I'll get a dynamic ip while the ipv4 static ip is present. If I install dhclient it gets stuck permanently.
```
iface eth0 inet6 auto
address fd00::171/64
pre-up echo 1 > /proc/sys/net/ipv6/conf/eth0/accept_ra
```
This results in only static ip.
```
iface eth0 inet6 static
pre-up echo 1 > /proc/sys/net/ipv6/conf/eth0/accept_ra
post-up dhclient -6 eth0
```
This results in dead interface.
```
iface eth0 inet static
iface eth0 inet6 dhcp
```
This results in get ips both ipv4 and ipv6.
On the other hand, running `ping -6 ipv6 address` or `dhclient -6 eth0` will get an unresponsive system.
I looked up https://wiki.alpinelinux.org/wiki/Configure_Networking and tried many things but they don't work. hope to get help here.https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/issues/157Document what "nocloud" cloud images are2024-03-24T18:30:56ZVincent LegollDocument what "nocloud" cloud images areCould you add a small explanation about what those image variants are
on the [cloud images page](https://alpinelinux.org/cloud/)
The other variations are explained:
> Image variants are assembled for cloud-valid combinations of CPU arch...Could you add a small explanation about what those image variants are
on the [cloud images page](https://alpinelinux.org/cloud/)
The other variations are explained:
> Image variants are assembled for cloud-valid combinations of CPU architecture (aarch64, x86_64),
> firmware (BIOS/UEFI), and instance bootstrap systems (Tiny Cloud and cloud-init).
A link to a more in-depth documentation of those "nocloud" images would be really nice. I don't know if such doc exists,
My personnal question wrt the "nocloud" images, is: "are they suitable for PCIe (or USB) device passthrough", which translates to "do they have all the drivers for *real hardware* instead of just the virtual ones".https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/issues/130Support Bare Metal Cloud Images2024-03-24T18:25:51ZJake Buchholz GöktürkSupport Bare Metal Cloud ImagesThis will probably involve using `linux-lts` instead of `linux-virt`.This will probably involve using `linux-lts` instead of `linux-virt`.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15384main/hylafaxplus: incompatible with tiff 4.62024-03-24T17:03:55ZAndy Postnikovmain/hylafaxplus: incompatible with tiff 4.6https://sourceforge.net/p/hylafax/mailman/hylafax-users/thread/98726dcd-c00a-fd7a-8f75-88da70a54b84%40howardsilvan.com/https://sourceforge.net/p/hylafax/mailman/hylafax-users/thread/98726dcd-c00a-fd7a-8f75-88da70a54b84%40howardsilvan.com/Francesco ColistaFrancesco Colistahttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/9016Support GnuPG public keys as an alternative to checksums2024-03-24T16:17:48ZalgitbotSupport GnuPG public keys as an alternative to checksumsSigned packages provide more security than checksums, e.g. in the case
of corrupt mirrors or download sites.
The private key is only owned by the devs or release managers. All users
can use the well known public key to verify their dow...Signed packages provide more security than checksums, e.g. in the case
of corrupt mirrors or download sites.
The private key is only owned by the devs or release managers. All users
can use the well known public key to verify their downloads. As an
additional feature, the key can be fetched from keyservers, so
corrupt/revoked keys will throw an error.
e.g. in the case of nginx:
Fetch B0F4253373F8F6F510D42178520A9993A1C052F8 in the APKBUILD and fetch
the \*.asc together with the tarball/signed git tag.
*(from redmine: issue id 9016, created on 2018-06-16)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/15901[Package request]: dissent - a gtk4 Discord client2024-03-24T16:07:05ZMarek Ľach[Package request]: dissent - a gtk4 Discord client**Package name**: dissent
**License**: GPLv3
**Dependencies**: go
**Source code**: https://github.com/diamondburned/dissent
**Releases**: https://github.com/diamondburned/dissent/releases
**Why package it**: A native, responsive Dis...**Package name**: dissent
**License**: GPLv3
**Dependencies**: go
**Source code**: https://github.com/diamondburned/dissent
**Releases**: https://github.com/diamondburned/dissent/releases
**Why package it**: A native, responsive Discord client for Linuxhttps://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/15894[Package Request] Velox2024-03-22T20:14:05ZDave[Package Request] Velox## Package Information
* Name: velox
* Homepage: https://github.com/michaelforney/velox
## Description
`velox` is a simple window manager based on `swc`. It is inspired by `dwm` and `xmonad`.
I have tried to build from git but I'm ju...## Package Information
* Name: velox
* Homepage: https://github.com/michaelforney/velox
## Description
`velox` is a simple window manager based on `swc`. It is inspired by `dwm` and `xmonad`.
I have tried to build from git but I'm just a normie and I'm hitting errors I cant seem to get past, but I'm sure someone who is more familiar with Apline's build environment will have no trouble at all.
* description edits are just me fumbling around trying to add the package request tag.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11351RFC: disable TLS < 1.22024-03-22T16:23:02ZJ0WIRFC: disable TLS < 1.2Debian [disabled TLS < 1.2](https://lists.debian.org/debian-devel-announce/2017/08/msg00004.html) in Buster, followed by other distros.
I suggest to disable TLS < 1.2 by default for OpenSSL/GnuTLS/NSS in the next release.Debian [disabled TLS < 1.2](https://lists.debian.org/debian-devel-announce/2017/08/msg00004.html) in Buster, followed by other distros.
I suggest to disable TLS < 1.2 by default for OpenSSL/GnuTLS/NSS in the next release.Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10653"apk info" output could be a lot nicer looking2024-03-22T13:03:31ZLuca Weiss"apk info" output could be a lot nicer lookingEspecially when multiple versions of the same package are available, the output is really hard to read:
```
$ apk info mesa-dev
mesa-dev-9999-r8 description:
[c41545c2f523e9f29e94317d5378045618ba6f67] Mesa DRI OpenGL library (development...Especially when multiple versions of the same package are available, the output is really hard to read:
```
$ apk info mesa-dev
mesa-dev-9999-r8 description:
[c41545c2f523e9f29e94317d5378045618ba6f67] Mesa DRI OpenGL library (development files)
mesa-dev-9999-r8 webpage:
https://www.mesa3d.org
mesa-dev-9999-r8 installed size:
2609152
mesa-dev-9999-r7 description:
[19.1.0] Mesa DRI OpenGL library (development files)
mesa-dev-9999-r7 webpage:
https://www.mesa3d.org
mesa-dev-9999-r7 installed size:
2576384
mesa-dev-19.1.2-r1 description:
Mesa DRI OpenGL library (development files)
mesa-dev-19.1.2-r1 webpage:
https://www.mesa3d.org
mesa-dev-19.1.2-r1 installed size:
2576384
```v3.1https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/7100apk should support the use of full '$pkgname-$pkgver' atom as returned by 'ap...2024-03-22T11:45:14ZChris Giorgiapk should support the use of full '$pkgname-$pkgver' atom as returned by 'apk search -x $pkgname' everywhere '$pkgname' is usedCurrently, apk does not consider a full package atom, including version
($pkgname-$pkgver) to match a package which matches that exact atom.
For instance:
# apk search -x linux-grsec
linux-grsec-4.9.20-r0
# apk search -x $...Currently, apk does not consider a full package atom, including version
($pkgname-$pkgver) to match a package which matches that exact atom.
For instance:
# apk search -x linux-grsec
linux-grsec-4.9.20-r0
# apk search -x $(apk search -x linux-grsec)
#
This issue is present in all places where apk expects a $pkgname and
receives a complete atom in the format returned by ‘apk search -x
$pkgname’.
This behavior is counter-intuitive and leads to significant additional
effort being required in parsing within scripts calling apk to strip the
version, perform an operation with apk, then check the version actually
retrieved.
apk should accept the full atom as returned by ‘apk search -x’, and
throw an error if the version specified doesn’t match the available
$pkgver.
*(from redmine: issue id 7100, created on 2017-04-07)*v3.1Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15736let abuild manage GOCACHE, GOMODCACHE, GOTMPDIR, CARGO_HOME2024-03-21T17:52:00ZSertonixlet abuild manage GOCACHE, GOMODCACHE, GOTMPDIR, CARGO_HOMEWhen the `MOVE_CACHES` environmental variable is set abuild will export `GOCACHE`, `GOMODCACHE`, `GOTMPDIR`, `CARGO_HOME`.
A lot of `APKBUILD` files export these variables too though. I suggest removing the exports from the `APKBUILD` f...When the `MOVE_CACHES` environmental variable is set abuild will export `GOCACHE`, `GOMODCACHE`, `GOTMPDIR`, `CARGO_HOME`.
A lot of `APKBUILD` files export these variables too though. I suggest removing the exports from the `APKBUILD` files.
Since this would be a larger effort I want to know some opinions on that before starting.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/15898GNOME 46 backgrounds require `libjxl-pixbuf-loader`2024-03-21T07:44:18ZAngelo Verlain ShemaGNOME 46 backgrounds require `libjxl-pixbuf-loader`<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue....<!--
This is the issue template for reporting an issue with a specific package. You
can select a different issue template from the dropdown above. Also, feel free
to use the "No template" option in case no template applies to your issue.
Also note that this repository is intended for reporting issues with packages.
For other components, separate issue trackers exist:
* Installer issues: https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues
* Infrastructure issues: https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues
* Initramfs issues: https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues
-->
## Package Information
* Package name: *libjxl-pixbuf-loader*
* Package version: *0.9.1-r0*
* Alpine version: *3.20.0_alpha20240315*
* Alpine architecture: *x86_64*
## Summary
The new GNOME 46 `gnome-backgrounds` package ships many wallpapers in JXL format. This includes the default wallpaper. However, the package `libjxl-pixbuf-loader` required for loading these files is missing as dependency of `gnome-backgrounds`.
This is a followup to #15863
cc @andypost
## Steps to reproduce
*If applicable, please provide instructions to reproduce the issue.*https://gitlab.alpinelinux.org/alpine/aports/-/issues/15895packaging 'dotnet' based software do we have a standard way yet?2024-03-21T06:53:13ZBjörn Strömbergpackaging 'dotnet' based software do we have a standard way yet?as we have dotnet6-runtime/sdk in v3.18/9 and will have dotnet8-runtime/sdk in v3.20 in a while..
* have there been any packaging of dotnet alpine packages yet to flesh out the gremlins of nuget -> apk when it comes to shared packages?...as we have dotnet6-runtime/sdk in v3.18/9 and will have dotnet8-runtime/sdk in v3.20 in a while..
* have there been any packaging of dotnet alpine packages yet to flesh out the gremlins of nuget -> apk when it comes to shared packages?
* is this something we want?
* or is native (AOT) output good enough?
i know three paths:
* dotnet build with nuget to fetch dependencies (shared libs but duplicated per application, pretty much like how a windows app installation looks, and its horrible waste of space)
* dotnet build with nuget to fetch dependencies (AOT) with native output (much static linking, producing large binaries, with a few so files, not as bad as the previous one. the likely solution in the short term
* apk based install of dynamic libraries from nuget and somehow getting everything to work (sounds like an utopia, but we do it like that with pypi etc so i guess its a question if its worth the work?)
any input in the matter? @ayakael or anyone else using dotnet?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15896community/kgamma5: package no longer exists2024-03-21T05:05:48ZPatrycja Rosaalpine@ptrcnull.mecommunity/kgamma5: package no longer exists`kgamma5` is included in explicitly `setup-desktop` - its removal causes existing setups to keep an orphaned package in apk world, not being able to do anything with it and potentially blocking dependencies, but also making existing inst...`kgamma5` is included in explicitly `setup-desktop` - its removal causes existing setups to keep an orphaned package in apk world, not being able to do anything with it and potentially blocking dependencies, but also making existing installations fail on `apk add` and being very sad about it:
![image](/uploads/e20d3d2c1cd67f63ead23b03619089bb/image.png)Bart RibbersBart Ribbers