alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2024-03-06T10:42:58Zhttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/10119No validation on metadata fields can break packages2024-03-06T10:42:58ZKevin DaudtNo validation on metadata fields can break packagesIt's possible to provide random data via `install_if` (and potentially other metadata fields), that are fed directly to the package control data, which in turn will break the index (package file format error).
Should we add validation t...It's possible to provide random data via `install_if` (and potentially other metadata fields), that are fed directly to the package control data, which in turn will break the index (package file format error).
Should we add validation to those fields so that we know it's not garbage?
[This commit](https://gitlab.alpinelinux.org/alpine/aports/-/commit/f369e4491da4?page=3#e911b71f2354d6e19257e8f730e5328e955f4e0f_66_68) for example set `install_if` to:
```
install_if="$
# The group tag is just to easily find this APKBUILD by some scripts for automation
# group=kde-applications
```
which was fed directly into the apk .PKGINFO file:
```
install_if = $ # The group tag is just to easily find this APKBUILD by some scripts for automation # group=kde-applications pkgname=23.04.3-r1 nftables
```
and the package was successfully added to the index. But afterwards, any attempt to add new packages to the index failed with:
```
>>> kdeconnect: Updating the community/s390x repository index...
ERROR: kdeconnect-nftables-23.04.3-r1.apk: package file format error
>>> ERROR: kdeconnect: Failed to create index
```
After fixing the packages, this was fixed by removing the old package from the index with `abuild cleanoldpkg; abuild cleanpkg` and building it again.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15162testing/please-build: test failure on x86_642024-02-17T22:10:42ZKevin Daudttesting/please-build: test failure on x86_64testing/please build has a test failure on the builder:
<details><summary>error parsing build file: Unterminated string literal</summary>
<pre>
2023/08/05 10:11:54 initial parse complete
2023/08/05 10:11:54 built completion package tree...testing/please build has a test failure on the builder:
<details><summary>error parsing build file: Unterminated string literal</summary>
<pre>
2023/08/05 10:11:54 initial parse complete
2023/08/05 10:11:54 built completion package tree
2023/08/05 10:11:54 loaded builtin function information
2023/08/05 10:11:54 Handled initialize message in 25.401233ms
2023/08/05 10:11:54 Received textDocument/didOpen message
2023/08/05 10:11:54 failed to figure out rel path: Rel: can't make test/test.build relative to /home/buildozer/aports/testing/please-build/src/please-17.2.3/plz-out/tmp/tools/build_langserver/lsp/lsp_test._test/run_1/tools/build_langserver/lsp/test_data
2023/08/05 10:11:54 Handled textDocument/didOpen message in 61.683µs
10:11:54.816 DEBUG: error parsing build file: Unterminated string literal
goroutine 3477 [running]:
runtime/debug.Stack()
runtime/debug/stack.go:24 +0x65
github.com/thought-machine/please/src/parse/asp.parseFileInput.func1()
src/parse/asp/grammar_parse.go:61 +0x46
panic({0xd50ea0, 0xc004a520f0})
runtime/panic.go:884 +0x213
github.com/thought-machine/please/src/parse/asp.fail({0xc002557b4f, 0xf}, 0xc0038b32b0?, {0xddfedf?, 0x40f10a?}, {0x0?, 0x80?, 0x78?})
src/parse/asp/errors.go:43 +0x76
github.com/thought-machine/please/src/parse/asp.(*lex).fail(...)
src/parse/asp/lexer.go:388
github.com/thought-machine/please/src/parse/asp.(*lex).consumeString(0xc0038b3df0, 0x22, 0x100c0038b3410?, 0x0, 0x0, 0x0)
src/parse/asp/lexer.go:340 +0x458
github.com/thought-machine/please/src/parse/asp.(*lex).consumePossiblyTripleQuotedString(...)
src/parse/asp/lexer.go:290
github.com/thought-machine/please/src/parse/asp.(*lex).nextToken(0xc0038b3df0)
src/parse/asp/lexer.go:231 +0x2d9
github.com/thought-machine/please/src/parse/asp.(*lex).nextToken(0xc0038b3df0)
src/parse/asp/lexer.go:226 +0x936
github.com/thought-machine/please/src/parse/asp.(*lex).Next(...)
src/parse/asp/lexer.go:144
github.com/thought-machine/please/src/parse/asp.(*parser).next(0xc0038b3dd0, 0x5b)
src/parse/asp/grammar_parse.go:86 +0x67
github.com/thought-machine/please/src/parse/asp.(*parser).parseList(0xc0038b3dd0, 0x417510?, 0x5d)
src/parse/asp/grammar_parse.go:616 +0x53
github.com/thought-machine/please/src/parse/asp.(*parser).parseValueExpression(0xc0038b3dd0)
src/parse/asp/grammar_parse.go:485 +0x447
github.com/thought-machine/please/src/parse/asp.(*parser).parseUnconditionalExpressionInPlace(...)
src/parse/asp/grammar_parse.go:385
github.com/thought-machine/please/src/parse/asp.(*parser).parseExpressionInPlace(0xc0038b3dd0, 0xc0038b3c18)
src/parse/asp/grammar_parse.go:358 +0x165
github.com/thought-machine/please/src/parse/asp.(*parser).parseCall(...)
src/parse/asp/grammar_parse.go:604
github.com/thought-machine/please/src/parse/asp.(*parser).parseIdentStatement(0xc0038b3dd0)
src/parse/asp/grammar_parse.go:548 +0x908
github.com/thought-machine/please/src/parse/asp.(*parser).parseStatement(...)
src/parse/asp/grammar_parse.go:184
github.com/thought-machine/please/src/parse/asp.parseFileInput({0x7f86eaa6fff0, 0xc004709720})
src/parse/asp/grammar_parse.go:68 +0x76a
github.com/thought-machine/please/src/parse/asp.(*Parser).parseAndHandleErrors(0xc001756840?, {0xf0c6e8?, 0xc004709720})
src/parse/asp/parser.go:146 +0x45
github.com/thought-machine/please/src/parse/asp.(*Parser).ParseData(0xc004a42000?, {0xc004652f00, 0x5d, 0x60}, {0xc002557b4f, 0xf})
src/parse/asp/parser.go:141 +0x105
lsp_test_lib.(*Handler).parse(0xc004aa1590, 0xc005339c80, {0xc0051120c0?, 0xc0012aef98?})
tools/build_langserver/lsp/text.go:104 +0x94
created by lsp_test_lib.(*Handler).open
tools/build_langserver/lsp/text.go:74 +0x2e5
//tools/build_langserver/lsp:lsp_test 18 tests run in 5m1.003s; 17 passed, 1 errored
68 test targets and 798 tests run; 795 passed, 1 errored, 2 skipped.
</pre>
</details>
See: https://build.alpinelinux.org/buildlogs/build-edge-x86_64/testing/please-build/please-build-17.2.3-r0.logHoang NguyenHoang Nguyenhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15167Segmentation fault after upgrading from 3.17 to 3.18 on armv7l Docker engine2024-01-30T17:06:02ZhutdevSegmentation fault after upgrading from 3.17 to 3.18 on armv7l Docker engineI am using Docker on a QNAP NAS and running any container based on 3.18 images results in a segmentation fault. I think I boiled it down to an issue with musl.
```
$ uname -a
Linux myhost 4.2.8 #2 SMP Fri Jul 21 08:24:05 CST 2023 armv7l...I am using Docker on a QNAP NAS and running any container based on 3.18 images results in a segmentation fault. I think I boiled it down to an issue with musl.
```
$ uname -a
Linux myhost 4.2.8 #2 SMP Fri Jul 21 08:24:05 CST 2023 armv7l unknown
$ docker -v
Docker version 20.10.22-qnap7, build 57ed8b8
$ docker run -ti alpine:3.17.4 sh
/ # sed -i -e 's/v3\.17/v3\.18/g' /etc/apk/repositories
/ # apk update
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/armv7/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/armv7/APKINDEX.tar.gz
v3.18.2-575-g02de16b1332 [https://dl-cdn.alpinelinux.org/alpine/v3.18/main]
v3.18.2-584-g790e4707150 [https://dl-cdn.alpinelinux.org/alpine/v3.18/community]
OK: 19320 distinct packages available
/ # apk add --upgrade musl
(1/1) Upgrading musl (1.2.3-r5 -> 1.2.4-r1)
OK: 5 MiB in 15 packages
/ # ls
Segmentation fault
/ #
```
Any clues what might cause this issue and what I could do to fix it?3.20.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/15170Package Request: gnome-network-displays2023-08-11T22:32:34ZSaijin-NaibPackage Request: gnome-network-displaysThis tool allows for streaming of audio/video via MiraCast to compatible displays, and I think would be a great addition to the other GNOME ecosystem packages we have already.
https://gitlab.gnome.org/GNOME/gnome-network-displaysThis tool allows for streaming of audio/video via MiraCast to compatible displays, and I think would be a great addition to the other GNOME ecosystem packages we have already.
https://gitlab.gnome.org/GNOME/gnome-network-displayshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15173Enable CONFIG_DYNAMIC_DEBUG on linux-edge2023-08-07T17:08:43ZNico SchotteliusEnable CONFIG_DYNAMIC_DEBUG on linux-edgeI was wondering whether we can enable CONFIG_DYNAMIC_DEBUG on linux-edge?
linux-lts has it and its very valuable for debugging, -edge does not have it atmI was wondering whether we can enable CONFIG_DYNAMIC_DEBUG on linux-edge?
linux-lts has it and its very valuable for debugging, -edge does not have it atmMilan P. StanićMilan P. Stanićhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15176CVE Fixes Available? Follow Up to issue #151502023-08-08T15:30:41ZKamaile Carrell-JoeCVE Fixes Available? Follow Up to issue #15150As Follow Up to Issue #15150, the following CVE: Have been flagged Security Scanners as having a Vendor Dependency Vulnerability located on Various Alpine Versions Images. We have the following list and corresponding CVE# (please see tab...As Follow Up to Issue #15150, the following CVE: Have been flagged Security Scanners as having a Vendor Dependency Vulnerability located on Various Alpine Versions Images. We have the following list and corresponding CVE# (please see table below) listed for responses needed. Please let us know if we are submitting this incorrectly and or need to be posting in other areas of this UI.
```
**Alpine Version:Pkg:Release | CVE # | Alpine Linux Response**
alpine://3.12:libssl1.1:1.1.1g-r0 |CVE-2021-4160 |
alpine://3.13:git:2.30.2-r0 | CVE-2022-31012 |
alpine://3.13:git:2.30.2-r0 | CVE-2022-41953 |
alpine://3.13:sqlite-libs:3.34.1-r | CVE-2022-46908 |
alpine://3.13:zfs:2.0.1-r0 | CVE-2013-20001 |
alpine://3.15:freeradius-lib:3.0.25-r1 | CVE-2022-41861 |
alpine://3.15:freeradius-lib:3.0.25-r1 | CVE-2022-41860 |
alpine://3.15:freeradius-lib:3.0.25-r1 | CVE-2022-41859 |
alpine://3.15:libwbclient:4.15.13-r0 | CVE-2021-20251 |
alpine://3.15:libwbclient:4.15.13-r0 | CVE-2023-0614 |
alpine://3.15:libwbclient:4.15.13-r0 | CVE-2023-0225 |
alpine://3.15:libwbclient:4.15.13-r0 | CVE-2023-0922 |
alpine://3.15:samba-util-libs:4.15.13-r0 | CVE-2018-14628 |
alpine://3.16:linux-pam:1.5.2-r0 | CVE-2022-28321 |
alpine://3.16:linux-pam:1.5.2-r0 | CVE-2022-28321 |
alpine://3.16:mariadb-client:10.6.14-r0 | CVE-2022-47015 |
alpine://3.16:sudo:1.9.10-r0 | CVE-2023-28487 |
alpine://3.16:sudo:1.9.10-r0 | CVE-2023-28486 |
alpine://3.17:freetype:2.12.1-r0 | CVE-2023-2004 |
alpine://3.17:libpng:1.6.38-r0 | CVE-2022-3857 |
alpine://3.17:python3:3.10.11-r0 | CVE-2023-24329 |
alpine://3.16:python3:3.10.12-r0 | CVE-2023-24329 |
alpine://3.17:python3-dev:3.10.12-r0 | CVE-2023-24329 |
alpine://3.17:python3:3.10.11-r0 | CVE-2023-27043 |
alpine://3.17:python3:3.10.11-r0 | CVE-2023-27043 |
alpine://3.17:zstd-libs:1.5.5-r0 | CVE-2022-4899 |
alpine://3.18:zstd-libs:1.5.5-r4 | CVE-2022-4899 |
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15180pip is not getting installed through python3 command2023-08-12T17:20:06ZAkilabbas Kapasipip is not getting installed through python3 commandWe are using image tfsec/tfsec-ci from docker hub website
We have installed latest Python3 version but it is not supported on Alpine 3.15.0 which is the image as mentioned above. Then we installed Python version 3.6.9 and pip version 3.6...We are using image tfsec/tfsec-ci from docker hub website
We have installed latest Python3 version but it is not supported on Alpine 3.15.0 which is the image as mentioned above. Then we installed Python version 3.6.9 and pip version 3.6 from https://bootstrap.pypa.io/pip/
We were trying to install get-pip.py through python3 command inside container by building dockerfile or through docker run exec command. But it is not getting installed
We have even tried pip version 3.5 but that too is not working.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15181community/nut: add powerfail service to init.d to shutdown UPS2023-08-13T18:36:53ZMatúš Olekšákcommunity/nut: add powerfail service to init.d to shutdown UPSHello,
I have been setting up UPS control with nut package and I have discovered, that there is missing powerfail service for shutdown runlevel, which will turn off power supply from UPS during powerfail shutdown. I have modified Gentoo ...Hello,
I have been setting up UPS control with nut package and I have discovered, that there is missing powerfail service for shutdown runlevel, which will turn off power supply from UPS during powerfail shutdown. I have modified Gentoo init.d service according to apcupsd.powerfail.initd from main/apcupsd package. Here it is [powerfail.initd](/uploads/cfbcfa0f33b2934589573d31a3e35c95/powerfail.initd)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15187hv_fcopy_daemon crashed (Hyper-V)2023-08-11T06:37:36ZHafedh TRIMECHEhv_fcopy_daemon crashed (Hyper-V)Hello,
Please note that the service hv_fcopy_daemon crashed:
```
rc-status --crashed
hv_fcopy_daemon
```
3.18.3 / 6.1.44-0-lts
Best regards.Hello,
Please note that the service hv_fcopy_daemon crashed:
```
rc-status --crashed
hv_fcopy_daemon
```
3.18.3 / 6.1.44-0-lts
Best regards.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15190npm 8.12 changes never merged into 3.16 stable2023-09-11T22:54:46ZAndy Smithnpm 8.12 changes never merged into 3.16 stableCommit 084d5d5dd1eee6b61bb6b51c6535f8e3ee6e2ad9 was merged to master on 6th June 2022 containing an update to npm version 8.12.1
This wasn't picked over to any 3.16 branch so the version of npm available (8.10) carries CVE-2022-25881, C...Commit 084d5d5dd1eee6b61bb6b51c6535f8e3ee6e2ad9 was merged to master on 6th June 2022 containing an update to npm version 8.12.1
This wasn't picked over to any 3.16 branch so the version of npm available (8.10) carries CVE-2022-25881, CVE-2022-25883 and CVE-2022-29244 which were all fixed in the 8.11 releaseJakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/44Raspberry PI Secure Boot with Alpine2023-08-12T13:31:15ZOuziel SlamaRaspberry PI Secure Boot with AlpineHello,
For now I'm trying to boot a `boot.img` file as shown in the documentation here: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#boot_ramdisk
The RPI manages to load `boot.img` correctly but when it passes ...Hello,
For now I'm trying to boot a `boot.img` file as shown in the documentation here: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#boot_ramdisk
The RPI manages to load `boot.img` correctly but when it passes control to the `initramfs-init` script I get the following error message:
```
Mounting boot media failed.
Initramfs emergency recovery shell launched. Type `exit` to continue boot
Sh: can’t access tty: job control turned off
/#
```
To continue the boot I use the following commands:
```
/# mkdir /tmp/boot
/# mount /dev/mmcblk0p1 /tmp/boot
/# mount /tmp/boot/boot.img /media/mmcblk0p1
/# exit
```
Apart from the fact that it does not take into account the `headless.apkovl.tar.gz` file, the boot continues normally.
Is there a kernel parameter(s) today that would tell `initramfs-init` to mount an .img file?
And if not, a hack that would do it?
Thanks in advance for the help!https://gitlab.alpinelinux.org/alpine/aports/-/issues/15201Adding tree-sitter-php2023-08-14T14:46:19ZdonobanAdding tree-sitter-phpHi people, I'm just trying to build tree-sitter-php for helix and "created" this APKBUILD:
```
# Contributor: Jakub Jirutka <jakub@jirutka.cz>
# Maintainer: Jakub Jirutka <jakub@jirutka.cz>
pkgname=tree-sitter-php
pkgver=0.19.0
pkgrel=0...Hi people, I'm just trying to build tree-sitter-php for helix and "created" this APKBUILD:
```
# Contributor: Jakub Jirutka <jakub@jirutka.cz>
# Maintainer: Jakub Jirutka <jakub@jirutka.cz>
pkgname=tree-sitter-php
pkgver=0.19.0
pkgrel=0
pkgdesc="PHP grammar for tree-sitter"
url="https://github.com/tree-sitter/tree-sitter-php"
arch="all"
license="MIT"
makedepends="tree-sitter-dev"
install_if="tree-sitter-grammars"
source="https://github.com/tree-sitter/tree-sitter-php/archive/v$pkgver/tree-sitter-php-$pkgver.tar.gz"
options="!check" # no tests for shared lib
build() {
abuild-tree-sitter build
}
package() {
DESTDIR="$pkgdir" abuild-tree-sitter install
}
sha512sums="
bf82af3a4c0da96f58e93aaee2724f327c11e297bcd455998e0863aa64ab6ae85d1d212afa51b75c8e8ab998568cc71b0309ee3d1d41b632ef0283478ecc5711 tree-sitter-php-0.19.0.tar.gz
"
```
This gives me a include error for "node.h" which is on "/usr/include/node/node.h", after patching it on the source code it can't find "v8config.h" which is also on "/usr/include/node/" so I suppose that the dir should be properly added but I have no idea about how "abuild-tree-sitter " works.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15202community/element-web: fails to build on riscv642023-08-14T20:54:42ZKevin Daudtcommunity/element-web: fails to build on riscv64element-web fails to build on riscv64:
<details><summary>element-web-1.11.38-r0.log</summary>
```
$ node scripts/copy-res.js
wasm://wasm/3d6788e6:1
RuntimeError: memory access out of bounds
at wasm://wasm/3d6788e6:wasm-function[2...element-web fails to build on riscv64:
<details><summary>element-web-1.11.38-r0.log</summary>
```
$ node scripts/copy-res.js
wasm://wasm/3d6788e6:1
RuntimeError: memory access out of bounds
at wasm://wasm/3d6788e6:wasm-function[2]:0x325
at WasmHash.digest (/home/buildozer/aports/community/element-web/src/element-web-1.11.38/node_modules/loader-utils/lib/hash/wasm-hash.js:172:13)
at BatchedHash.digest (/home/buildozer/aports/community/element-web/src/element-web-1.11.38/node_modules/loader-utils/lib/hash/BatchedHash.js:60:22)
at Object.getHashDigest (/home/buildozer/aports/community/element-web/src/element-web-1.11.38/node_modules/loader-utils/lib/getHashDigest.js:127:17)
at genLangFile (/home/buildozer/aports/community/element-web/src/element-web-1.11.38/scripts/copy-res.js:177:32)
at /home/buildozer/aports/community/element-web/src/element-web-1.11.38/scripts/copy-res.js:282:22
at Array.reduce (<anonymous>)
at Object.<anonymous> (/home/buildozer/aports/community/element-web/src/element-web-1.11.38/scripts/copy-res.js:281:41)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
Node.js v18.17.0
```
</details>
See: https://build.alpinelinux.org/buildlogs//build-edge-riscv64/community/element-web/element-web-1.11.38-r0.log
The package has been [disabled on riscv64](56816d68fbc2) for now.lauren n. liberdalauren n. liberdahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15203lxcfs: enabling loadavg virtualization2023-08-15T09:51:49ZArisu Desulxcfs: enabling loadavg virtualizationlxcfs allows passing `-l, --enable-loadavg` to virtualize load avg inside containers, i.e. only display load in container. This flag is not passed to lxcfs in init script and there is no variable in conf.d/lxcfs to specify user flags. It...lxcfs allows passing `-l, --enable-loadavg` to virtualize load avg inside containers, i.e. only display load in container. This flag is not passed to lxcfs in init script and there is no variable in conf.d/lxcfs to specify user flags. It would be kinda useful if flag was either added directly or variable added to conf.d/lxcfs to specify this flag if needed, without need to edit init script directly.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15206Missing Qt6.5.2 modules, grpc and protobuf2023-08-16T18:17:23ZMitchell WinkleMissing Qt6.5.2 modules, grpc and protobufI was very happy to see Qt v 6.5.2 since it includes grpc and protobuf modules, but I do not see those in the list of packages. Thanks very much for the QtMqtt lib too!
Regards,
MitchI was very happy to see Qt v 6.5.2 since it includes grpc and protobuf modules, but I do not see those in the list of packages. Thanks very much for the QtMqtt lib too!
Regards,
Mitchhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15207package request: eduvpn-client2023-08-17T17:25:43ZJoanes Grandjeanpackage request: eduvpn-clienteduvpn-client is a python client for accessing ~1000 academic institutions around the world via VPN.
https://github.com/eduvpn/python-eduvpn-clienteduvpn-client is a python client for accessing ~1000 academic institutions around the world via VPN.
https://github.com/eduvpn/python-eduvpn-clienthttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15210e2fsprogs unstable2023-08-18T14:30:04ZArnaud Lecomtee2fsprogs unstableI'm currently facing an issue with mkfs from e2fsprogs package.
**Context** : On an alpine machine, I've got a partition on which I added an ext4 filesystem through the mkfs command.
Afterwards I put into this partition a new distributi...I'm currently facing an issue with mkfs from e2fsprogs package.
**Context** : On an alpine machine, I've got a partition on which I added an ext4 filesystem through the mkfs command.
Afterwards I put into this partition a new distribution (I tried with a rocky and ubuntu image).
When rebooting into this new distribution, it fails on file system consistency verification :
```bash
fsck: /dev/vda3 has unsupported feature(s): FEATURE_C12
```
and I'm moved to the initrd.
**Literature :** I've found some people having this issue and I found this bug report on ubuntu launchpad : https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339
**Temporary fix:** In order to fix this issue, I've currently modified `/etc/mke2fs.conf` by removing the problematic file system feature **FEATURE_C12** and it actually works.
I also find out that in previous versions of this package, those features were disabled by default : https://git.alpinelinux.org/aports/commit/main/e2fsprogs?id=fbb670c0d42a7e22ca60af8e325439c4b919bfaa
Why it is not the case with the last version (1.47.0) ?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15211telegram-desktop calls are not working2023-08-24T18:18:41ZHAH! Suntelegram-desktop calls are not workingwhen doing or receiving a call it freezes at "Exchanging encryption keys".
this bug does NOT exist in telegram-desktop@edge.
also I just saw this in my dmesg:
`telegram-deskto[43754]: segfault at 1310 ip 00007f979234069f sp 00007fff8960...when doing or receiving a call it freezes at "Exchanging encryption keys".
this bug does NOT exist in telegram-desktop@edge.
also I just saw this in my dmesg:
`telegram-deskto[43754]: segfault at 1310 ip 00007f979234069f sp 00007fff896000f8 error 4 likely on CPU 0 (core 0, socket 0)`https://gitlab.alpinelinux.org/alpine/aports/-/issues/15214community/libixion: upgrade to 0.18.12023-08-21T10:45:30ZKrassy Boykinovkboykinov@teamcentrixx.comcommunity/libixion: upgrade to 0.18.1As of today, the source of libixion is hosted by alpine. It is the version `0.17.0`. The latest version of libixion is `0.18.1`. Downloading it from their server leads to the build failing with the following cmd error:
```
>>> libixion: ...As of today, the source of libixion is hosted by alpine. It is the version `0.17.0`. The latest version of libixion is `0.18.1`. Downloading it from their server leads to the build failing with the following cmd error:
```
>>> libixion: No update needed for ./config.sub
>>> ERROR: libixion: prepare failed
```
I have attached the [APKBUILD](/uploads/b1d826b599b251d537f12ef26c2debb1/APKBUILD)
Note: liborcus also seems to be affectedhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/48Add functionality to remove misflagged packages2024-02-28T10:38:30ZKrassy Boykinovkboykinov@teamcentrixx.comAdd functionality to remove misflagged packagesSometimes the flagged page of aports-turbo (https://pkgs.alpinelinux.org/flagged) can contain bogus information, it seems useful for me to introduce some kind of removal process to aid in general validity of the said service.
There are ...Sometimes the flagged page of aports-turbo (https://pkgs.alpinelinux.org/flagged) can contain bogus information, it seems useful for me to introduce some kind of removal process to aid in general validity of the said service.
There are multiple types of wrong flags:
1. Non version number content:
![spam](/uploads/b08f250aaf96278fd15fefab7b2873dc/spam.png)
2. Wrong version number content:
![wrong](/uploads/cf9574072f24a72adf7329dbc7cbf2d3/wrong.png)
3. Dev version marked as release by Anitya (mapping error on their platform):
![anitya](/uploads/29004ab4512778f0c9ac8447f68d0850/anitya.png)
<br>
<br>
What have i thought of?
As there are multiple causes of the mismatched flag data, multiple sulutions are proposed:
* Non Solution: The admin has to remove the entries by hand from the SQL database (does not happen atm)
* Solution 1: Removing the userbased flag functionality and instead referencing to Anitya for flagging (after the Flag button click)
| pros | cons |
| ------ | ------ |
| light implementation demand | some enterprise users have time windows and possibly would not flag the package at all |
| bar for spam flaggers rises, because an account has to be created at Anitya | does not directly aid in removing existing bad entries |
* Solution 2: Adding a "report false positive" button, that notifies the maintainer of the package to confirm the false positive
| pros | cons |
| ------ | ------ |
| safegurad against bot-based deletes | if maintainer is inactive, the confirmation link will (probably) never be clicked on |
| | does not handle unmaintained packages well |
* Sulution 3: Solution_2() + notifying active maintainers, that have write permission to `/aports` repo after a timeout or directly if without maintainer
| pros | cons |
| ------ | ------ |
| safegurad against bot-based deletes | maybe harder to implement |
| confirmation links of inactive maintainers are forwardable to active ones | |
| handles unmaintained packages | |
Comments welcome!
P.S. Whether one of these solutions is approached, displaying a tooltip with a link and one to two lines of explanation towards Anitya would help imo.