alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2023-07-24T08:06:56Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13508Fix check for some Python packages2023-07-24T08:06:56ZPatrycja Rosaalpine@ptrcnull.meFix check for some Python packagesnewapkbuild seems to add `python3 setup.py check` to new Python packages' check function - that's not actually running any tests, just checking if metadata of the package is correct (see [here](https://docs.python.org/3.10/distutils/apir...newapkbuild seems to add `python3 setup.py check` to new Python packages' check function - that's not actually running any tests, just checking if metadata of the package is correct (see [here](https://docs.python.org/3.10/distutils/apiref.html#module-distutils.command.check)), which is useful to upstream devs but not so much for distro packaging
**list of affected packages:**
main:
- [x] meson (!29489)
- [x] py3-bcrypt (!30697)
- [x] py3-cairo (!30698)
- [x] py3-certifi (1085da3c)
- [x] py3-extras (!30717)
- [x] py3-fixtures (!30721)
- [x] py3-future (!30755)
- [x] py3-lxml (!30710)
- [x] py3-monotonic (!31603)
- [x] py3-pbr (!30757)
- [x] py3-pexpect (!30756)
- [x] py3-pynacl (!30713)
- [x] py3-pytest (!30773)
- [x] py3-sphinxcontrib-websupport (3b612e0d)
- [x] py3-testtools (!30769)
- [x] py3-urllib3 (!30709)
- [x] py3-wcwidth (!30711)
- [x] scons (!30766)
- [x] speedtest-cli (!30696)
community:
- [ ] aws-cli
- [x] certbot (!30688)
- [x] cloud-init (!30874)
- [x] docker-py (!30875)
- [x] electrum (!30741)
- [ ] git-review
- [x] gvm-tools (63e49c536a7)
- [ ] mate-tweak
- [x] ospd (51a71b185540)
- [x] ospd-openvas (24ed5058fc5)
- [ ] py3-aiohttp (!36944)
- [x] py3-aiohttp-socks (!36946)
- [x] py3-aiorpcx (!36947)
- [ ] py3-aiosignal
- [x] py3-alembic
- [ ] py3-anytree (!37088)
- [ ] py3-apache-libcloud
- [x] ~~py3-argparse~~
- [ ] py3-async_generator
- [ ] py3-blist
- [ ] py3-botocore
- [ ] py3-cached-property
- [ ] py3-cheetah
- [ ] py3-construct
- [ ] py3-cx_freeze
- [ ] py3-decorator (!36970)
- [ ] py3-dialog
- [ ] py3-distutils-extra
- [ ] py3-django-oscar
- [ ] py3-django-registration
- [x] py3-dotenv (!36964)
- [ ] py3-fasteners
- [x] py3-frozenlist (!36968)
- [ ] py3-gettext (!36948)
- [x] py3-gvm (88db827bc272)
- [ ] py3-icu
- [ ] py3-josepy
- [ ] py3-jsonrpclib
- [x] py3-mechanize (!37089)
- [ ] py3-netifaces
- [ ] py3-pdfrw
- [ ] py3-prompt_toolkit
- [ ] py3-psutil
- [ ] py3-pyaes
- [ ] py3-pysocks
- [ ] py3-rpigpio
- [ ] py3-scp
- [x] py3-secretstorage (!36793)
- [x] py3-solo1 (8081e96c)
- [ ] py3-sqlalchemy-migrate
- [ ] py3-unicodecsv (!36967)
- [ ] py3-zabbix (!37098)
- [ ] scapy
- [x] terminator (!30695)
- [x] virt-manager (!30690)
- [ ] you-get
- [ ] yubikey-manager
testing:
- [ ] awslogs
- [ ] bump2version
- [ ] gaupol
- [ ] guake
- [ ] junit2html
- [ ] nyx
- [ ] openscap-daemon
- [ ] ospd-acunetix
- [ ] ospd-debsecan
- [ ] ospd-ikescan
- [ ] ospd-nmap
- [ ] ospd-paloalto
- [ ] py3-apsw
- [ ] py3-blockchain
- [ ] py3-bump2version
- [ ] py3-cchardet
- [ ] py3-fpdf
- [ ] py3-kerberos
- [ ] py3-libacl
- [ ] py3-netmiko
- [ ] py3-pam
- [ ] py3-pefile
- [ ] py3-pg_activity
- [ ] py3-pgspecial
- [ ] py3-pyautogui
- [ ] py3-pygdbmi
- [ ] py3-pyte
- [ ] py3-sphinx-theme-better
- [ ] py3-stem
- [ ] py3-terminaltables
- [ ] py3-tls_parser
- [ ] py3-ufonormalizer
- [ ] py3-xmldiff
- [ ] py3-yara
- [ ] s3cmd
- [ ] solaar
- [ ] tartube
- [ ] thefuck
- [ ] vidcutter
- [ ] volatility3https://gitlab.alpinelinux.org/alpine/aports/-/issues/13506Management agent version is not detected in Xen Orchestra2022-02-07T14:18:21ZForzaManagement agent version is not detected in Xen OrchestraHi,
I am not able to see the Management version in XCP-ng Center or in XOA using xe-guest-utilities-7.30.0-r2 on Alpine 3.14 and Alpine 3.15.
This is how it looks like from XOA:
![image](/uploads/0b7f714b6500aa390ecabcae9d23b69d/image...Hi,
I am not able to see the Management version in XCP-ng Center or in XOA using xe-guest-utilities-7.30.0-r2 on Alpine 3.14 and Alpine 3.15.
This is how it looks like from XOA:
![image](/uploads/0b7f714b6500aa390ecabcae9d23b69d/image.png)
This is how it looks like from XCP-ng Center - it fails to detect management agent:
![image](/uploads/ea0001c3833f3823e58c8f798fea79a9/image.png)
According to the developers of Xen Orchestra, there seems to be some missing strings compiled in the xe-guest-utilities: https://xcp-ng.org/forum/topic/5059/alpine-3-14-not-detected-correctly/3?_=1644241915917https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10808Progress bar flushed by script execution2022-12-21T19:37:22ZPaul SpoorenProgress bar flushed by script executionIn OpenWrt every script executes a default `post-install` script which thereby always flushes the progress bar, it's only flickering around. Would it be possible to write the package installation progress bar after printing the execution...In OpenWrt every script executes a default `post-install` script which thereby always flushes the progress bar, it's only flickering around. Would it be possible to write the package installation progress bar after printing the execution message?
```
(15/139) Installing ucode-mod-uci (0_git20220126-r1)
Executing ucode-mod-uci_0_git20220126-r1.post-install
(16/139) Installing firewall4 (0_git20220128-r1)
Executing firewall4_0_git20220128-r1.post-install
(17/139) Installing ubi-utils (2.1.4-r1)
Executing ubi-utils_2.1.4-r1.post-install
(18/139) Installing fstools (0_git20211116-r2)
Executing fstools_0_git20211116-r2.post-install
(19/139) Installing getrandom (0_git20210803-r2)
Executing getrandom_0_git20210803-r2.post-install
(20/139) Installing hostapd-common (0_git20210522-r67)
Executing hostapd-common_0_git20210522-r67.post-install
...
```v3.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/13483unsupported cpio format2022-03-10T18:46:03ZJoachim Weberunsupported cpio formatHello all,
just a fwe minutes ago I fired an "apk update; apk upgrade --available" on my small vServer followed by a reboot, as it got a new kernel. But I was a little confused about the lines:
```
...
Executing mkinitfs-3.6.0-r0.trigg...Hello all,
just a fwe minutes ago I fired an "apk update; apk upgrade --available" on my small vServer followed by a reboot, as it got a new kernel. But I was a little confused about the lines:
```
...
Executing mkinitfs-3.6.0-r0.trigger
==> initramfs: creating /boot/initramfs-virt
**cpio: unsupported cpio format, use newc or crc**
**cpio: write error: Broken pipe**
Executing syslinux-6.04_pre1-r9.trigger
/boot is device /dev/vda1
OK: 198 MiB in 200 packages
...
```
Nevertheless the "OK" encouraged me to restart the box - but it didn't come up to more than energency mode.
What happened?
Thanks for reading!
-troubleticket- (Joe Weber)https://gitlab.alpinelinux.org/alpine/aports/-/issues/13480main/eudev: intermittent error after unplugging USB drive2022-01-28T23:31:18ZMogens Jensenmain/eudev: intermittent error after unplugging USB driveOn an Alpine edge x86_64 system, I noticed the following error in dmesg output, after unplugging a USB flash drive:
`udevd[2042]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory`
The drive does not need to be mount...On an Alpine edge x86_64 system, I noticed the following error in dmesg output, after unplugging a USB flash drive:
`udevd[2042]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory`
The drive does not need to be mounted, just inserting and removing it will generate the error, but not always, maybe 6 out of 10 times.
I don't know if this is a serious problem or just a harmless message, but it's not something I have seen before.Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13479lua-busted: add lua 5.4 support2023-09-05T21:47:14ZNatanael Copalua-busted: add lua 5.4 supportWould be nice with busted working with lua 5.4.
- [x] luarocks5.4
- [x] lua5.4-cliargs
- [x] lua5.4-system
- [x] lua5.4-say
- [x] lua5.4-luassert
- [x] lua5.4-mediatorWould be nice with busted working with lua 5.4.
- [x] luarocks5.4
- [x] lua5.4-cliargs
- [x] lua5.4-system
- [x] lua5.4-say
- [x] lua5.4-luassert
- [x] lua5.4-mediatorhttps://gitlab.alpinelinux.org/alpine/infra/aports-qa-bot/-/issues/23Add security tag based on commit message2022-04-23T14:26:15ZJ0WIAdd security tag based on commit messagee.g. commit contains a CVE or "security upgrade"e.g. commit contains a CVE or "security upgrade"https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10500Add support for syslinux EFI in setup-disk2022-04-01T09:44:36ZPhilippe SchommersAdd support for syslinux EFI in setup-diskHi,
I'd really like to be able to use `setup-disk` with `syslinux` for an EFI system.
Currently, one needs to mount the EFI partition on `/boot/efi`, and only `bootx64.efi` will be installed by `grub-efi` on that partition, keeping the ...Hi,
I'd really like to be able to use `setup-disk` with `syslinux` for an EFI system.
Currently, one needs to mount the EFI partition on `/boot/efi`, and only `bootx64.efi` will be installed by `grub-efi` on that partition, keeping the kernel and stuff out of it.
What I'd like to achieve is having the EFI partition mounted on `/boot`, so that `initramfs` and `vmlinuz` end up on the EFI partition (which is required for `syslinux` as far as I know, as the root would be on LVM).
I think this goes well in line with the Alpine philosophy.
Is this something you'd be interested in / that would get merged if I opened a PR? If so, is there something I should be mindful of?
Maybe this could be done with a `syslinux-efi` package? One thing I noticed is that installing `syslinux` automatically "pollutes" `/boot` with `.m32` and `.sys` as well as `extlinux.conf` files, which are not required for an EFI setup. Is there a way around this?https://gitlab.alpinelinux.org/alpine/aports/-/issues/13466testing/fluent-bit: segfaults on 3.15 with multiple file outputs configuration2022-01-26T13:57:33Zs-kibayashitesting/fluent-bit: segfaults on 3.15 with multiple file outputs configurationI tried fluent-bit on 3.15 armhf-build.
In case multiple file outputs configuration, segfaults were occured. (Please refer to the following configuration example and gdb dump)
When I checked 'CMakeCache.txt' after package building with...I tried fluent-bit on 3.15 armhf-build.
In case multiple file outputs configuration, segfaults were occured. (Please refer to the following configuration example and gdb dump)
When I checked 'CMakeCache.txt' after package building with original APKBUILD, '-Os -fomit-frame-pointer' was applied as GCC option. (It may be CMake's default value.)
As a test, I changed GCC option to '-O2 -fomit-frame-pointer' and tried fluent-bit rebuild, the problem of segfaults was sloved. (Please refer to the following APKBUILD modification example)
GCC's binary size optimization may be doing something wrong.
Please check this issue at the next release.
configuration example (/etc/fluent-bit/fluent-bit.conf):
```
[INPUT]
name cpu
tag cpu.local
# Read interval (sec) Default: 1
interval_sec 1
[OUTPUT]
name file
match *
path /tmp
file sample0.log
[OUTPUT]
name file
match *
path /tmp
file sample1.log
[OUTPUT]
name file
match *
path /tmp
file sample2.log
```
gdb dump (3.15 armhf-build fluent-bit original package):
```
(gdb) run -v -c /etc/fluent-bit/fluent-bit.conf
Starting program: /usr/bin/fluent-bit -v -c /etc/fluent-bit/fluent-bit.conf
Fluent Bit v1.8.9
* Copyright (C) 2019-2021 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
[2022/01/20 11:45:58] [ info] Configuration:
[2022/01/20 11:45:58] [ info] flush time | 5.000000 seconds
[2022/01/20 11:45:58] [ info] grace | 5 seconds
[2022/01/20 11:45:58] [ info] daemon | 0
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] inputs:
[2022/01/20 11:45:58] [ info] cpu
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] filters:
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] outputs:
[2022/01/20 11:45:58] [ info] file.0
[2022/01/20 11:45:58] [ info] file.1
[2022/01/20 11:45:58] [ info] file.2
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] collectors:
[New LWP 2837]
[New LWP 2838]
[2022/01/20 11:45:58] [ info] [engine] started (pid=2834)
[2022/01/20 11:45:58] [debug] [engine] coroutine stack size: 24576 bytes (24.0K)
[2022/01/20 11:45:58] [debug] [storage] [cio stream] new stream registered: cpu.0
[2022/01/20 11:45:58] [ info] [storage] version=1.1.5, initializing...
[2022/01/20 11:45:58] [ info] [storage] in-memory
[2022/01/20 11:45:58] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2022/01/20 11:45:58] [ info] [cmetrics] version=0.2.2
[2022/01/20 11:45:58] [debug] [file:file.0] created event channels: read=19 write=20
[2022/01/20 11:45:58] [debug] [file:file.1] created event channels: read=21 write=22
[2022/01/20 11:45:58] [debug] [file:file.2] created event channels: read=23 write=24
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.0
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.1
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.2
[2022/01/20 11:45:58] [ info] [sp] stream processor started
[2022/01/20 11:46:03] [debug] [task] created task=0x76ecc0e0 id=0 OK
Thread 2 "flb-pipeline" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 2837]
0x0044f2e4 in flb_input_event_type_is_metric ()
(gdb) info threads
Id Target Id Frame
1 LWP 2834 "fluent-bit" 0x76fadc88 in __aeabi_read_tp ()
from /lib/ld-musl-armhf.so.1
* 2 LWP 2837 "flb-pipeline" 0x0044f2e4 in flb_input_event_type_is_metric ()
3 LWP 2838 "flb-logger" 0x76fadc8c in __aeabi_read_tp ()
from /lib/ld-musl-armhf.so.1
(gdb) backtrace
#0 0x0044f2e4 in flb_input_event_type_is_metric ()
#1 0x004aedd4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
```
APKBUILD modification example (overwriting C_FLAGS/CXX_FLAGS):
```diff
build() {
if [ "$CBUILD" != "$CHOST" ]; then
CMAKE_CROSSOPTS="-DCMAKE_SYSTEM_NAME=Linux -DCMAKE_HOST_SYSTEM_NAME=Linux"
fi
# default CORE_STACK_SIZE=((3 * PTHREAD_STACK_MIN) / 2)=3072 is invalid
# based on https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/configuration-file
# set default to 24576
cmake -B build \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_INSTALL_LIBDIR=lib \
-DCMAKE_BUILD_TYPE=None \
+ -DCMAKE_CXX_FLAGS='-O2 -fomit-frame-pointer'
+ -DCMAKE_C_FLAGS='-O2 -fomit-frame-pointer'
-DFLB_CORO_STACK_SIZE=24576 \
-DFLB_TESTS_INTERNAL=Yes \
-DFLB_TLS=Yes \
-DFLB_HTTP_SERVER=Yes \
$CMAKE_CROSSOPTS .
make -C build
}
```https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10748meet IPv62022-02-19T14:16:22ZJ0WImeet IPv6Forking from #6377:
IPv6 for `meet.alpinelinux.org`.
Hopefully _before_ AlpineConf 2022.Forking from #6377:
IPv6 for `meet.alpinelinux.org`.
Hopefully _before_ AlpineConf 2022.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10746mail IPv62022-02-19T14:16:28ZJ0WImail IPv6Forking from #6377:
IPv6 for `mail.alpinelinux.org`Forking from #6377:
IPv6 for `mail.alpinelinux.org`https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10744dev IPv62022-02-19T14:16:35ZJ0WIdev IPv6Forking from #6377:
IPv6 for `dev.alpinelinux.org`Forking from #6377:
IPv6 for `dev.alpinelinux.org`https://gitlab.alpinelinux.org/alpine/infra/alpine-netboot/-/issues/3Alpine v3.15 netboot kernel version behind main repo2022-02-27T22:09:23ZA mrAlpine v3.15 netboot kernel version behind main repoProblem is that we can't install/add kernel modules given that kernel modules from main repo has newer version.
https://dl-cdn.alpinelinux.org/alpine/v3.15/releases/x86_64/netboot/vmlinuz-lts -- 5.15.4-0-lts
https://dl-cdn.alpinelinux...Problem is that we can't install/add kernel modules given that kernel modules from main repo has newer version.
https://dl-cdn.alpinelinux.org/alpine/v3.15/releases/x86_64/netboot/vmlinuz-lts -- 5.15.4-0-lts
https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/zfs-lts-5.15.16-r0.apkhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13437CVE data in SecDB (existing vulns, but missing CVE IDs)2022-01-16T15:20:19ZhadasbloomCVE data in SecDB (existing vulns, but missing CVE IDs)[Not Urgent]
We noticed that there are a few vulnerabilities in various branches that have only an external ID, but a CVE can be potentially added to them. Posting here in case you want to add the CVEs to the data :slight_smile:
| alp...[Not Urgent]
We noticed that there are a few vulnerabilities in various branches that have only an external ID, but a CVE can be potentially added to them. Posting here in case you want to add the CVEs to the data :slight_smile:
| alpine_release | package_name | external_id | CVE_to_add |
|----------------|--------------|---------------------|----------------|
| 3.10 | squid | GHSA-572g-rvwr-6c7f | CVE-2021-33620 |
| 3.10 | xen | XSA-235 | CVE-2017-15596 |
| 3.10 | xen | XSA-238 | CVE-2017-15591 |
| 3.10 | xen | XSA-245 | CVE-2017-17046 |
| 3.10 | xen | XSA-246 | CVE-2017-17044 |
| 3.10 | xen | XSA-247 | CVE-2017-17045 |
| 3.10 | xen | XSA-248 | CVE-2017-17566 |
| 3.10 | xen | XSA-249 | CVE-2017-17563 |
| 3.10 | xen | XSA-250 | CVE-2017-17564 |
| 3.10 | xen | XSA-251 | CVE-2017-17565 |
| 3.10 | xen | XSA-253 | CVE-2018-5244 |
| 3.10 | xen | XSA-254 | CVE-2017-5753 |
| 3.10 | xen | XSA-254 | CVE-2017-5715 |
| 3.10 | xen | XSA-254 | CVE-2017-5754 |
| 3.11 | squid | GHSA-572g-rvwr-6c7f | CVE-2021-33620 |
| 3.11 | xen | XSA-235 | CVE-2017-15596 |
| 3.11 | xen | XSA-238 | CVE-2017-15591 |
| 3.11 | xen | XSA-245 | CVE-2017-17046 |
| 3.11 | xen | XSA-246 | CVE-2017-17044 |
| 3.11 | xen | XSA-247 | CVE-2017-17045 |
| 3.11 | xen | XSA-248 | CVE-2017-17566 |
| 3.11 | xen | XSA-249 | CVE-2017-17563 |
| 3.11 | xen | XSA-250 | CVE-2017-17564 |
| 3.11 | xen | XSA-251 | CVE-2017-17565 |
| 3.11 | xen | XSA-253 | CVE-2018-5244 |
| 3.11 | xen | XSA-254 | CVE-2017-5754 |
| 3.11 | xen | XSA-254 | CVE-2017-5715 |
| 3.11 | xen | XSA-254 | CVE-2017-5753 |
| 3.12 | librsvg | RUSTSEC-2020-0146 | CVE-2020-36465 |
| 3.12 | librsvg | RUSTSEC-2021-0030 | CVE-2021-28031 |
| 3.12 | librsvg | RUSTSEC-2020-0059 | CVE-2020-35905 |
| 3.12 | librsvg | RUSTSEC-2020-0060 | CVE-2020-35906 |
| 3.12 | squid | GHSA-572g-rvwr-6c7f | CVE-2021-33620 |
| 3.12 | xen | XSA-235 | CVE-2017-15596 |
| 3.12 | xen | XSA-238 | CVE-2017-15591 |
| 3.12 | xen | XSA-245 | CVE-2017-17046 |
| 3.12 | xen | XSA-246 | CVE-2017-17044 |
| 3.12 | xen | XSA-247 | CVE-2017-17045 |
| 3.12 | xen | XSA-248 | CVE-2017-17566 |
| 3.12 | xen | XSA-249 | CVE-2017-17563 |
| 3.12 | xen | XSA-250 | CVE-2017-17564 |
| 3.12 | xen | XSA-251 | CVE-2017-17565 |
| 3.12 | xen | XSA-253 | CVE-2018-5244 |
| 3.12 | xen | XSA-254 | CVE-2017-5715 |
| 3.12 | xen | XSA-254 | CVE-2017-5754 |
| 3.12 | xen | XSA-254 | CVE-2017-5753 |
| 3.13 | glib | GHSL-2021-045 | CVE-2021-27219 |
| 3.13 | librsvg | RUSTSEC-2020-0146 | CVE-2020-36465 |
| 3.13 | py3-bleach | GHSA-vv2x-vrpj-qqpq | CVE-2021-23980 |
| 3.13 | squid | GHSA-572g-rvwr-6c7f | CVE-2021-33620 |
| 3.13 | xen | XSA-235 | CVE-2017-15596 |
| 3.13 | xen | XSA-238 | CVE-2017-15591 |
| 3.13 | xen | XSA-245 | CVE-2017-17046 |
| 3.13 | xen | XSA-246 | CVE-2017-17044 |
| 3.13 | xen | XSA-247 | CVE-2017-17045 |
| 3.13 | xen | XSA-248 | CVE-2017-17566 |
| 3.13 | xen | XSA-249 | CVE-2017-17563 |
| 3.13 | xen | XSA-250 | CVE-2017-17564 |
| 3.13 | xen | XSA-251 | CVE-2017-17565 |
| 3.13 | xen | XSA-253 | CVE-2018-5244 |
| 3.13 | xen | XSA-254 | CVE-2017-5754 |
| 3.13 | xen | XSA-254 | CVE-2017-5753 |
| 3.13 | xen | XSA-254 | CVE-2017-5715 |
| 3.14 | librsvg | RUSTSEC-2020-0146 | CVE-2020-36465 |
| 3.14 | py3-bleach | GHSA-vv2x-vrpj-qqpq | CVE-2021-23980 |
| 3.14 | squid | GHSA-572g-rvwr-6c7f | CVE-2021-33620 |
| 3.14 | xen | XSA-235 | CVE-2017-15596 |
| 3.14 | xen | XSA-238 | CVE-2017-15591 |
| 3.14 | xen | XSA-245 | CVE-2017-17046 |
| 3.14 | xen | XSA-246 | CVE-2017-17044 |
| 3.14 | xen | XSA-247 | CVE-2017-17045 |
| 3.14 | xen | XSA-248 | CVE-2017-17566 |
| 3.14 | xen | XSA-249 | CVE-2017-17563 |
| 3.14 | xen | XSA-250 | CVE-2017-17564 |
| 3.14 | xen | XSA-251 | CVE-2017-17565 |
| 3.14 | xen | XSA-253 | CVE-2018-5244 |
| 3.14 | xen | XSA-254 | CVE-2017-5715 |
| 3.14 | xen | XSA-254 | CVE-2017-5753 |
| 3.14 | xen | XSA-254 | CVE-2017-5754 |
| 3.15 | librsvg | RUSTSEC-2020-0146 | CVE-2020-36465 |
| 3.15 | xen | XSA-235 | CVE-2017-15596 |
| 3.15 | xen | XSA-238 | CVE-2017-15591 |
| 3.15 | xen | XSA-245 | CVE-2017-17046 |
| 3.15 | xen | XSA-246 | CVE-2017-17044 |
| 3.15 | xen | XSA-247 | CVE-2017-17045 |
| 3.15 | xen | XSA-248 | CVE-2017-17566 |
| 3.15 | xen | XSA-249 | CVE-2017-17563 |
| 3.15 | xen | XSA-250 | CVE-2017-17564 |
| 3.15 | xen | XSA-251 | CVE-2017-17565 |
| 3.15 | xen | XSA-254 | CVE-2017-5715 |
| 3.15 | xen | XSA-254 | CVE-2017-5753 |
| 3.15 | xen | XSA-254 | CVE-2017-5754 |
| 3.4 | xen | XSA-238 | CVE-2017-15591 |
| 3.4 | zabbix | ZBX-11023 | CVE-2016-10134 |
| 3.5 | wireshark | wnpa-sec-2017-18 | CVE-2017-7747 |
| 3.5 | wireshark | wnpa-sec-2017-19 | CVE-2017-7746 |
| 3.5 | wireshark | wnpa-sec-2017-20 | CVE-2017-7745 |
| 3.5 | wireshark | wnpa-sec-2017-21 | CVE-2017-7748 |
| 3.7 | xen | XSA-235 | CVE-2017-15596 |
| 3.7 | xen | XSA-238 | CVE-2017-15591 |
| 3.7 | xen | XSA-245 | CVE-2017-17046 |
| 3.7 | xen | XSA-246 | CVE-2017-17044 |
| 3.7 | xen | XSA-247 | CVE-2017-17045 |
| 3.7 | xen | XSA-248 | CVE-2017-17566 |
| 3.7 | xen | XSA-249 | CVE-2017-17563 |
| 3.7 | xen | XSA-250 | CVE-2017-17564 |
| 3.7 | xen | XSA-251 | CVE-2017-17565 |
| 3.8 | xen | XSA-235 | CVE-2017-15596 |
| 3.8 | xen | XSA-238 | CVE-2017-15591 |
| 3.8 | xen | XSA-245 | CVE-2017-17046 |
| 3.8 | xen | XSA-246 | CVE-2017-17044 |
| 3.8 | xen | XSA-247 | CVE-2017-17045 |
| 3.8 | xen | XSA-248 | CVE-2017-17566 |
| 3.8 | xen | XSA-249 | CVE-2017-17563 |
| 3.8 | xen | XSA-250 | CVE-2017-17564 |
| 3.8 | xen | XSA-251 | CVE-2017-17565 |
| 3.8 | xen | XSA-253 | CVE-2018-5244 |
| 3.8 | xen | XSA-254 | CVE-2017-5753 |
| 3.8 | xen | XSA-254 | CVE-2017-5754 |
| 3.8 | xen | XSA-254 | CVE-2017-5715 |
| 3.8 | xen | XSA-284 | CVE-2019-17340 |
| 3.8 | xen | XSA-285 | CVE-2019-17341 |
| 3.8 | xen | XSA-286 | CVE-2020-27674 |
| 3.8 | xen | XSA-287 | CVE-2017-17342 |
| 3.8 | xen | XSA-288 | CVE-2019-17343 |
| 3.8 | xen | XSA-290 | CVE-2017-17344 |
| 3.8 | xen | XSA-291 | CVE-2019-17345 |
| 3.8 | xen | XSA-292 | CVE-2019-17346 |
| 3.8 | xen | XSA-293 | CVE-2019-17347 |
| 3.8 | xen | XSA-294 | CVE-2019-17348 |
| 3.8 | xen | XSA-295 | CVE-2019-17349 |
| 3.8 | xen | XSA-295 | CVE-2019-17350 |
| 3.8 | xen | XSA-296 | CVE-2019-18420 |
| 3.9 | xen | XSA-235 | CVE-2017-15596 |
| 3.9 | xen | XSA-238 | CVE-2017-15591 |
| 3.9 | xen | XSA-245 | CVE-2017-17046 |
| 3.9 | xen | XSA-246 | CVE-2017-17044 |
| 3.9 | xen | XSA-247 | CVE-2017-17045 |
| 3.9 | xen | XSA-248 | CVE-2017-17566 |
| 3.9 | xen | XSA-249 | CVE-2017-17563 |
| 3.9 | xen | XSA-250 | CVE-2017-17564 |
| 3.9 | xen | XSA-251 | CVE-2017-17565 |
| 3.9 | xen | XSA-253 | CVE-2018-5244 |
| 3.9 | xen | XSA-254 | CVE-2017-5754 |
| 3.9 | xen | XSA-254 | CVE-2017-5715 |
| 3.9 | xen | XSA-254 | CVE-2017-5753 |Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13436community/plasmatube (21.12): can't connect and show/search, just an eternal ...2022-01-19T15:08:28ZMike Banoncommunity/plasmatube (21.12): can't connect and show/search, just an eternal spinning wheel@Newbyte and @PureTryOut : Plasmatube is still not working for me, even after upgrading to `edge`@Newbyte and @PureTryOut : Plasmatube is still not working for me, even after upgrading to `edge`https://gitlab.alpinelinux.org/alpine/infra/compose/algitbot/-/issues/2Add a free software license for algitbot2022-02-23T19:28:50ZAnjandev MomiAdd a free software license for algitbotCarlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13401main/libttng-ust-dev: contains liblttng-ust-ctl.so with bad symbol references2022-07-26T07:29:59ZAntoine Martinmain/libttng-ust-dev: contains liblttng-ust-ctl.so with bad symbol referencesSimilar to issue #6989
The lttng-ust-ctl.so in the package version 2.13.0-r1 (tested for x86_64 on Alpine Edge as it exists 07/01/2022) contains references to symbols that don’t exist. This bug was introduced with 2.13.0, as 2.12.0 has ...Similar to issue #6989
The lttng-ust-ctl.so in the package version 2.13.0-r1 (tested for x86_64 on Alpine Edge as it exists 07/01/2022) contains references to symbols that don’t exist. This bug was introduced with 2.13.0, as 2.12.0 has no such symbol issues.
```
$ ldd /usr/lib/liblttng-ust-ctl.so
/lib/ld-musl-x86_64.so.1 (0x7f1e41a30000)
liblttng-ust-common.so.1 => /usr/lib/liblttng-ust-common.so.1 (0x7f1e419e7000)
libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7f1e41a30000)
Error relocating liblttng-ust-ctl.so: rcu_dereference_sym: symbol not found
Error relocating liblttng-ust-ctl.so: rcu_set_pointer_sym: symbol not found
Error relocating liblttng-ust-ctl.so: lttng_ust_sigbus_state: symbol not found
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/13399community/retroarch: on a small screen, clicks happen higher than they're don...2022-01-08T16:00:18ZMike Banoncommunity/retroarch: on a small screen, clicks happen higher than they're done (+ can't exit without pkill)Experienced on Pinephone _(so - a smaller screen than Desktop)_Experienced on Pinephone _(so - a smaller screen than Desktop)_https://gitlab.alpinelinux.org/alpine/aports/-/issues/13397community/koko: shows folder icons instead of image thumbnails, and UI is broken2022-01-07T21:12:58ZMike Banoncommunity/koko: shows folder icons instead of image thumbnails, and UI is brokenExperienced on Pinephone *(so - a smaller screen than Desktop)* . May be related to packaging, but just in case also reporting here: https://invent.kde.org/graphics/koko/-/issues/61Experienced on Pinephone *(so - a smaller screen than Desktop)* . May be related to packaging, but just in case also reporting here: https://invent.kde.org/graphics/koko/-/issues/61Bart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10741Live build log updates2022-01-07T18:13:39ZSören TempelLive build log updatesThis is a follow up to a short discussion I had yesterday with @kdaudt on `#alpine-infra`.
Presently, it seems that build logs are uploaded to [build.alpinelinux.org](https://build.alpinelinux.org) in a separate step after the build has...This is a follow up to a short discussion I had yesterday with @kdaudt on `#alpine-infra`.
Presently, it seems that build logs are uploaded to [build.alpinelinux.org](https://build.alpinelinux.org) in a separate step after the build has completed. As such, they are not available during the build which often makes it difficult to determine if there is a problem with the currently ongoing build (e.g. if the build is stuck which happens quite often on riscv64 for example).
IMHO it would be nice to have live buildlogs for all architectures to ease detection of hanging builds etc. Maybe this could be achieved by having the builders write logs to a NFS which could then also be mounted on the webserver powering [build.alpinelinux.org](https://build.alpinelinux.org) thereby having these files updated continuously?