aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2024-03-15T17:18:22Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15837package request: prometheus-podman-exporter2024-03-15T17:18:22ZNavid Yaghoobipackage request: prometheus-podman-exporterPrometheus exporter for podman environments exposing containers, pods, images, volumes and networks information.
https://github.com/containers/prometheus-podman-exporterPrometheus exporter for podman environments exposing containers, pods, images, volumes and networks information.
https://github.com/containers/prometheus-podman-exporterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15836Package request: flatpak-builder-tools2024-03-06T22:02:42ZAngelo Verlain ShemaPackage request: flatpak-builder-toolshttps://github.com/flatpak/flatpak-builder-tools
From the repo: "This repository contains a collection of various scripts to aid in using flatpak-builder."
It provides tools that work with `flatpak-builder`. It allows generating source...https://github.com/flatpak/flatpak-builder-tools
From the repo: "This repository contains a collection of various scripts to aid in using flatpak-builder."
It provides tools that work with `flatpak-builder`. It allows generating sources for cargo, npm, yarn and others and make building flatpak packages that depend on said build tools easier.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15832thin-provisioning-tools package is missing for s390x in Alpine 3.182024-03-21T12:25:56ZPrabhav Thalithin-provisioning-tools package is missing for s390x in Alpine 3.18thin-provisioning-tools package is not present for alpine v3.18.
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/s390x/APKINDEX.tar.gz
ERROR: unable to select packages:
thin-provisioning-tools (no such package):
required ...thin-provisioning-tools package is not present for alpine v3.18.
```
fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/s390x/APKINDEX.tar.gz
ERROR: unable to select packages:
thin-provisioning-tools (no such package):
required by: world[thin-provisioning-tools]
```
Looks like the build is disabled for s390x (Ref: [link](https://gitlab.alpinelinux.org/alpine/aports/-/commit/d62aa7ba18f3ef9360799c79c341237db2c084be)). Could you please provide more details about the same?https://gitlab.alpinelinux.org/alpine/aports/-/issues/15830Please Package A Build of River With No XWayland Support i.e. river-noxwayland2024-03-04T19:49:13ZVehementHamPlease Package A Build of River With No XWayland Support i.e. river-noxwaylandI do not need XWayland, and it is extremely bloated. Please package a build that does not requrie it (don't build with `-Dxwayland` flag). The package could be called `river-noxwayland`. A package like this exists in the AUR.I do not need XWayland, and it is extremely bloated. Please package a build that does not requrie it (don't build with `-Dxwayland` flag). The package could be called `river-noxwayland`. A package like this exists in the AUR.Anjandev MomiAnjandev Momihttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15829sub-package request: texlive-context (& possibly texmf-dist-context?)2024-03-03T23:50:03Zomniomni+alpine@hack.orgsub-package request: texlive-context (& possibly texmf-dist-context?)The last alpinelinux release where `/usr/bin/context` and `/usr/bin/mtxrun` etc is available is 3.17
- https://pkgs.alpinelinux.org/contents?file=context&path=&name=&branch=v3.17
- https://pkgs.alpinelinux.org/contents?file=mtxrun&path=...The last alpinelinux release where `/usr/bin/context` and `/usr/bin/mtxrun` etc is available is 3.17
- https://pkgs.alpinelinux.org/contents?file=context&path=&name=&branch=v3.17
- https://pkgs.alpinelinux.org/contents?file=mtxrun&path=&name=&branch=v3.17
I'm guessing that they got lost after an upgrade of `texlive` and `texmf-dist`.Marian BuschsiewekeMarian Buschsiewekehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15828nftables counters added to the default table don't save2024-03-04T06:26:24ZDave Akersnftables counters added to the default table don't saveI've recently starting experimenting with using alpine as a home router. The nftables init script has an option to save counters to a state file. However if you add a counter to the default table in /etc/nftables.nft the counter will be ...I've recently starting experimenting with using alpine as a home router. The nftables init script has an option to save counters to a state file. However if you add a counter to the default table in /etc/nftables.nft the counter will be saved but not reloaded. This is because the state file is included at the end of /etc/nftables.nft and the counters are already defined.
If the state file is included at the beginning of /etc/nftables.nft then the counters will be reloaded and adding new counters to the default table works as expected.
Another alternative would be to move the default table in /etc/nftables.nft to a file in /etc/nftables.d/... then the include order would work as expected. A benefit of moving the default table to nftables.d is to provide an example to the user as to how to use the .d directory.Francesco ColistaFrancesco Colistahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15827[RFC] Disabling "thought-provoking stories" on Firefox new tab2024-03-03T20:11:35ZPatrycja Rosaalpine@ptrcnull.me[RFC] Disabling "thought-provoking stories" on Firefox new tabFirefox 125.0 seems to introduce "exceptional content curated by the Firefox family" on the new tab:
![image](/uploads/201e5b78b8466e7fa0e0c29ba35086ea/image.png)
should Alpine disable those by default in the vendor preferences? the `a...Firefox 125.0 seems to introduce "exceptional content curated by the Firefox family" on the new tab:
![image](/uploads/201e5b78b8466e7fa0e0c29ba35086ea/image.png)
should Alpine disable those by default in the vendor preferences? the `about:config` key responsible for this ( `browser.newtabpage.activity-stream.feeds.section.topstories` ) is also exposed as a checkbox in preferences, so a user would be able to enable them as such:
![image](/uploads/ac55ba47ef3bbe4474051dc64e30052d/image.png)https://gitlab.alpinelinux.org/alpine/aports/-/issues/15819certain public URLs not resolving from Alpine image-based pods2024-03-26T14:26:51ZRamesh Madurangacertain public URLs not resolving from Alpine image-based podsWe are currently experiencing an issue with Alpine Kubernetes pods. Specifically, URLs associated with '*dap.c-path.org' (customer) are not resolving from Alpine image-based pods. As the application is hosted in an AKS cluster, I reached...We are currently experiencing an issue with Alpine Kubernetes pods. Specifically, URLs associated with '*dap.c-path.org' (customer) are not resolving from Alpine image-based pods. As the application is hosted in an AKS cluster, I reached out to Azure support, they have concluded that the problem is linked to Alpine behavior.
Interestingly, these URLs are resolving correctly from local pods (docker desktop), but they are not functioning within AKS Alpine pods. Also, in the same cluster, Ubuntu pods can handle the resolution without any problems.
Appreciate your assistance in investigating and resolving this matter. I'm happy to provide any information you might need from my side.
ex:
$ ping fair.dapstaging.c-path.org \
ping: bad address 'fair.dapstaging.c-path.org'
/ # cat /etc/os-release \
NAME="Alpine Linux" \
ID=alpine \
VERSION_ID=3.19.1 \
PRETTY_NAME="Alpine Linux v3.19"https://gitlab.alpinelinux.org/alpine/aports/-/issues/15818Missing symbols in smbd2024-02-29T07:42:07ZViktorMissing symbols in smbdHello I have a problem running smbd service on Alpine Edge
Installed samba package version `samba-4.19.4-r0`
When attempting to start service or run `ldd /usr/sbin/smbd` I get these lines about missing symbols:
```
Error relocating /us...Hello I have a problem running smbd service on Alpine Edge
Installed samba package version `samba-4.19.4-r0`
When attempting to start service or run `ldd /usr/sbin/smbd` I get these lines about missing symbols:
```
Error relocating /usr/lib/samba/libsmbd-base-samba4.so: ctdbd_unregister_ips: symbol not found
Error relocating /usr/lib/samba/libsmbd-base-samba4.so: ctdbd_passed_ips: symbol not found
Error relocating /usr/sbin/smbd: samba_copyright_string: symbol not found
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15817community/zlib-ng: Provide variant built with the compat mode as a replacemen...2024-02-26T22:43:48ZJakub Jirutkacommunity/zlib-ng: Provide variant built with the compat mode as a replacement for zlibhttps://fedoraproject.org/wiki/Changes/ZlibNGTransitionhttps://fedoraproject.org/wiki/Changes/ZlibNGTransitionhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15816Upgrade LibreOffice to 7.6.5 or 24.22024-03-01T21:20:13ZjgarciaUpgrade LibreOffice to 7.6.5 or 24.2I am interested in using the latest version of LibreOffice either 7.6.5.2 or 24.2.1.2 since the 7.6.4.1 has a few known vulnerabilities. Is it possible to update the current 7.6.4.1 to at least 7.6.5.2, or even update to all the way to 2...I am interested in using the latest version of LibreOffice either 7.6.5.2 or 24.2.1.2 since the 7.6.4.1 has a few known vulnerabilities. Is it possible to update the current 7.6.4.1 to at least 7.6.5.2, or even update to all the way to 24.2.1.2 for the edge if not possible for 3.19?
Thanks!Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15815podman: Wrong status after service failed to start but some containers did2024-03-01T21:19:21ZDawid Wróbelpodman: Wrong status after service failed to start but some containers didI have podman configured to run as a service at boot time. There are about 6 containers configured to always restart, so the service should pick them all up and start accordingly.
However, for a known reason, some containers fail to sta...I have podman configured to run as a service at boot time. There are about 6 containers configured to always restart, so the service should pick them all up and start accordingly.
However, for a known reason, some containers fail to start, which results in podman service itself failing to start, which is expected:
`Feb 26 12:21:19 myvm daemon.err /etc/init.d/podman[2631]: ERROR: podman failed to start`
The service status, however, is 'stopped', not 'crashed' like it should be:
```
myvm:~# rc-service podman status
* status: stopped
```
The rest of the containers which have not failed are running fine at this point, which makes it impossible to start the service again:
```
myvm:~# rc-service podman start
* Caching service dependencies ... [ ok ]
* Configured as rootful service
* Starting Podman API service ...
* supervise-daemon: /usr/bin/podman is already running
* failed to start Podman API service [ !! ]
* ERROR: podman failed to start
```
The fact that the service is in 'stopped' status already, makes it also impossible to properly shut down the 'zombie' containers (I mean outside of manually iterating them with `podman stop`, but who wants that). At the very least it should be `crashed` status, which would allow to actually issue an `rc-service podman stop` and a subsequent `start`.
It may also be worth considering implementing OpenRC health checks, as explained in https://github.com/OpenRC/openrc/blob/master/supervise-daemon-guide.mdMichał PolańskiMichał Polańskihttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15812git-hook or other to prevent commit messages that doesn't start with somethin...2024-02-25T22:50:12Zomniomni+alpine@hack.orggit-hook or other to prevent commit messages that doesn't start with something in the root of aports/ dirI don't mind if this would disallow commit messages like `*/*: fix thing` (not `community/*: fix thing`) if that's the price to pay to prevent me from accidentally do what I just did when I merged 0ba76300839729d91706dc82247ae765f4813a57I don't mind if this would disallow commit messages like `*/*: fix thing` (not `community/*: fix thing`) if that's the price to pay to prevent me from accidentally do what I just did when I merged 0ba76300839729d91706dc82247ae765f4813a57https://gitlab.alpinelinux.org/alpine/aports/-/issues/15811monit: service doesn't start with supervise-daemon in 3.192024-02-27T13:23:11Zhaarymonit: service doesn't start with supervise-daemon in 3.19The monit service doesn't start in the default configuration in Alpine 3.19 using supervise-daemon. As a workaround one can edit `/etc/conf.d/monit` and comment out the line `supervisor="supervise-daemon" ` which makes the rcscript start...The monit service doesn't start in the default configuration in Alpine 3.19 using supervise-daemon. As a workaround one can edit `/etc/conf.d/monit` and comment out the line `supervisor="supervise-daemon" ` which makes the rcscript start the service with start-stop-daemon instead, which works.
However, it would be desirable if the default setting worked out of the boxhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15808freenginx aport2024-03-03T06:02:56Zraspbeguyfreenginx aportHello,
freenginx (forked from nginx by its main dev one week ago, see [announcement mail](https://mailman.nginx.org/pipermail/nginx/2024-February/GPXQY27UA5SJJZ2Y6JWTRWJB2TKPTJR7.html)) made [its first release](http://freenginx.org/en/d...Hello,
freenginx (forked from nginx by its main dev one week ago, see [announcement mail](https://mailman.nginx.org/pipermail/nginx/2024-February/GPXQY27UA5SJJZ2Y6JWTRWJB2TKPTJR7.html)) made [its first release](http://freenginx.org/en/download.html). I wish we could package it in Alpine.
I feel I'm not experienced enough to maintain such a big port. If nobody wish to do it, I could try but I would need help for sure.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15804[Package request] Rye: a Hassle-Free Python Experience2024-02-19T19:42:42ZPan S[Package request] Rye: a Hassle-Free Python ExperienceWebpage: https://rye-up.com/
Github: https://github.com/mitsuhiko/rye
Rye is a comprehensive project and package management solution for Python.Webpage: https://rye-up.com/
Github: https://github.com/mitsuhiko/rye
Rye is a comprehensive project and package management solution for Python.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15800swayimg: Update the stable repo's version to 2.12024-02-18T15:16:42Z/dev/urandomswayimg: Update the stable repo's version to 2.1If that's possible, I'd like the maintainers to push version 2.1 of swayimg, as currently available in `edge`, to the stable (`v3.19`) repository. The new version includes support for more image formats, a fixed anti-aliasing mode (befor...If that's possible, I'd like the maintainers to push version 2.1 of swayimg, as currently available in `edge`, to the stable (`v3.19`) repository. The new version includes support for more image formats, a fixed anti-aliasing mode (before it just blurred the image and didn't actually do anti-aliasing) and improves controls by adding mouse, touchpad and modifier key support.Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15797syslog-ng: libcloud_auth.so missing symbols2024-02-17T19:02:04ZForzasyslog-ng: libcloud_auth.so missing symbolssyslog-ng fails to start with a error of missing symbols in `libcloud_auth.so`.
We can see the missing symbols using ldd:
```
# ldd /usr/lib/syslog-ng/libcloud_auth.so
/lib/ld-musl-x86_64.so.1 (0x7fee86cdc000)
libsyslog...syslog-ng fails to start with a error of missing symbols in `libcloud_auth.so`.
We can see the missing symbols using ldd:
```
# ldd /usr/lib/syslog-ng/libcloud_auth.so
/lib/ld-musl-x86_64.so.1 (0x7fee86cdc000)
libsyslog-ng-4.5.so.0 => /usr/lib/libsyslog-ng-4.5.so.0 (0x7fee86beb000)
libevtlog-4.5.so.0 => /usr/lib/libevtlog-4.5.so.0 (0x7fee86be5000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7fee86a99000)
libcrypto.so.3 => /lib/libcrypto.so.3 (0x7fee86600000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fee86a75000)
libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7fee86cdc000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x7fee86a6e000)
libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x7fee86559000)
libivykis.so.0 => /usr/lib/libivykis.so.0 (0x7fee86a60000)
libsecret-storage.so.0 => /usr/lib/libsecret-storage.so.0 (0x7fee86a5a000)
libssl.so.3 => /lib/libssl.so.3 (0x7fee864d3000)
libintl.so.8 => /usr/lib/libintl.so.8 (0x7fee86a48000)
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt3_V214error_categoryE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt3_V214error_categoryE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt3_V214error_categoryE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt3_V214error_categoryE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt3_V214error_categoryE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt13runtime_error4whatEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt13runtime_error4whatEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt13runtime_error4whatEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt13runtime_error4whatEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt13runtime_error4whatEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10_M_messageB5cxx11Ei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10_M_messageB5cxx11Ei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10_M_messageB5cxx11Ei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10_M_messageB5cxx11Ei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10_M_messageB5cxx11Ei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category23default_error_conditionEi: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category23default_error_conditionEi: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category23default_error_conditionEi: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category23default_error_conditionEi: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category23default_error_conditionEi: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentEiRKSt15error_condition: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentEiRKSt15error_condition: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentEiRKSt15error_condition: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentEiRKSt15error_condition: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentEiRKSt15error_condition: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentERKSt10error_codei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentERKSt10error_codei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentERKSt10error_codei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentERKSt10error_codei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNKSt3_V214error_category10equivalentERKSt10error_codei: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt12system_errorD2Ev: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_free_exception: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_begin_catch: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt6chrono3_V212system_clock3nowEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt13runtime_errorC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt14basic_ifstreamIcSt11char_traitsIcEE5closeEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _Znwm: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt14overflow_errorD1Ev: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt3_V214error_categoryD2Ev: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt20__throw_length_errorPKc: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_guard_release: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt15basic_streambufIcSt11char_traitsIcEE5sgetcEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt14basic_ifstreamIcSt11char_traitsIcEED1Ev: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt14overflow_errorC1EPKc: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_allocate_exception: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt29_Rb_tree_insert_and_rebalancebPSt18_Rb_tree_node_baseS0_RS_: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_throw: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_guard_abort: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt17__throw_bad_allocv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt18_Rb_tree_incrementPKSt18_Rb_tree_node_base: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_end_catch: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_guard_acquire: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVSt12system_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt13runtime_errorC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt13runtime_errorC1EPKc: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt13runtime_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt13runtime_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt28__throw_bad_array_new_lengthv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt3_V215system_categoryEv: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt14basic_ifstreamIcSt11char_traitsIcEEC1EPKcSt13_Ios_Openmode: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTISt14overflow_error: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZSt21__glibcxx_assert_failPKciS0_S0_: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZNSt13runtime_errorD1Ev: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __cxa_rethrow: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZdlPvm: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTINSt8ios_base7failureB5cxx11E: symbol not found
Error relocating /usr/lib/syslog-ng/libcloud_auth.so: __gxx_personality_v0: symbol not found
```
I am using plain install of Alpine 3.19.1 with syslog-ng-4.5.0-r0https://gitlab.alpinelinux.org/alpine/aports/-/issues/15796testing/sc-controller: incorrectly flagged as out-of-date2024-02-17T18:56:24ZJoshua Murphytesting/sc-controller: incorrectly flagged as out-of-dateThe problem seems to be that the [automated version monitoring](https://release-monitoring.org/project/12312/) thinks that version 0.4.10-pre
is a newer release than 0.4.8.13, which is the actual current release.
Based solely on vers...The problem seems to be that the [automated version monitoring](https://release-monitoring.org/project/12312/) thinks that version 0.4.10-pre
is a newer release than 0.4.8.13, which is the actual current release.
Based solely on version number that makes sense, however, sc-controller's versioning is a bit _interesting_ in that
the 0.4.9.x and 0.4.10.x versions are from 2022 and are incomplete attempts at porting to C++.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15794documenting community/kodi-gbm install2024-02-16T08:28:01ZBjörn Strömbergdocumenting community/kodi-gbm installso i'm currently moving my htpc from libreelec-11.0.6 to alpine-v3.19 for various reasons, <br>
like they succesfully messed up NFS usage during patching libreelec-11.0.3 -> libreelec-11.0.4, <br>
and that bug is not likely to be resolve...so i'm currently moving my htpc from libreelec-11.0.6 to alpine-v3.19 for various reasons, <br>
like they succesfully messed up NFS usage during patching libreelec-11.0.3 -> libreelec-11.0.4, <br>
and that bug is not likely to be resolved unless its gone in libreelec-12 when that now comes along.
and like usual, it seems alpine got kodi-gbm in community. which will fit the B.O.M. (bill of materials) pretty damn well for what i want.
also like usual when it comes to us here at alpine, <br>
there is not a single hit on either kodi or gbm in wiki.alpinelinux.org so unless there is documentation else where that i don't know about, <br>
i guess i should atleast make an effort to document this process.
aim is to use a nuc as htpc, and do the minimal to get kodi running over hdmi, without using x11 or wayland.
and to document this so it can be used to create a wiki page or whatever documentation platform we're really using