aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2021-02-22T20:06:56Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12456mumble: Remote code execution vulnerability (CVE-2021-27229)2021-02-22T20:06:56ZAlicha CHmumble: Remote code execution vulnerability (CVE-2021-27229)Mumble before 1.3.4 allows remote code execution if a victim navigates to a crafted URL on a server list and clicks on the Open Webpage text.
#### References:
* https://nvd.nist.gov/vuln/detail/CVE-2021-27229
* https://github.com/mumbl...Mumble before 1.3.4 allows remote code execution if a victim navigates to a crafted URL on a server list and clicks on the Open Webpage text.
#### References:
* https://nvd.nist.gov/vuln/detail/CVE-2021-27229
* https://github.com/mumble-voip/mumble/pull/4733
#### Patch:
https://github.com/mumble-voip/mumble/commit/e59ee87abe249f345908c7d568f6879d16bfd648
### Affected branches:
* [x] master (2fabc9f231b9ec75740d4bf7af9ac7b16ca59619)
* [x] 3.13-stablehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12421subversion: Remote unauthenticated denial-of-service in Subversion mod_authz_...2021-02-11T11:43:34ZAlicha CHsubversion: Remote unauthenticated denial-of-service in Subversion mod_authz_svn (CVE-2020-17525)A flaw was found in subversion versions 1.9.0 through 1.10.6 and 1.11.0 through 1.14.0. Subversion's mod_authz_svn module will crash if the server is using in-repository authz rules with the AuthzSVNReposRelativeAccessFile option and a c...A flaw was found in subversion versions 1.9.0 through 1.10.6 and 1.11.0 through 1.14.0. Subversion's mod_authz_svn module will crash if the server is using in-repository authz rules with the AuthzSVNReposRelativeAccessFile option and a client sends a request for a non-existing repository URL. This can lead to disruption for users of the service.
#### Fixed In Version:
Subversion 1.14.1, subversion 1.10.7
#### References:
* https://subversion.apache.org/security/CVE-2020-17525-advisory.txt
* https://www.openwall.com/lists/oss-security/2021/02/10/2
### Affected branches:
* [x] master (7e0b94cfbf05c8505ace4bd0992f8300db8d1b51)
* [x] 3.13-stable
* [x] 3.12-stable
* [x] 3.11-stable
* [x] 3.10-stableNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12372firefox-esr: Multiple vulnerabilities (CVE-2021-23953, CVE-2021-23954, CVE-20...2021-02-24T10:28:21ZAlicha CHfirefox-esr: Multiple vulnerabilities (CVE-2021-23953, CVE-2021-23954, CVE-2021-23960, CVE-2021-23964, CVE-2020-26976)* CVE-2021-23953: Cross-origin information leakage via redirected PDF requests
* CVE-2021-23954: Type confusion when using logical assignment operators in JavaScript switch statements
* CVE-2021-23960: Use-after-poison for incorrectly re...* CVE-2021-23953: Cross-origin information leakage via redirected PDF requests
* CVE-2021-23954: Type confusion when using logical assignment operators in JavaScript switch statements
* CVE-2021-23960: Use-after-poison for incorrectly redeclared JavaScript variables during GC
* CVE-2021-23964: Memory safety bugs
* CVE-2020-26976: HTTPS pages could have been intercepted by a registered service worker when they should not have been
#### Fixed In Version:
Firefox ESR 78.7
#### Reference:
https://www.mozilla.org/en-US/security/advisories/mfsa2021-04/
### Affected branches:
* [x] master (3bfe2035546b511130bb1e0f6aee1a9de86814d9)
* [x] 3.13-stable (7d0962393fe7a71f0191f1c1c4f4c57f09bd68f2)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12666community/php8 in 3.13 is 4 Versions behind (8.0.2 to 8.0.6)2021-08-09T01:31:38ZStephan Wentzcommunity/php8 in 3.13 is 4 Versions behind (8.0.2 to 8.0.6)community/php8 is several versions behind the current release, 8.0.6
The missing version are only bug fix releases, not security releases, but since php8 was a major upgrade, these bug fixes might be important.community/php8 is several versions behind the current release, 8.0.6
The missing version are only bug fix releases, not security releases, but since php8 was a major upgrade, these bug fixes might be important.https://gitlab.alpinelinux.org/alpine/aports/-/issues/13224Install php8-pecl-imagick 3.5.0-r0 failing2022-03-22T11:17:12ZP PandaInstall php8-pecl-imagick 3.5.0-r0 failingWhen adding php8-pecl-imagick 3.5.0-r0 on alpine-3.14 failing with following
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/aarch64/APKINDEX....When adding php8-pecl-imagick 3.5.0-r0 on alpine-3.14 failing with following
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/aarch64/APKINDEX.tar.gz
ERROR: unable to select packages:
so:libMagickCore-7.Q16HDRI.so.9 (no such package):
required by: php8-pecl-imagick-3.5.0-r0[so:libMagickCore-7.Q16HDRI.so.9]
so:libMagickWand-7.Q16HDRI.so.9 (no such package):
required by: php8-pecl-imagick-3.5.0-r0[so:libMagickWand-7.Q16HDRI.so.9]
```
Probably happening since imagemagick 7.0.11.14-r0J0WIJ0WIhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13036linux 5.10.61-r0 broke xen pci passthrough2021-11-12T13:44:23ZHenrik Riomarlinux 5.10.61-r0 broke xen pci passthroughCan not boot a XEN PV domU with pci passthrough with the `5.10.61-r0` kernel
This was fixed in `5.10.67` with the following commit
```
commit 5f13c8bae824d491e3e84ebd6efe37d6940792ca
Author: Marek Marczykowski-Górecki <marmarek@invisib...Can not boot a XEN PV domU with pci passthrough with the `5.10.61-r0` kernel
This was fixed in `5.10.67` with the following commit
```
commit 5f13c8bae824d491e3e84ebd6efe37d6940792ca
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date: Thu Aug 26 19:03:42 2021 +0200
PCI/MSI: Skip masking MSI-X on Xen PV
commit 1a519dc7a73c977547d8b5108d98c6e769c89f4b upstream.
When running as Xen PV guest, masking MSI-X is a responsibility of the
hypervisor. The guest has no write access to the relevant BAR at all - when
it tries to, it results in a crash like this:
BUG: unable to handle page fault for address: ffffc9004069100c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0003) - permissions violation
RIP: e030:__pci_enable_msix_range.part.0+0x26b/0x5f0
e1000e_set_interrupt_capability+0xbf/0xd0 [e1000e]
e1000_probe+0x41f/0xdb0 [e1000e]
local_pci_probe+0x42/0x80
(...)
The recently introduced function msix_mask_all() does not check the global
variable pci_msi_ignore_mask which is set by XEN PV to bypass the masking
of MSI[-X] interrupts.
Add the check to make this function XEN PV compatible.
Fixes: 7d5ec3d36123 ("PCI/MSI: Mask all unused MSI-X entries")
Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20210826170342.135172-1-marmarek@invisiblethingslab.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
```Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12867main/krb5-1.18.4-r0: test failure on 3.13-armv72021-08-03T19:54:04ZKevin Daudtmain/krb5-1.18.4-r0: test failure on 3.13-armv7krb5 has a test failure on 3.13-armv7:
```
*** Failure: /home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/clients/kinit/kinit failed with code 1.
*** Last mark: ktutil addent
*** Last command (#137): /home/buildozer/aports/main/krb5/...krb5 has a test failure on 3.13-armv7:
```
*** Failure: /home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/clients/kinit/kinit failed with code 1.
*** Last mark: ktutil addent
*** Last command (#137): /home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/clients/kinit/kinit -k default
*** Output of last command:
kinit: Key table file '/home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/tests/testdir/keytab' not found while getting initial credentials
For details, see: /home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/tests/testlog
Or re-run this test script with the -v flag:
cd /home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/tests
PYTHONPATH=/home/buildozer/aports/main/krb5/src/krb5-1.18.4/src/util /usr/bin/python3 ./t_keytab.py -v
Use --debug=NUM to run a command under a debugger. Use
--stop-after=NUM to stop after a daemon is started in order to
attach to it with a debugger. Use --help to see other
options.
make[1]: *** [Makefile:791: check-pytests] Error 1
```
See:
* https://build.alpinelinux.org/buildlogs/build-3-13-armv7/main/krb5/krb5-1.18.4-r0.log3.13.6J0WIJ0WIhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12789main/mariadb-10.5.10-r0: ftbts on armhf for 3.132021-06-27T12:59:06ZKevin Daudtmain/mariadb-10.5.10-r0: ftbts on armhf for 3.13For 3.13-stable, mariadb fails to build on armhf:
```
/tmp/ccMGBDbG.s:141: Error: selected processor does not support `isb' in ARM mode
/tmp/ccMGBDbG.s:618: Error: selected processor does not support `isb' in ARM mode
make[2]: *** [mys...For 3.13-stable, mariadb fails to build on armhf:
```
/tmp/ccMGBDbG.s:141: Error: selected processor does not support `isb' in ARM mode
/tmp/ccMGBDbG.s:618: Error: selected processor does not support `isb' in ARM mode
make[2]: *** [mysys/CMakeFiles/mysys.dir/build.make:1252: mysys/CMakeFiles/mysys.dir/lf_alloc-pin.c.o] Error 1
/tmp/ccOFIBhb.s: Assembler messages:
/tmp/ccOFIBhb.s:87: Error: selected processor does not support `isb' in ARM mode
make[2]: *** [mysys/CMakeFiles/mysys.dir/build.make:1395: mysys/CMakeFiles/mysys.dir/waiting_threads.c.o] Error 1
[ 17%] Building CXX object storage/rocksdb/CMakeFiles/rocksdblib.dir/rocksdb/env/env_chroot.cc.o
/tmp/cchogPgL.s: Assembler messages:
/tmp/cchogPgL.s:180: Error: selected processor does not support `isb' in ARM mode
/tmp/cchogPgL.s:262: Error: selected processor does not support `isb' in ARM mode
/tmp/cchogPgL.s:290: Error: selected processor does not support `isb' in ARM mode
make[2]: *** [mysys/CMakeFiles/mysys.dir/build.make:1278: mysys/CMakeFiles/mysys.dir/lf_hash.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:8504: mysys/CMakeFiles/mysys.dir/all] Error 2
```
See:
* https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1805267.html
* https://github.com/MariaDB/server/commit/76d2846a71a155ee2861fd52e6635e35490a9dd1
* https://build.alpinelinux.org/buildlogs/build-3-13-armhf/main/mariadb/mariadb-10.5.10-r0.log3.13.6Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12768open-iscsi does not honor exec_prefix at build time2021-06-18T14:46:29ZFrancesco Colistaopen-iscsi does not honor exec_prefix at build time```APKBUILD``` of open-iscsi has as ```exec_prefix=/usr```.
The Makefile has ```exec_prefix = /```
At build time, ```exec_prefix=/usr``` is not honored, this ends up in having binary files in ```/sbin``` rather than ```/usr/sbin```.
So...```APKBUILD``` of open-iscsi has as ```exec_prefix=/usr```.
The Makefile has ```exec_prefix = /```
At build time, ```exec_prefix=/usr``` is not honored, this ends up in having binary files in ```/sbin``` rather than ```/usr/sbin```.
So far, commit:28e8f052e8d863d85ff95ed5a4ffe6844d3ba522 has modified the path to ```/sbin``` to make it work, but this actually was incomplete, since the init has also ```iscsi-iname``` in the wrong, not existing, path.
In order to fix it, we can:
1. remove ```exec_prefix``` in Makefile and adjust the initd to have the all binaries called pointing to ```/sbin```
2. patch the Makefile in order to correct exec_prefix, still fix the initd which basically reverts commit:28e8f052e8d863d85ff95ed5a4ffe6844d3ba522
I will leave the choice to @larena since he's the maintainer.
If we go to option .2 (which I prefer) this is a possible patch (which I've tested and it's working):
```
diff --git a/Makefile b/Makefile
index 7f52cc8..32a86d3 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@
DESTDIR ?=
prefix = /usr
-exec_prefix = /
+exec_prefix = $(prefix)
sbindir = $(exec_prefix)/sbin
bindir = $(exec_prefix)/bin
mandir = $(prefix)/share/man
```
.: Francesco ColistaLeonardo ArenaLeonardo Arenahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12410Nginx lua upstream in 3.13 breaks nginx2021-06-13T01:14:20ZaptalcaNginx lua upstream in 3.13 breaks nginxInstalling package `nginx-mod-http-lua-upstream` version `1.18.0-r13`, which is the latest in Alpine 3.13 results in the following error and crash of nginx:
```
nginx: [emerg] dlopen() "/var/lib/nginx/modules/ngx_http_lua_upstream_modul...Installing package `nginx-mod-http-lua-upstream` version `1.18.0-r13`, which is the latest in Alpine 3.13 results in the following error and crash of nginx:
```
nginx: [emerg] dlopen() "/var/lib/nginx/modules/ngx_http_lua_upstream_module.so" failed (Error relocating /var/lib/nginx/modules/ngx_http_lua_upstream_module.so: lua_concat: symbol not found) in /etc/nginx/modules/20_http_lua_upstream.conf:1
```
Here's a basic test:
```
~$ docker run --rm -it alpine:3.13 /bin/sh -c 'apk add --no-cache nginx-mod-http-lua-upstream && nginx'
fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz
(1/9) Installing pcre (8.44-r0)
(2/9) Installing nginx (1.18.0-r13)
Executing nginx-1.18.0-r13.pre-install
Executing nginx-1.18.0-r13.post-install
(3/9) Installing nginx-mod-devel-kit (1.18.0-r13)
(4/9) Installing libgcc (10.2.1_pre1-r3)
(5/9) Installing luajit (2.2.0-r3)
(6/9) Installing lua-resty-lrucache (0.09-r1)
(7/9) Installing lua-resty-core (0.1.21-r0)
(8/9) Installing nginx-mod-http-lua (1.18.0-r13)
(9/9) Installing nginx-mod-http-lua-upstream (1.18.0-r13)
Executing busybox-1.32.1-r2.trigger
OK: 9 MiB in 23 packages
nginx: [emerg] dlopen() "/var/lib/nginx/modules/ngx_http_lua_upstream_module.so" failed (Error relocating /var/lib/nginx/modules/ngx_http_lua_upstream_module.so: lua_concat: symbol not found) in /etc/nginx/modules/20_http_lua_upstream.conf:1
```Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12384mysqld consumes about 100% cpu when idle on arm v72023-02-07T17:48:04ZAndre Rmysqld consumes about 100% cpu when idle on arm v7Issue is also [filed in mariadb](https://jira.mariadb.org/browse/MDEV-24756)
Fresh alpine linux 3.13 container running on an arm v7 debian 10.7 host.
The following issue appeared with alpine 3.13 packing mariadb 10.5.8 (there is no iss...Issue is also [filed in mariadb](https://jira.mariadb.org/browse/MDEV-24756)
Fresh alpine linux 3.13 container running on an arm v7 debian 10.7 host.
The following issue appeared with alpine 3.13 packing mariadb 10.5.8 (there is no issue with alpine 3.12 and mariadb 10.4.x):
- On arm v7 (32 bits) mysqld consumes about 100% cpu when idle, but still works.
- On arm v8 (64 bits) or amd64, it consumes near 0% cpu when idle as expected.
I see only one difference in start logs (but that may be irrelevant):
- arm v7 : "Using generic crc32 instructions"
- arm v8 : "Using ARMv8 crc32 instructions"
Any idea why this happens and if there is an option in mysqld to circumvent the issue?
Steps to reproduce on a new alpine container:
```
~ # apk --update --upgrade add mariadb sudo
~ # mkdir /run/mysqld
~ # chown mysql:mysql /run/mysqld
~ # sudo -su mysql
~ $ mysql_install_db
~ $ mysqld --datadir=./data
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/12381[postfix] unsupported dictionary type: hash2021-05-02T19:37:35ZJelle Smet[postfix] unsupported dictionary type: hashIt seems Postfix 3.5.9-r0 from edge has no builtin support for the (default) hash dictionary type.
I cannot find any postfix-hash package or related.
I had to revert to alpine 3.11 which offers postfix 3.4.12-r0 which works.It seems Postfix 3.5.9-r0 from edge has no builtin support for the (default) hash dictionary type.
I cannot find any postfix-hash package or related.
I had to revert to alpine 3.11 which offers postfix 3.4.12-r0 which works.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12373Problems starting Xen DomUs with linux 5.10.11 as Dom0 kernel2021-02-02T07:38:33Zomniomni+alpine@hack.orgProblems starting Xen DomUs with linux 5.10.11 as Dom0 kernelThis is a [known problem](https://lore.kernel.org/xen-devel/20210129005129.GA2452@mail-itl/T/#ma8f4a2e5cb092c92dd6496142bb1f5145bed59ad), also discussed in #alpine-devel@freenode, mentioned here for others to see.
If you find yourself h...This is a [known problem](https://lore.kernel.org/xen-devel/20210129005129.GA2452@mail-itl/T/#ma8f4a2e5cb092c92dd6496142bb1f5145bed59ad), also discussed in #alpine-devel@freenode, mentioned here for others to see.
If you find yourself having this problem
```
libxl: error: libxl_device.c:1103:device_backend_callback: Domain 1:unable to add device with path /local/domain/0/backend/vbd/3/2048
libxl: error: libxl_device.c:1103:device_backend_callback: Domain 1:unable to add device with path /local/domain/0/backend/vbd/3/2064
libxl: error: libxl_create.c:1608:domcreate_launch_dm: Domain 1:unable to add disk devices
libxl: error: libxl_device.c:1103:device_backend_callback: Domain 1:unable to remove device with path /local/domain/0/backend/vbd/3/2048
libxl: error: libxl_device.c:1103:device_backend_callback: Domain 1:unable to remove device with path /local/domain/0/backend/vbd/3/2064
libxl: error: libxl_domain.c:1529:devices_destroy_cb: Domain 1:libxl__devices_destroy failed
libxl: error: libxl_domain.c:1182:libxl__destroy_domid: Domain 1:Non-existant domain
libxl: error: libxl_domain.c:1136:domain_destroy_callback: Domain 1:Unable to destroy guest
libxl: error: libxl_domain.c:1063:domain_destroy_cb: Domain 1:Destruction of domain failed
```
the workaround is to downgrade your Dom0 kernel from linux 5.10.11-r0 to 5.10.10-r0, until the patch is backported ~~or linux 5.10.12 is released~~.3.13.2https://gitlab.alpinelinux.org/alpine/aports/-/issues/12371ansible 2.10.6 broken without ansible-base 2.10.52021-01-30T16:37:32ZAndrea Galbuseraansible 2.10.6 broken without ansible-base 2.10.5ba350dd64ccbb5e3352c93a7b760f23dec26afda was ported to stable branch while 60310aef9b24c9250e5f7bbccf0d1f1f1950e764 was not. I guess we need both, otherwise we hit errors like below:
```
$ ANSIBLE_CONFIG=ansible.cfg ansible-lint -x 701 ...ba350dd64ccbb5e3352c93a7b760f23dec26afda was ported to stable branch while 60310aef9b24c9250e5f7bbccf0d1f1f1950e764 was not. I guess we need both, otherwise we hit errors like below:
```
$ ANSIBLE_CONFIG=ansible.cfg ansible-lint -x 701 site.yml
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 568, in _build_master
ws.require(__requires__)
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 886, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 777, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (ansible-base 2.10.4 (/usr/lib/python3.8/site-packages), Requirement.parse('ansible-base<2.11,>=2.10.5'), {'ansible'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/ansible-lint", line 33, in <module>
sys.exit(load_entry_point('ansible-lint==0.0.0', 'console_scripts', 'ansible-lint')())
File "/usr/bin/ansible-lint", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 783, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/usr/lib/python3.8/site-packages/ansiblelint/__init__.py", line 23, in <module>
from ansiblelint.version import __version__
File "/usr/lib/python3.8/site-packages/ansiblelint/version.py", line 4, in <module>
import pkg_resources
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3243, in <module>
def _initialize_master_working_set():
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3226, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 570, in _build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 772, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'ansible-base<2.11,>=2.10.5' distribution was not found and is required by ansible
```Fabian AffolterFabian Affolterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12323main/bluez: 32-bit bug with musl 1.2 - Bluetooth AVRCP key events not reachin...2022-01-18T16:59:16Zmacmpimain/bluez: 32-bit bug with musl 1.2 - Bluetooth AVRCP key events not reaching input systemI'm transitioning a working PiZeroW 3.11 setup to 3.13: Pi sends audio to BT headsets, and gets AVRCP commands (play/pause/etc) from headset keys through _busybox acpi_.
On 3.13 bluetooth AVRCP events do no seem so come-up anymore from...I'm transitioning a working PiZeroW 3.11 setup to 3.13: Pi sends audio to BT headsets, and gets AVRCP commands (play/pause/etc) from headset keys through _busybox acpi_.
On 3.13 bluetooth AVRCP events do no seem so come-up anymore from connected headset at key press. Audio is ok (_bluez-alsa_).
Testing with _evtest_ does not give much clue, except no key press is detected...
Tested with several headsets which work fine on 3.11, and also ok on Ubuntu 18.04
Any hint?
```
tiny-radiocd:~$ sudo bluetoothctl
Agent registered
[Vivan BT600]# info
Device XX:XX:XX:XX:XX:XX (public)
Name: Vivan BT600
Alias: Vivan BT600
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
[Vivan BT600]#
tiny-radiocd:~$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Mitsumi Electric Apple USB Keyboard
/dev/input/event1: Logitech M4848
/dev/input/event2: MacALLY USB Two Button Mini Mouse
/dev/input/event3: Vivan BT600 (AVRCP)
Select the device event number [0-3]: 3
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x0 product 0x0 version 0x0
Input device name: "Vivan BT600 (AVRCP)"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 2 (KEY_1)
Event code 3 (KEY_2)
Event code 4 (KEY_3)
Event code 5 (KEY_4)
Event code 6 (KEY_5)
Event code 7 (KEY_6)
Event code 8 (KEY_7)
Event code 9 (KEY_8)
Event code 10 (KEY_9)
Event code 11 (KEY_0)
Event code 28 (KEY_ENTER)
Event code 52 (KEY_DOT)
Event code 59 (KEY_F1)
Event code 60 (KEY_F2)
Event code 61 (KEY_F3)
Event code 62 (KEY_F4)
Event code 63 (KEY_F5)
Event code 64 (KEY_F6)
Event code 65 (KEY_F7)
Event code 66 (KEY_F8)
Event code 67 (KEY_F9)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Event code 113 (KEY_MUTE)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 138 (KEY_HELP)
Event code 139 (KEY_MENU)
Event code 163 (KEY_NEXTSONG)
Event code 165 (KEY_PREVIOUSSONG)
Event code 166 (KEY_STOPCD)
Event code 167 (KEY_RECORD)
Event code 168 (KEY_REWIND)
Event code 171 (KEY_CONFIG)
Event code 174 (KEY_EXIT)
Event code 200 (KEY_PLAYCD)
Event code 201 (KEY_PAUSECD)
Event code 208 (KEY_FASTFORWARD)
Event code 353 (KEY_SELECT)
Event code 356 (KEY_POWER2)
Event code 358 (KEY_INFO)
Event code 362 (KEY_PROGRAM)
Event code 364 (KEY_FAVORITES)
Event code 395 (KEY_LIST)
Event code 398 (KEY_RED)
Event code 399 (KEY_GREEN)
Event code 400 (KEY_YELLOW)
Event code 401 (KEY_BLUE)
Event code 402 (KEY_CHANNELUP)
Event code 403 (KEY_CHANNELDOWN)
Event code 405 (KEY_LAST)
Event type 2 (EV_REL)
Key repeat handling:
Repeat type 20 (EV_REP)
Repeat code 0 (REP_DELAY)
Value 250
Repeat code 1 (REP_PERIOD)
Value 33
Properties:
Testing ... (interrupt to exit)
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/123213.13.0 vs. edge - cmake fails to detect C compiler ABI info2021-04-22T08:02:49ZJake Buchholz Göktürk3.13.0 vs. edge - cmake fails to detect C compiler ABI infoRan into this issue while updating/fixing `testing/galera` for #12307 ...
### 3.13.0 works...
```
% docker run --rm -it alpine:latest /bin/sh
/ # apk -U upgrade
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.g...Ran into this issue while updating/fixing `testing/galera` for #12307 ...
### 3.13.0 works...
```
% docker run --rm -it alpine:latest /bin/sh
/ # apk -U upgrade
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/x86_64/APKINDEX.tar.gz
(1/8) Upgrading musl (1.1.24-r8 -> 1.1.24-r10)
(2/8) Upgrading busybox (1.31.1-r16 -> 1.31.1-r19)
Executing busybox-1.31.1-r19.post-upgrade
(3/8) Upgrading alpine-baselayout (3.2.0-r6 -> 3.2.0-r7)
Executing alpine-baselayout-3.2.0-r7.pre-upgrade
Executing alpine-baselayout-3.2.0-r7.post-upgrade
(4/8) Upgrading libcrypto1.1 (1.1.1g-r0 -> 1.1.1i-r0)
(5/8) Upgrading libssl1.1 (1.1.1g-r0 -> 1.1.1i-r0)
(6/8) Upgrading ca-certificates-bundle (20191127-r2 -> 20191127-r4)
(7/8) Upgrading ssl_client (1.31.1-r16 -> 1.31.1-r19)
(8/8) Upgrading musl-utils (1.1.24-r8 -> 1.1.24-r10)
Executing busybox-1.31.1-r19.trigger
OK: 6 MiB in 14 packages
/ # apk add build-base cmake
(1/35) Installing libgcc (9.3.0-r2)
(2/35) Installing libstdc++ (9.3.0-r2)
(3/35) Installing binutils (2.34-r1)
(4/35) Installing libmagic (5.38-r0)
(5/35) Installing file (5.38-r0)
(6/35) Installing gmp (6.2.0-r0)
(7/35) Installing isl (0.18-r0)
(8/35) Installing libgomp (9.3.0-r2)
(9/35) Installing libatomic (9.3.0-r2)
(10/35) Installing libgphobos (9.3.0-r2)
(11/35) Installing mpfr4 (4.0.2-r4)
(12/35) Installing mpc1 (1.1.0-r1)
(13/35) Installing gcc (9.3.0-r2)
(14/35) Installing musl-dev (1.1.24-r10)
(15/35) Installing libc-dev (0.7.2-r3)
(16/35) Installing g++ (9.3.0-r2)
(17/35) Installing make (4.3-r0)
(18/35) Installing fortify-headers (1.1-r0)
(19/35) Installing patch (2.7.6-r6)
(20/35) Installing build-base (0.5-r2)
(21/35) Installing libacl (2.2.53-r0)
(22/35) Installing libbz2 (1.0.8-r1)
(23/35) Installing expat (2.2.9-r1)
(24/35) Installing lz4-libs (1.9.2-r0)
(25/35) Installing xz-libs (5.2.5-r0)
(26/35) Installing zstd-libs (1.4.5-r0)
(27/35) Installing libarchive (3.4.3-r1)
(28/35) Installing ca-certificates (20191127-r4)
(29/35) Installing nghttp2-libs (1.41.0-r0)
(30/35) Installing libcurl (7.69.1-r3)
(31/35) Installing ncurses-terminfo-base (6.2_p20200523-r0)
(32/35) Installing ncurses-libs (6.2_p20200523-r0)
(33/35) Installing rhash-libs (1.3.9-r1)
(34/35) Installing libuv (1.38.1-r0)
(35/35) Installing cmake (3.17.2-r0)
Executing busybox-1.31.1-r19.trigger
Executing ca-certificates-20191127-r4.trigger
OK: 252 MiB in 49 packages
/ # cat > CMakeLists.txt
message(STATUS "CMake version ${CMAKE_VERSION}")
cmake_minimum_required(VERSION 2.8)
project(galera-4)
/ # cmake .
-- CMake version 3.17.2
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /
```
### edge does not...
```
% docker run --rm -it alpine:latest /bin/sh -l
6a62cabdcfba:/# cat > /etc/apk/repositories
http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
6a62cabdcfba:/# apk -U upgrade
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
Upgrading critical system libraries and apk-tools:
(1/2) Upgrading musl (1.1.24-r8 -> 1.2.2-r0)
(2/2) Upgrading apk-tools (2.10.5-r1 -> 2.12.0-r4)
Executing busybox-1.31.1-r16.trigger
Continuing the upgrade transaction with new apk-tools:
(1/8) Upgrading busybox (1.31.1-r16 -> 1.32.1-r0)
Executing busybox-1.32.1-r0.post-upgrade
(2/8) Upgrading alpine-baselayout (3.2.0-r6 -> 3.2.0-r8)
Executing alpine-baselayout-3.2.0-r8.pre-upgrade
Executing alpine-baselayout-3.2.0-r8.post-upgrade
(3/8) Upgrading libcrypto1.1 (1.1.1g-r0 -> 1.1.1i-r0)
(4/8) Upgrading libssl1.1 (1.1.1g-r0 -> 1.1.1i-r0)
(5/8) Upgrading ca-certificates-bundle (20191127-r2 -> 20191127-r5)
(6/8) Upgrading ssl_client (1.31.1-r16 -> 1.32.1-r0)
(7/8) Upgrading scanelf (1.2.6-r0 -> 1.2.8-r0)
(8/8) Upgrading musl-utils (1.1.24-r8 -> 1.2.2-r0)
Executing busybox-1.32.1-r0.trigger
OK: 6 MiB in 14 packages
6a62cabdcfba:/# apk add build-base cmake
(1/36) Installing libgcc (10.2.1_pre1-r3)
(2/36) Installing libstdc++ (10.2.1_pre1-r3)
(3/36) Installing binutils (2.35.1-r1)
(4/36) Installing libmagic (5.39-r0)
(5/36) Installing file (5.39-r0)
(6/36) Installing libgomp (10.2.1_pre1-r3)
(7/36) Installing libatomic (10.2.1_pre1-r3)
(8/36) Installing libgphobos (10.2.1_pre1-r3)
(9/36) Installing gmp (6.2.1-r0)
(10/36) Installing isl22 (0.22-r0)
(11/36) Installing mpfr4 (4.1.0-r0)
(12/36) Installing mpc1 (1.2.0-r0)
(13/36) Installing gcc (10.2.1_pre1-r3)
(14/36) Installing musl-dev (1.2.2-r0)
(15/36) Installing libc-dev (0.7.2-r3)
(16/36) Installing g++ (10.2.1_pre1-r3)
(17/36) Installing make (4.3-r0)
(18/36) Installing fortify-headers (1.1-r0)
(19/36) Installing patch (2.7.6-r6)
(20/36) Installing build-base (0.5-r2)
(21/36) Installing libacl (2.2.53-r0)
(22/36) Installing libbz2 (1.0.8-r1)
(23/36) Installing expat (2.2.10-r1)
(24/36) Installing lz4-libs (1.9.2-r0)
(25/36) Installing xz-libs (5.2.5-r0)
(26/36) Installing zstd-libs (1.4.5-r3)
(27/36) Installing libarchive (3.5.1-r0)
(28/36) Installing ca-certificates (20191127-r5)
(29/36) Installing brotli-libs (1.0.9-r3)
(30/36) Installing nghttp2-libs (1.42.0-r1)
(31/36) Installing libcurl (7.74.0-r0)
(32/36) Installing ncurses-terminfo-base (6.2_p20210109-r0)
(33/36) Installing ncurses-libs (6.2_p20210109-r0)
(34/36) Installing rhash-libs (1.4.1-r0)
(35/36) Installing libuv (1.40.0-r1)
(36/36) Installing cmake (3.18.4-r1)
Executing busybox-1.32.1-r0.trigger
Executing ca-certificates-20191127-r5.trigger
OK: 245 MiB in 50 packages
6a62cabdcfba:/# cat > CMakeLists.txt
message(STATUS "CMake version ${CMAKE_VERSION}")
cmake_minimum_required(VERSION 2.8)
project(galera-4)
6a62cabdcfba:/# cmake .
-- CMake version 3.18.4
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc - broken
CMake Error at usr/share/cmake/Modules/CMakeTestCCompiler.cmake:66 (message):
The C compiler
"/usr/bin/cc"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: //CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_9a0ab/fast && /usr/bin/make -f CMakeFiles/cmTC_9a0ab.dir/build.make CMakeFiles/cmTC_9a0ab.dir/build
make: /usr/bin/make: Operation not permitted
make: *** [Makefile:140: cmTC_9a0ab/fast] Error 127
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
//CMakeLists.txt:3 (project)
-- Configuring incomplete, errors occurred!
See also "//CMakeFiles/CMakeOutput.log".
See also "//CMakeFiles/CMakeError.log".
6a62cabdcfba:/# cat CMakeFiles/CMakeOutput.log
The system is: Linux - 4.19.121-linuxkit - x86_64
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: /usr/bin/cc
Build flags:
Id flags:
The output was:
0
Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "a.out"
The C compiler identification is GNU, found in "//CMakeFiles/3.18.4/CompilerIdC/a.out"
Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
Compiler: /usr/bin/c++
Build flags:
Id flags:
The output was:
0
Compilation of the CXX compiler identification source "CMakeCXXCompilerId.cpp" produced "a.out"
The CXX compiler identification is GNU, found in "//CMakeFiles/3.18.4/CompilerIdCXX/a.out"
6a62cabdcfba:/# cat CMakeFiles/CMakeError.log
Detecting C compiler ABI info failed to compile with the following output:
Change Dir: //CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_9dbd3/fast && /usr/bin/make -f CMakeFiles/cmTC_9dbd3.dir/build.make CMakeFiles/cmTC_9dbd3.dir/build
make: /usr/bin/make: Operation not permitted
make: *** [Makefile:140: cmTC_9dbd3/fast] Error 127
Determining if the C compiler works failed with the following output:
Change Dir: //CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_9a0ab/fast && /usr/bin/make -f CMakeFiles/cmTC_9a0ab.dir/build.make CMakeFiles/cmTC_9a0ab.dir/build
make: /usr/bin/make: Operation not permitted
make: *** [Makefile:140: cmTC_9a0ab/fast] Error 127
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/12314Segfault on mdadm (because of Musl 1.2.2?)2021-02-24T10:45:31ZAdrienSegfault on mdadm (because of Musl 1.2.2?)Hi,
I have updated Alpine Linux from 3.12.0 to 3.13.0.
Since then, I see some segfaults in my logs:
```
mdadm[10989]: segfault at 7f9e094311db ip 00007f9e09483792 sp 00007fff90024c58 error 4 in ld-musl-x86_64.so.1[7f9e09448000+48000]
C...Hi,
I have updated Alpine Linux from 3.12.0 to 3.13.0.
Since then, I see some segfaults in my logs:
```
mdadm[10989]: segfault at 7f9e094311db ip 00007f9e09483792 sp 00007fff90024c58 error 4 in ld-musl-x86_64.so.1[7f9e09448000+48000]
Code: 84 c0 74 0d 48 8d 3c 06 48 8d 1c 01 48 39 c2 75 e3 c6 03 00 e8 0a 00 00 00 48 29 eb 5a 48 01 d8 5b 5d c3 48 89 f8 a8 07 74 0a <80> 38 00 74 3b 48 ff c0 eb f2 49 b8 ff fe fe fe fe fe fe fe 48 be
```
and
```
mdadm[11387]: segfault at 7fac20d6d283 ip 00007fac20dbf792 sp 00007ffe4047f2f8 error 4 in ld-musl-x86_64.so.1[7fac20d84000+48000]
Code: 84 c0 74 0d 48 8d 3c 06 48 8d 1c 01 48 39 c2 75 e3 c6 03 00 e8 0a 00 00 00 48 29 eb 5a 48 01 d8 5b 5d c3 48 89 f8 a8 07 74 0a <80> 38 00 74 3b 48 ff c0 eb f2 49 b8 ff fe fe fe fe fe fe fe 48 be
udevd[11249]: 'mdadm --incremental --export /dev/sde1 --offroot /dev/disk/by-id/scsi-36d0946604c1723002791c133fe851a9d-part1 /dev/disk/by-id/wwn-0x6d0946604c1723002791c133fe851a9d-part1 /dev/disk/by-partlabel/\x2fboot /dev/disk/by-partuuid/ce0c13cb-39f1-4c47-9fca-b895ae4c71ca /dev/disk/by-path/pci-0000:03:00.0-scsi-0:2:4:0-part1' [11387] terminated by signal 11 (Segmentation fault)
```
They are triggered by `udev` that executes `mdadm --incremental /dev/sda1`.
And indeed, if I run the command manually, I get a segfault:
```
# mdadm --incremental /dev/sda1
Segmentation fault
```
With gdb I got more informations:
```
(gdb) run --incremental /dev/sda1
Starting program: mdadm --incremental /dev/sda1
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7fb7792 in strlen () from /lib/ld-musl-x86_64.so.1
(gdb) backtrace
#0 0x00007ffff7fb7792 in strlen () from /lib/ld-musl-x86_64.so.1
#1 0x00007ffff7fb75ea in strdup () from /lib/ld-musl-x86_64.so.1
#2 0x0000000000002000 in ?? ()
#3 0x00007ffff7f5f133 in ?? ()
#4 0x00007fffffffa8d8 in ?? ()
#5 0x00005555555a7514 in ?? ()
#6 0x00005555555605d0 in ?? ()
#7 0x0000555555561473 in ?? ()
#8 0x000055555557f92e in ?? ()
#9 0x000055555555dcc8 in ?? ()
#10 0x00007ffff7f83a03 in ?? () from /lib/ld-musl-x86_64.so.1
#11 0x00007ffff7f839dc in ?? () from /lib/ld-musl-x86_64.so.1
#12 0x00007fffffffec00 in ?? ()
#13 0x0000000000000000 in ?? ()
```
And with ltrace:
```
opendir("/dev/disk/by-path/") = 0x7f4227613030
readdir(0x7f4227613030) = 0x7f4227613048
readdir(0x7f4227613030) = 0x7f4227613060
readdir(0x7f4227613030) = 0x7f4227613078
strncpy(0x7ffe0ca3ce4a, "pci-0000:01:00.0-scsi-0:2:2:0-pa"..., 4078) = 0x7ffe0ca3ce4a
stat(0x7ffe0ca3ce38, 0x7ffe0ca3cda8, 3, 0) = 0
readdir(0x7f4227613030) = 0x7f42276130b0
strncpy(0x7ffe0ca3ce4a, "pci-0000:01:00.0-scsi-0:2:2:0-pa"..., 4078) = 0x7ffe0ca3ce4a
stat(0x7ffe0ca3ce38, 0x7ffe0ca3cda8, 3, 0) = 0
readdir(0x7f4227613030) = 0x7f42276130e8
strncpy(0x7ffe0ca3ce4a, "pci-0000:01:00.0-scsi-0:2:0:0-pa"..., 4078) = 0x7ffe0ca3ce4a
stat(0x7ffe0ca3ce38, 0x7ffe0ca3cda8, 3, 0) = 0
closedir(0x7f4227613030) = 0
strdup("\373\374\375\376\377" <no return ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
```
I copied `ld-musl-x86_64.so.1` from Alpine 3.12.0 and I don't have the segfault anymore (just a "Resource busy" which seems expected).
It seems that Musl have been updated from 1.1.24 to 1.2.2 so I suppose the problem is here (mdadm binary is the same between 3.12.0 and 3.13.0).
Note that I don't have a segfault if "/dev/disk/by-path/" is not populated.
Right now I don't know how to handle this more. Don't hesitate to ask me for more informations if I can help :)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12310composer failing to install packages due to a dns resolving error on Docker i...2021-01-16T11:21:22ZAlbert Casademontcomposer failing to install packages due to a dns resolving error on Docker images with Alpine 3.13With a simple Dockerfile
```
FROM alpine:3.13 AS php-build
RUN apk --no-cache add composer
RUN composer require hashids/hashids
```
`
Failed to download hashids/hashids from dist: curl error 6 while downloading https://api.github.com/r...With a simple Dockerfile
```
FROM alpine:3.13 AS php-build
RUN apk --no-cache add composer
RUN composer require hashids/hashids
```
`
Failed to download hashids/hashids from dist: curl error 6 while downloading https://api.github.com/repos/vinkla/hashids/zipball/8cab111f78e0bd9c76953b082919fc9e251761be: Could not resolve host: api.github.com
`
On Alpine 3.12 everything works fine
```
FROM alpine:3.12 AS php-build
RUN apk --no-cache add composer
RUN composer require hashids/hashids
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/12309net-snmp not working on Alpine 3.13 (amd64)2022-11-19T07:09:09ZStefano Marinellinet-snmp not working on Alpine 3.13 (amd64)Both on updated Alpine 3.12->3.13 hosts and newly created Alpine 3.13 hosts, snmpd kills itself just after being launched. dmesg reports:
`traps: snmpd[21440] general protection fault ip:7f7bbd9efc59 sp:7ffd4e6df8e0 error:0 in ld-musl-...Both on updated Alpine 3.12->3.13 hosts and newly created Alpine 3.13 hosts, snmpd kills itself just after being launched. dmesg reports:
`traps: snmpd[21440] general protection fault ip:7f7bbd9efc59 sp:7ffd4e6df8e0 error:0 in ld-musl-x86_64.so.1[7f7bbd9e1000+48000]`
Removing the trapsink on snmpd.conf, it seems to be running but dmesg reports:
`snmpd[22073]: segfault at 7f7598021110 ip 00007f759859d215 sp 00007ffed55515e0 error 6 in libnetsnmpmibs.so.40.0.0[7f759858b000+ab000]
Code: 09 f0 f3 48 0f 2a c8 f3 0f 58 c9 f3 0f 5e c1 f3 0f 58 05 22 b1 09 00 f3 0f 2c c0 c3 53 e8 53 0e ff ff 48 89 c7 48 85 c0 74 1a <48> 83 a7 70 20 00 00 df 48 c7 87 68 20 00 00 ff ff ff ff e8 c3 33`
Still, there seem to be some stability problems as after some pollings it seems to kill itself.Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12308/usr/bin/php symlink is not created when installing php8 on Alpine 3.13?2021-01-16T11:00:01ZAlbert Casademont/usr/bin/php symlink is not created when installing php8 on Alpine 3.13?Hi!
Normally a symlink from /usr/bin/php to /usr/bin/php7 was created when installing php7. Ideally the same should happen when installing php8 on Alpine 3.13. We had to manually create it in our Dockerfile.
Thanks!Hi!
Normally a symlink from /usr/bin/php to /usr/bin/php7 was created when installing php7. Ideally the same should happen when installing php8 on Alpine 3.13. We had to manually create it in our Dockerfile.
Thanks!