alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2020-11-17T16:37:42Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12113Dependencies on gammu component broken: Cannot delete SMS messages2020-11-17T16:37:42ZOscar CalvoDependencies on gammu component broken: Cannot delete SMS messagesA [gammu issue](https://github.com/gammu/gammu/issues/460) is preventing dependencies to delete SMS messages.
This [has been fixed](https://wammu.eu/news/2020/10/03/gammu-1-42-0/), however we need to release a bug fix release of Alpine s...A [gammu issue](https://github.com/gammu/gammu/issues/460) is preventing dependencies to delete SMS messages.
This [has been fixed](https://wammu.eu/news/2020/10/03/gammu-1-42-0/), however we need to release a bug fix release of Alpine so that it can be consumed by [Home Assistant](https://github.com/home-assistant/core/issues/40462).Scrumpy JackScrumpy Jackhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12110wkhtmltopdf segfaults2021-08-07T16:59:34ZPaul Zillmannwkhtmltopdf segfaultsThe package `wkhtmltopdf` segfaults at about 30 to 40% of it's progress.
This is reproducible with the 3.12 repo and the edge repo.
Example call: `wkhtmltopdf https://google.com /tmp/google.pdf`The package `wkhtmltopdf` segfaults at about 30 to 40% of it's progress.
This is reproducible with the 3.12 repo and the edge repo.
Example call: `wkhtmltopdf https://google.com /tmp/google.pdf`Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10722Support for Optional Dependencies2024-01-21T09:12:24ZBenSupport for Optional DependenciesSome software has dependencies that are not strictly required for core operation, but add functionality. It would be helpful if there was a way to represent this in APKs, notify the user of these during installation, and allow the user t...Some software has dependencies that are not strictly required for core operation, but add functionality. It would be helpful if there was a way to represent this in APKs, notify the user of these during installation, and allow the user to install them as well when the -i flag is provided.backloghttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11528too hard to report bugs2022-07-06T13:40:42ZDan Ackroydtoo hard to report bugsHi,
My name is Danack, and I maintain the PHP Imagick library http://pecl.php.net/package/imagick
It seems that it is really hard for people using Imagick on Alpine to report Alpine related issues. I've had multiple users report issues...Hi,
My name is Danack, and I maintain the PHP Imagick library http://pecl.php.net/package/imagick
It seems that it is really hard for people using Imagick on Alpine to report Alpine related issues. I've had multiple users report issues at https://github.com/Imagick/imagick/ even though as part of the bug report they say something along the lines of:
"Apologies for posting this here, I didn't know where better to post it."
I think they have a point. Even if you know the alpine Imagick project page is here: https://pkgs.alpinelinux.org/package/edge/community/x86/php7-pecl-imagick
Figuring out how to open a bug for the package is not trivial.
There is no 'report a bug' button on that page and clicking on 'bugs' takes me to https://gitlab.alpinelinux.org/ - which 'somewhat surprisingly' does not have any way of reporting bugs on it.
I really think the page at https://pkgs.alpinelinux.org/package/edge/community/x86/php7-pecl-imagick should have a "Report a bug" button that takes the user directly to the correct page to open a bug for that project. Or just a link to view bugs for that project, that has the 'new issue' button on that page.
Oh wow - does this bug reporting system not allow me to select packages......that's not great.
cheers
Dan
Ack
ps - I don't like the word bug. The word 'issue' is far more neutral. e.g. a missing feature is an issue, not a bug.https://gitlab.alpinelinux.org/alpine/aports/-/issues/11002Roadmap to PHP 7.42020-07-03T00:37:22ZMarco Aurélio DeleuRoadmap to PHP 7.4# Goal
Make all dependent packages on `php7` or `php7-fpm` compatible with PHP 7.4
The next version PHP 8 scheduled for December https://wiki.php.net/todo/php80 so it will give a window for apps to make them compatible
## Compatible ...# Goal
Make all dependent packages on `php7` or `php7-fpm` compatible with PHP 7.4
The next version PHP 8 scheduled for December https://wiki.php.net/todo/php80 so it will give a window for apps to make them compatible
## Compatible list
- https://pkgs.alpinelinux.org/packages?name=nextcloud
- https://pkgs.alpinelinux.org/packages?name=composer
- https://pkgs.alpinelinux.org/packages?name=phpmyadmin
- icingaweb2 needs upgrade to https://github.com/Icinga/icingaweb2/releases/tag/v2.8.0-rc1
- cacti-php7, nextcloud, rutorrent, speedtest
## Incompatible
Should be patched or moved to unmaintained
- https://pkgs.alpinelinux.org/packages?name=drupal7
- https://pkgs.alpinelinux.org/packages?name=phpldapadmin https://github.com/leenooks/phpLDAPadmin/pull/97
## To review
The list is from "Required by (27)" https://pkgs.alpinelinux.org/package/edge/community/x86_64/php7
- https://pkgs.alpinelinux.org/packages?name=phabricator & libphutil & arcanist (dependencies)
- bareos-webui, hiawatha, phoronix-test-suite, rainloop-webmail, racktables, postfixadmin - most probably will work
- ltb-project-ssp, zabix, zoneminder
**Original summary**
Hi everyone. I've been using Alpine for quite some time now and with the release of PHP 7.4 I was trying to google around how to contribute the installation of PHP 7.4 to Alpine. Unfortunately my searches hasn't yield great results yet except finding the Wiki that points here for a "Request for new package".
If someone could point me to where I could find information on contributing to getting PHP 7.4 on the 3.11, that would be great!3.13.0https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10637Improve CI for aports2021-11-12T15:58:41ZKevin DaudtImprove CI for aportsCurrently we only try to build changed packages, but there are other things we can test / verify. This is a meta issue to track the different CI tests.
* [x] building packages
* [x] Extract ci scripts to allow adding tagged images: al...Currently we only try to build changed packages, but there are other things we can test / verify. This is a meta issue to track the different CI tests.
* [x] building packages
* [x] Extract ci scripts to allow adding tagged images: alpine/infra/docker/docker-cli!3
* [x] Let `docker-image.yml` use the scripts added to docker-cli: alpine/infra/gitlab-ci-templates!2
* [x] Convert drone-ci to gitlab-ci: alpine/infra/docker/alpine-gitlab-ci!2
* [x] Enable CI job on aports: alpine/aports!74
* [x] Builders on different arches
* [x] x86_64
* [x] x86
* [x] Allow specifying the arch for the base image: alpine/infra/docker/docker-cli!4
* [x] Specify the arch for the base image: alpine/infra/gitlab-ci-templates!3
* [x] armhf
* [x] armv7
* [x] aarch64
* [x] s390x
* [x] ppc64le
* [x] codestyle linting
* [x] Move shellcheck to community alpine/aports!19
* [x] Create docker container with required tools: alpine/infra/docker/apkbuild-lint-tools!1
* [x] Enable linting in Aports: alpine/aports!25
* [ ] cyclic dependency testing (#10676)
* [ ] dependencies on 'lower' repositories
* [x] verify secfix yaml syntax
* [ ] ~~generate alpine-seclist from master~~Kevin DaudtKevin Daudthttps://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10651APK should have --force-reinstall option2022-12-21T20:00:36ZAndrey LAPK should have --force-reinstall optionHello!
Sometimes it’s needed to reinstall package overwriting all files
included in package
There should an easy way to do it.
*(from redmine: issue id 10303, created on 2019-04-19)*Hello!
Sometimes it’s needed to reinstall package overwriting all files
included in package
There should an easy way to do it.
*(from redmine: issue id 10303, created on 2019-04-19)*v3.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/7946nss-pam-ldapd missing libnss_ldap.so.22020-10-23T08:58:45Zalgitbotnss-pam-ldapd missing libnss_ldap.so.2After installing and configuring nss-pam-ldapd I get the following error
when starting the nslcd service:
nslcd: Warning: NSS\_LDAP module not loaded: Error loading shared
library libnss\_ldap.so.2: No such file or directory
*(from re...After installing and configuring nss-pam-ldapd I get the following error
when starting the nslcd service:
nslcd: Warning: NSS\_LDAP module not loaded: Error loading shared
library libnss\_ldap.so.2: No such file or directory
*(from redmine: issue id 7946, created on 2017-09-29)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/6710Package request: nss_wrapper2022-09-21T11:16:54ZDennis SchriddePackage request: nss_wrapperPlease package nss\_wrapper: https://cwrap.org/nss\_wrapper.html
It is a small library that allows to fake NSS passwd and group
information, by filling a custom passwd file with “fake” information
that is used by programs started with L...Please package nss\_wrapper: https://cwrap.org/nss\_wrapper.html
It is a small library that allows to fake NSS passwd and group
information, by filling a custom passwd file with “fake” information
that is used by programs started with LD\_PRELOADing nss\_wrapper.
This is especially useful inside a container, where information about
the executing user might not be available in /etc/passwd, because it was
specified on the Docker command-line using the —user argument. In such
situation it is necessary to create a custom passwd file containing
information about this user, since some programs require this to work
properly.
*(from redmine: issue id 6710, created on 2017-01-20)*https://gitlab.alpinelinux.org/alpine/tsc/-/issues/76Handling of aports which invoke external package managers2024-03-06T20:54:35ZSören TempelHandling of aports which invoke external package managersAlpine packages for programming languages like Rust/Go/Haskell currently relying on invoking the package manager of this programming language from within the APKBUILD. As such, dependencies of such packages are not properly tracked by ap...Alpine packages for programming languages like Rust/Go/Haskell currently relying on invoking the package manager of this programming language from within the APKBUILD. As such, dependencies of such packages are not properly tracked by apk. This leads to a variety of issues, most importantly:
1. We cannot reason about the dependencies using apk.
2. Patching dependencies of such packages is almost impossible.
This has [security implications](https://blogs.gentoo.org/mgorny/2021/02/19/the-modern-packagers-security-nightmare/). As a recent case in point, finding and patching packages which are vulnerable to the recent [Terrapin SSH attack](https://gitlab.alpinelinux.org/alpine/aports/-/issues/15593#note_363967) is very cumbersome. With the every increasing amount of Go and Rust packages, this problem will become even more relevant in the future. Therefore, I believe we should attempt to improve our packaging guidelines for such software.
The following may be potential solutions:
1. Package the source code of Rust/Go dependencies (the Debian approach) [\[1\]](https://wiki.debian.org/Teams/RustPackaging) [\[2\]](https://go-team.pages.debian.net/packaging.html).
2. Track additional metadata within the generated APK which at least allows us to identify vendored dependencies and their pinned version.
Note though that the second solution is only partial as it does not resolve the patching problem.
Additional suggestions regarding solutions for the outlined problems are more than welcome!https://gitlab.alpinelinux.org/alpine/aports/-/issues/15594community/firefox: firefox tries to download and run widevinecdm2024-03-27T19:28:57ZHugo Barreracommunity/firefox: firefox tries to download and run widevinecdmFirefox tries (as per the upstream default) to download the DRM plugin `widevinecdm` and execute it.
It tries to do so even if the plugin is not available for the current platform, so it downloads this binary for GNU/Linux, and reports ...Firefox tries (as per the upstream default) to download the DRM plugin `widevinecdm` and execute it.
It tries to do so even if the plugin is not available for the current platform, so it downloads this binary for GNU/Linux, and reports that it crashed. This happens automatically when visiting a website that uses DRM.
I think the aport should disable this feature, given that it is not supported on musl/linux anyway.Patrycja Rosaalpine@ptrcnull.mePatrycja Rosaalpine@ptrcnull.mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15591package request: yq (not go-yq)2024-02-24T14:46:14ZBen Widawskypackage request: yq (not go-yq)https://github.com/kislyuk/yq
This project is useful for the xq command to use jqlang on XML.https://github.com/kislyuk/yq
This project is useful for the xq command to use jqlang on XML.Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15570Can't start containers with Docker when resources are set2024-03-27T19:28:58ZNazar MokrynskyiCan't start containers with Docker when resources are setWhen resources are specified for Docker container, it can no longer start after latest upgrade to stable Alpine Linux with this:
```
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime...When resources are specified for Docker container, it can no longer start after latest upgrade to stable Alpine Linux with this:
```
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: cannot enter cgroupv2 "/sys/fs/cgroup/docker" with domain controllers -- it is in domain threaded mode: unknown
```
Example resources (docker compose):
```yml
deploy:
resources:
limits:
cpus: "4.0"
memory: 4G
```
It worked fine before and I already enabled cgroups v2 as described in https://wiki.alpinelinux.org/wiki/OpenRC#cgroups_v2 and rebooted machine just in case.3.19.1Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15435Make more use of supervise-daemon in OpenRC service?2023-11-07T12:47:28ZSören TempelMake more use of supervise-daemon in OpenRC service?As of OpenRC 0.51, supervise-daemon is [no longer considered experimental](https://github.com/OpenRC/openrc/commit/18e53f7fed1a92dd6dc91e79ab620d22fee1e195). Maybe we should make more us of it in our OpenRC services now? I believe it to ...As of OpenRC 0.51, supervise-daemon is [no longer considered experimental](https://github.com/OpenRC/openrc/commit/18e53f7fed1a92dd6dc91e79ab620d22fee1e195). Maybe we should make more us of it in our OpenRC services now? I believe it to be superior to the pidfile-based service status tracking employed by OpenRC by default.
Thoughts?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15357IpTables does not properly shut down (/etc/init.d/iptables).2024-03-27T19:28:57ZCarlo MonteIpTables does not properly shut down (/etc/init.d/iptables).Error message during poweroff: "Your Kernel lacks iptables support, please load\nappropriate modules and try again.".
The problem is apparent in edge, but not in 3.18.
The reason is a test for /proc/net/ip_tables_names in /etc/init.d/ip...Error message during poweroff: "Your Kernel lacks iptables support, please load\nappropriate modules and try again.".
The problem is apparent in edge, but not in 3.18.
The reason is a test for /proc/net/ip_tables_names in /etc/init.d/iptables; ip_tables_names is missing.
Iptables seems to work perfectly, as shown in "iptables -L -n -v".
Yet, the /proc file is never created.
In /etc/init.d/iptables, ip_tables_names is not used for anything else except the existance check.Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15297package request: opentofu2023-10-16T20:33:18Zomniomni+alpine@hack.orgpackage request: opentofuAs we're talking about dropping, amongst others, `community/terraform` it would be nice to package the replacement [opentofu](https://opentofu.org/).
!52139 #15193As we're talking about dropping, amongst others, `community/terraform` it would be nice to package the replacement [opentofu](https://opentofu.org/).
!52139 #151933.19.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/15149audacious-plugins: Enable Opus and PipeWire support2023-07-31T21:49:30ZThomas Langeaudacious-plugins: Enable Opus and PipeWire supportAudacious 4.3 supports an Opus and PipeWire plugin which are not enabled on Alpine Linux.
Please consider adding `opusfile-dev` and `pipewire-dev` as make-dependency.
See also: https://audacious-media-player.org/news/56-audacious-4-3-r...Audacious 4.3 supports an Opus and PipeWire plugin which are not enabled on Alpine Linux.
Please consider adding `opusfile-dev` and `pipewire-dev` as make-dependency.
See also: https://audacious-media-player.org/news/56-audacious-4-3-releasedhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14992openssl out of date because the arm builders are offline2023-06-16T15:41:24ZMarcelloopenssl out of date because the arm builders are offlineOn 2023-05-30 openssl for x86 arch was updated to 3.1.1-r1 but arm arch still on 3.1.0-r4
https://pkgs.alpinelinux.org/packages?name=openssl&branch=v3.18&repo=&arch=&maintainer=
Is there a reason why its not updated?On 2023-05-30 openssl for x86 arch was updated to 3.1.1-r1 but arm arch still on 3.1.0-r4
https://pkgs.alpinelinux.org/packages?name=openssl&branch=v3.18&repo=&arch=&maintainer=
Is there a reason why its not updated?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10554setup-repos sets wrong repositories2023-08-28T06:52:31ZHGpunktTsetup-repos sets wrong repositoriesWhen bootet via netboot from
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/vmlinuz-lts
with
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/initramfs-lts
`# setup-apkrepos`
inserts repositor...When bootet via netboot from
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/vmlinuz-lts
with
https://dl-cdn.alpinelinux.org/alpine/v3.17/releases/x86_64/netboot/initramfs-lts
`# setup-apkrepos`
inserts repository names from **edge** and not from **v3.17** into `/etc/apk/repositories`Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/tsc/-/issues/66armhf status2023-11-02T21:29:51ZGhost Userarmhf statuschoices:
- drop
- keep
prior discussion:
- https://lists.alpinelinux.org/~alpine/devel/%3C20200528104748.4d37ede5%40ncopa-desktop.copa.dup.pw%3E
reasons for keep:
- some (seemingly mostly abandoned?) postmarketos devices. almo...choices:
- drop
- keep
prior discussion:
- https://lists.alpinelinux.org/~alpine/devel/%3C20200528104748.4d37ede5%40ncopa-desktop.copa.dup.pw%3E
reasons for keep:
- some (seemingly mostly abandoned?) postmarketos devices. almost all of these use not-up-to-date-kernels now
+ slightly dated issue in pmos: https://gitlab.com/postmarketOS/pmaports/-/issues/599
- the [rpi0](https://www.raspberrypi.com/products/raspberry-pi-zero/) and [rpi0 w](https://www.raspberrypi.com/products/raspberry-pi-zero-w/)
+ these are produced until 2026, and are quite popular.
+ however, almost no other devices really use this architecture, [except...](https://social.hackerspace.pl/@q3k/109673111874789884)
reasons for drop:
- toolchain support for armv6 only gets increasingly poorer. issues such as https://github.com/llvm/llvm-project/issues/41201 have existed for years without resolution, and that one specifically causes e.g. [rust to fail](https://gitlab.alpinelinux.org/alpine/aports/-/issues/14667) without applying workaround
+ of course, one could say this is niche to our setup. it also cost me dozens of hours until clandmeter remembered what the issue was...
- most patches to 'fixing something on armhf' are usually something of a weirder hack and never upstream. i don't have any links, however
- the 'passive costs' of keeping an architecture
+ niche failures cause someone to look at them at least once, take up CI time, ..
+ a (mostly) full built package set takes mirror space, including every release
+ some people find it 'annoying' to do `arch="all !arch"` and try to enable things on every arch even when it does not make sense, and spend both their own time and maintenance time on things like enabling packages that don't have value (graphical apps, ..)
+ (so by dropping it, the `!arch` is not even needed in that case and nobody thinks about it)
currently the status can be summarised as follows:
- armhf is enabled, some stuff like qt5 is disabled on it
- when something doesn't build on armhf, it just gets disabled and everyone moves on. no time spent on it
+ this is okay, as practically nothing disabled would be ran on these tiny 512M devices anyway (graphical apps)
continuing to do that is okay. dropping it would also have its maintenance benefits.2024-04-27