aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2024-03-24T23:55:28Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15881font-dejavu not properly installed2024-03-24T23:55:28Zcristian_cifont-dejavu not properly installed## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not ...## Package Information
* Package name: *font-dejavu*
* Package version: *2.37-r5*
* Alpine version: *3.20.0_alpha20231219*
* Alpine architecture: *x86*
## Summary
I was suggested to issue a report against font-dejavu because it's not properly installed on Xorg. If I run `xlsfonts` (built from [sources](https://gitlab.freedesktop.org/xorg/app/xlsfonts)) command, it doesn't list dejavu font. As a result, applications that rely on it do not find the font in the right path, for some reason. I've tried to compare package() functions in archilinux's [PKGBUILD](https://gitlab.archlinux.org/archlinux/packaging/packages/ttf-dejavu/-/blob/main/PKGBUILD) and alpine's [APKBUILD](https://git.alpinelinux.org/aports/tree/main/font-dejavu/APKBUILD).
When I remove and reinstall the package, I get:
```
alpine-test:~$ doas apk del font-dejavu
(1/1) Purging font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 314 MiB in 958 packages
alpine-test:~$
```
```
alpine-test:~$ doas apk add font-dejavu
(1/1) Installing font-dejavu (2.37-r5)
Executing fontconfig-2.15.0-r0.trigger
Executing mkfontscale-1.2.2-r5.trigger
OK: 324 MiB in 959 packages
alpine-test:~$
```
So, I've compared also [fontconfig](https://git.alpinelinux.org/aports/tree/main/fontconfig/fontconfig.trigger) and [mkfontscale](https://git.alpinelinux.org/aports/tree/main/mkfontscale/mkfontscale.trigger) triggers with the respective archlinux's hooks.
Still, I can't figure out why the path is wrong and is not listed by xlsfonts, after font-dejavu installation.
While at it, I noticed that font-dejavu's APKBUILD doesn'install the [LICENSE](https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE) file into `/usr/share/licenses`, unlike archlinux's PKGBUILD (likely that's not required by alpine)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15879testing/wine-staging - WineD3D is broken2024-03-21T10:14:14ZLassebqtesting/wine-staging - WineD3D is broken## Package Information
* Package name: wine-staging
* Package version: 9.4.1-r0
* Alpine version: 3.20.0_alpha20240315
* Alpine architecture: x86_64
## Summary
DirectX games have graphical glitches when using built-in WineD3D DirectX t...## Package Information
* Package name: wine-staging
* Package version: 9.4.1-r0
* Alpine version: 3.20.0_alpha20240315
* Alpine architecture: x86_64
## Summary
DirectX games have graphical glitches when using built-in WineD3D DirectX to OpenGL translation layer. This does not happen with DXVK installed in the prefix.
## Steps to reproduce
- Disable DXVK if installed (change library overrides for dx-related DLLs to built-in in winecfg)
- Run a DirectX game
To make sure that this isn't a bug with mesa-opengl, I decided to run wine with zink. Issue persists.
This does not happen with wine-staging 8.21 (Tested on Arch Linux). And I'm also unable to reproduce this bug on wine 9.0-r0 from community repo.Matthias Ahouansoumatthias@ahouansou.czMatthias Ahouansoumatthias@ahouansou.czhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15878Freezing on "Loading hardware drivers"2024-03-25T14:18:05ZGianmichele TrottaFreezing on "Loading hardware drivers"Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someon...Hi everyone. I have a big problem installing the latest version of Linux Alpine.
When I start the installation it freeze almost immediately while loading hardware drivers.
I'm trying to install it on an Asus Eee PC 1101HA.
I hope someone can help me. Thanks everyone in advance.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15869community/helix Grammars/syntax hightlighting not working (23.10-r2)2024-03-25T19:10:53ZRdbocommunity/helix Grammars/syntax hightlighting not working (23.10-r2)Similarly to #14303, syntax hightlighting doesn't seem to be working on `helix-23.10-r2`.
To reproduce:
- Install helix on edge `sudo apk add helix`
- Fetch grammars `hx -g fetch`
- Build grammars `hx -g build`
- Run `hx --health`
The la...Similarly to #14303, syntax hightlighting doesn't seem to be working on `helix-23.10-r2`.
To reproduce:
- Install helix on edge `sudo apk add helix`
- Fetch grammars `hx -g fetch`
- Build grammars `hx -g build`
- Run `hx --health`
The last command will show you that none of the grammars are getting picked up.
Also, using the `tree-sitter-*` packages works, but is not ideal, since there are many missing languages from there.
I manage to fix this problem by downgrading helix to `23.10-r0`, so something must have happened between these two versions that caused this.
My downgrade process that fixed the issue:
```
echo 'http://dl-cdn.alpinelinux.org/alpine/v3.19/community' > /tmp/REPOS
sudo apk del helix
sudo apk add --no-cache --repositories-file=/tmp/REPOS helix
hx -g fetch
hx -g build
```Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15788main/dnsmasq: Upgrade from 2.89-r6 to 2.90-r0 causes issues 100% CPU usage an...2024-03-27T19:29:00ZNewbytemain/dnsmasq: Upgrade from 2.89-r6 to 2.90-r0 causes issues 100% CPU usage and DNS lookup fail for some usersDownstream issue with more information and reports from users, including a workaround: https://gitlab.com/postmarketOS/pmaports/-/issues/2601
Everyone reporting issues is on aarch64.
Not sure if I should copy information from there to ...Downstream issue with more information and reports from users, including a workaround: https://gitlab.com/postmarketOS/pmaports/-/issues/2601
Everyone reporting issues is on aarch64.
Not sure if I should copy information from there to here. Let me know if you prefer that.
Relevant commit: https://gitlab.alpinelinux.org/alpine/aports/-/commit/72ab6c34cd91684f87630c5dbe1180b18360e4b3
Paging maintainer: @ncopa
And author of the commit: @omnihttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15759valgrind on armv7 doesn't work2024-03-01T20:57:33Zqaqlandvalgrind on armv7 doesn't workProblem first found when package mustach !59786 , armv7 get check failed.
Setup qemu-arm following [wiki](https://wiki.alpinelinux.org/wiki/How_to_make_a_cross_architecture_chroot) and run `valgrind uname` also get errors:
<details><su...Problem first found when package mustach !59786 , armv7 get check failed.
Setup qemu-arm following [wiki](https://wiki.alpinelinux.org/wiki/How_to_make_a_cross_architecture_chroot) and run `valgrind uname` also get errors:
<details><summary>Click to expand logs</summary>
```
lab:~/test-c# valgrind uname
==19523== Memcheck, a memory error detector
==19523== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==19523== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==19523== Command: uname
==19523==
==19523== error calling PR_SET_PTRACER, vgdb might block
disInstr(thumb): unhandled instruction: 0xDEFF 0x6803
disInstr(thumb): unhandled instruction: 0xDEFF 0xF8D6
disInstr(thumb): unhandled instruction: 0xDEFF 0x2502
disInstr(thumb): unhandled instruction: 0xDEFF 0x4584
disInstr(thumb): unhandled instruction: 0xDEFF 0x682B
disInstr(thumb): unhandled instruction: 0xDEFF 0x4A83
disInstr(thumb): unhandled instruction: 0xDEFF 0xF850
==19523== Invalid write of size 4
==19523== at 0x48956F4: strcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f8007ac is on thread 1's stack
==19523== 56 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x4884466: ??? (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x488B4C2: ??? (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115AFE: ??? (in /bin/busybox)
==19523== Address 0x3f800c80 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
disInstr(thumb): unhandled instruction: 0xDEFF 0xF850
disInstr(thumb): unhandled instruction: 0xDEFF 0x1B1F
disInstr(thumb): unhandled instruction: 0xDEFF 0x5D73
disInstr(thumb): unhandled instruction: 0xDEFF 0x2602
==19523== Invalid write of size 4
==19523== at 0x1160E2: ??? (in /bin/busybox)
==19523== Address 0x3f800d40 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115CA2: ??? (in /bin/busybox)
==19523== Address 0x3f800d38 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x18D644: ??? (in /bin/busybox)
==19523== Address 0x3f800d38 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115E0C: ??? (in /bin/busybox)
==19523== Address 0x3f800d18 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115B3C: ??? (in /bin/busybox)
==19523== Address 0x3f800d00 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115D5E: ??? (in /bin/busybox)
==19523== Address 0x3f800d20 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115D12: ??? (in /bin/busybox)
==19523== Address 0x3f800d18 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x173A56: ??? (in /bin/busybox)
==19523== Address 0x3f800ae4 is on thread 1's stack
==19523== 560 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x182E78: ??? (in /bin/busybox)
==19523== Address 0x3f800ac0 is on thread 1's stack
==19523== 24 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x182984: ??? (in /bin/busybox)
==19523== Address 0x3f80063c is on thread 1's stack
==19523== 1144 bytes below stack pointer
==19523==
Linux
==19523== Invalid write of size 4
==19523== at 0x1931FE: ??? (in /bin/busybox)
==19523== Address 0x3f800ae8 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x1822C6: ??? (in /bin/busybox)
==19523== Address 0x3f800ae0 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x1165B2: ??? (in /bin/busybox)
==19523== Address 0x3f800ad8 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x115A9A: ??? (in /bin/busybox)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x488B45E: ??? (in /usr/libexec/valgrind/vgpreload_memcheck-arm-linux.so)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x4884402: ??? (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800a10 is on thread 1's stack
==19523== 8 bytes below stack pointer
==19523==
==19523== Invalid write of size 4
==19523== at 0x48844A8: _vgnU_freeres (in /usr/libexec/valgrind/vgpreload_core-arm-linux.so)
==19523== Address 0x3f800a9c is on thread 1's stack
==19523== 48 bytes below stack pointer
==19523==
==19523==
==19523== HEAP SUMMARY:
==19523== in use at exit: 0 bytes in 0 blocks
==19523== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==19523==
==19523== All heap blocks were freed -- no leaks are possible
==19523==
==19523== For lists of detected and suppressed errors, rerun with: -s
==19523== ERROR SUMMARY: 25 errors from 21 contexts (suppressed: 0 from 0)
```
</details>Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15538Upgrade from 3.18.y to 3.19-rc2 fails2024-03-27T19:28:55ZHenrik RiomarUpgrade from 3.18.y to 3.19-rc2 failsVM upgraded like this
```
# sed -i 's/3.18/3.19/' /etc/apk/repositories
# apk update
# apk upgrade -a
```
Log
```
Executing busybox-1.36.1-r15.trigger
Executing ca-certificates-20230506-r0.trigger
Executing kmod-31-r0.trigger
Executin...VM upgraded like this
```
# sed -i 's/3.18/3.19/' /etc/apk/repositories
# apk update
# apk upgrade -a
```
Log
```
Executing busybox-1.36.1-r15.trigger
Executing ca-certificates-20230506-r0.trigger
Executing kmod-31-r0.trigger
Executing mkinitfs-3.9.0_rc2-r0.trigger
lib/apk/exec/mkinitfs-3.9.0_rc2-r0.trigger: line 33: can't create /lib/modules/6.1.64-0-virt/initramfs-suffix: nonexistent directory
/lib/modules/6.1.64-0-virt does not exist or is not a directory
mkinitfs failed!
your system may not be bootable
ERROR: mkinitfs-3.9.0_rc2-r0.trigger: script exited with error 1
Executing syslinux-6.04_pre1-r15.trigger
/boot is device /dev/vda1
```
```
# ls -l /boot/initramfs-virt
-rw------- 1 root root 7698801 Dec 2 19:18 /boot/initramfs-virt
```
```
# ls -l /lib/modules
total 4
drwxr-xr-x 3 root root 4096 Dec 4 18:57 6.6.4-0-virt
```
```
# mkinitfs 6.6.4-0-virt
==> initramfs: creating /boot/initramfs-virt for 6.6.4-0-virt
# ls -l /boot/initramfs-virt
-rw------- 1 root root 7979735 Dec 4 18:59 /boot/initramfs-virt
```3.19.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15447monitoring-plugins: missing --with-*-command build options?2024-03-27T19:28:48ZLuca Weissmonitoring-plugins: missing --with-*-command build options?Hi, when using e.g. icinga mailq check, so `/usr/lib/monitoring-plugins/check_mailq` it expects to have e.g. `PATH_TO_MAILQ` or `PATH_TO_SUDO` defined in `utils.pm`.
Looking in there we see a bunch of empty variables
```
## updated by a...Hi, when using e.g. icinga mailq check, so `/usr/lib/monitoring-plugins/check_mailq` it expects to have e.g. `PATH_TO_MAILQ` or `PATH_TO_SUDO` defined in `utils.pm`.
Looking in there we see a bunch of empty variables
```
## updated by autoconf
$PATH_TO_SUDO = "";
$PATH_TO_RPCINFO = "" ;
$PATH_TO_LMSTAT = "" ;
$PATH_TO_SMBCLIENT = "" ;
$PATH_TO_MAILQ = "";
$PATH_TO_QMAIL_QSTAT = "";
```
Looking into some old Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905318 it looks the APKBUILD needs to set e.g. `--with-sudo-command="/usr/bin/sudo"` and `--with-mailq-command="/usr/bin/mailq"`
See also Debian list of build time options: https://salsa.debian.org/nagios-team/monitoring-plugins/-/blob/master/debian/rules#L83
edit: seems they are determined at build time from the binary if it's available. See also Arch Linux PKGBUILD (also check makedepends) https://gitlab.archlinux.org/archlinux/packaging/packages/monitoring-plugins/-/blob/main/PKGBUILD?ref_type=heads#L31 and utils.pm from there:
```
## updated by autoconf
$PATH_TO_SUDO = "/usr/bin/sudo";
$PATH_TO_RPCINFO = "/usr/bin/rpcinfo" ;
$PATH_TO_LMSTAT = "" ;
$PATH_TO_SMBCLIENT = "/usr/bin/smbclient" ;
$PATH_TO_MAILQ = "/usr/bin/mailq";
$PATH_TO_QMAIL_QSTAT = "";
$PATH_TO_SNMPGET = "/usr/bin/snmpget";
```Francesco ColistaFrancesco Colistahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14869rdiff-backup in 3.18-rc2 not backwards compatible with the one in 3.17 and older2023-05-05T07:25:42ZHenrik Riomarrdiff-backup in 3.18-rc2 not backwards compatible with the one in 3.17 and olderNot possible to backup a Alpine v3.18-rc2 system from a system running an earlier rdiff-backup version in the 2.x series (i.e. v3.17 Alpine)
Upstream bug report: https://github.com/rdiff-backup/rdiff-backup/issues/872Not possible to backup a Alpine v3.18-rc2 system from a system running an earlier rdiff-backup version in the 2.x series (i.e. v3.17 Alpine)
Upstream bug report: https://github.com/rdiff-backup/rdiff-backup/issues/8723.18.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/14444geary segfaulting with phosh on edge and 3.172022-12-13T07:55:19ZOliver Smithgeary segfaulting with phosh on edge and 3.17@craftyguy found that geary segfaults in alpine 3.17. I reproduced it on 3.17 and edge.
CC: @team/gnome@craftyguy found that geary segfaults in alpine 3.17. I reproduced it on 3.17 and edge.
CC: @team/gnomehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/14442[gnome-menus, community package] no usr/lib/girepository-1.0/GMenu-3.0.typelib2022-12-11T15:32:02ZDrSheppard[gnome-menus, community package] no usr/lib/girepository-1.0/GMenu-3.0.typelibNo gmenu, which is required for extensions such as arcmenu or gnome-shell-apps-menu
Example https://pkgs.org/search/?q=GMenu-3.0.typelibNo gmenu, which is required for extensions such as arcmenu or gnome-shell-apps-menu
Example https://pkgs.org/search/?q=GMenu-3.0.typelibhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13973alpine-extended-3.16.0-x86_64.iso lacks linux-firmware-none2022-07-08T05:49:04ZHenrik Riomaralpine-extended-3.16.0-x86_64.iso lacks linux-firmware-noneInstalling alpine 3.16 with the extended iso fails without networking
```
# setup-disk -m sys /mnt
Installing system on /dev/xvda1:
extlinux: Not a directory: /mnt/boot
ERROR: unable to select packages:
linux-firmware-none (no such pa...Installing alpine 3.16 with the extended iso fails without networking
```
# setup-disk -m sys /mnt
Installing system on /dev/xvda1:
extlinux: Not a directory: /mnt/boot
ERROR: unable to select packages:
linux-firmware-none (no such package):
required by: world[linux-firmware-none]
```
```
# find /media/cdrom -name linux-firmware-none\*
#
```
There are other firmware apk's on the extended iso but `linux-firmware-none` is missing
Tested with: `alpine-extended-3.16.0-x86_64.iso`3.16.1Henrik RiomarHenrik Riomarhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13953gajim needs py3-pillow as a runtime dependency2022-06-23T21:16:15Z/dev/urandomgajim needs py3-pillow as a runtime dependencyDistro version: v3.16 (no edge repos used)
When trying to install `gajim`, it at first reported the lack of the `PIL` module. Turns out, `py3-pillow` needs to be installed for the program to properly run, even though this dependency is ...Distro version: v3.16 (no edge repos used)
When trying to install `gajim`, it at first reported the lack of the `PIL` module. Turns out, `py3-pillow` needs to be installed for the program to properly run, even though this dependency is not specified in the package.Peter ShkenevPeter Shkenevhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13946logrotate fix incomplete2022-06-21T08:22:11ZHenrik Riomarlogrotate fix incompleteThis fix: https://git.alpinelinux.org/aports/commit/?id=ec39fd2b2f64fde0319c4b127749e7d84c3027aa
is incomplete, in the patch there is a spec file change:
```diff
+-%attr(0644, root, root) %verify(not size md5 mtime) %config(noreplace) %...This fix: https://git.alpinelinux.org/aports/commit/?id=ec39fd2b2f64fde0319c4b127749e7d84c3027aa
is incomplete, in the patch there is a spec file change:
```diff
+-%attr(0644, root, root) %verify(not size md5 mtime) %config(noreplace) %{_localstatedir}/lib/logrotate.status
++%ghost %attr(0640, root, root) %verify(not size md5 mtime) %{_localstatedir}/lib/logrotate.status
```
In Alpine this must be handled with a post-install script or something like that.
Result of this missing is this error from logrotate
```
error: state file /var/lib/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition...
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/13944main/kbd: binary keymaps empty since upgrade to 2.5.12022-06-20T06:58:14ZSören Tempelmain/kbd: binary keymaps empty since upgrade to 2.5.1Since 4471a172c590cff840412ef8c04649ef084a138c many of the binary keymaps provided by the `kbd-bkeymaps` subpackage are simply empty.
For example:
```
$ zcat /usr/share/keymaps/xkb/de-e1.map.gz | wc -c
0
```
Some also seem to contain ...Since 4471a172c590cff840412ef8c04649ef084a138c many of the binary keymaps provided by the `kbd-bkeymaps` subpackage are simply empty.
For example:
```
$ zcat /usr/share/keymaps/xkb/de-e1.map.gz | wc -c
0
```
Some also seem to contain uncomplete/garbage data, for example:
```
$ zcat /usr/share/bkeymaps/ua/ua-homophonic.bmap.gz | hexdump -C
00000000 62 6b 65 79 6d 61 70 00 00 00 00 00 00 00 00 00 |bkeymap.........|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000100 00 00 00 00 00 00 00 |.......|
```
This causes BusyBox loadkmap to not set the keymap correctly.https://gitlab.alpinelinux.org/alpine/aports/-/issues/13859[3.16] bareos upgrade broken2022-05-26T12:03:23ZSimon Fsimon-alpine@fraho.eu[3.16] bareos upgrade broken```
(42/227) Upgrading bareos (20.0.3-r1 -> 21.1.3-r0)
Executing bareos-21.1.3-r0.pre-upgrade
var/cache/misc/bareos-21.1.3-r0.pre-upgrade: local: line 2: not in a function
ERROR: bareos-21.1.3-r0.pre-upgrade: script exited with error 2
`...```
(42/227) Upgrading bareos (20.0.3-r1 -> 21.1.3-r0)
Executing bareos-21.1.3-r0.pre-upgrade
var/cache/misc/bareos-21.1.3-r0.pre-upgrade: local: line 2: not in a function
ERROR: bareos-21.1.3-r0.pre-upgrade: script exited with error 2
```
https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/bareos/bareos.pre-upgrade#L2
`local` is only allowed inside a function and should be removed on this line.Francesco ColistaFrancesco Colistahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13814Wireshark 3.6.5 segfaults on startup2023-06-17T21:47:46ZSören TempelWireshark 3.6.5 segfaults on startupWireshark currently segfaults on startup:
```
$ gdb --args wireshark
(gdb) run
Starting program: /usr/bin/wireshark
[New LWP 10362]
** (wireshark:10356) 13:13:14.132856 [GUI WARNING] -- QStandardPaths: XDG_RUNTIME_DIR not set, defaulti...Wireshark currently segfaults on startup:
```
$ gdb --args wireshark
(gdb) run
Starting program: /usr/bin/wireshark
[New LWP 10362]
** (wireshark:10356) 13:13:14.132856 [GUI WARNING] -- QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-soeren'
[New LWP 10363]
[New LWP 10364]
** (wireshark:10356) 13:13:14.137941 [GUI WARNING] -- codecForName: ucnv_open failed ISO-8859-2 U_FILE_ACCESS_ERROR
(gdb) bt
Thread 1 "wireshark" received signal SIGSEGV, Segmentation fault.
0x00005555557b1959 in MainWindow::findTextCodecs (this=0x7fffecdfd390) at /home/soeren/src/aports/community/wireshark/src/wireshark-3.6.5/ui/qt/main_window.cpp:2029
2029 QString key = codec->name().toUpper();
(gdb) bt
#0 0x00005555557b1959 in MainWindow::findTextCodecs (this=0x7fffecdfd390) at /home/soeren/src/aports/community/wireshark/src/wireshark-3.6.5/ui/qt/main_window.cpp:2029
#1 0x00005555557b4ce3 in MainWindow::MainWindow (this=this@entry=0x7fffecdfd390, parent=parent@entry=0x0) at /home/soeren/src/aports/community/wireshark/src/wireshark-3.6.5/ui/qt/main_window.cpp:362
#2 0x000055555564f0af in main (argc=<optimized out>, qt_argv=0x7fffffffe748) at /home/soeren/src/aports/community/wireshark/src/wireshark-3.6.5/ui/qt/main.cpp:725
```3.16.0Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13747[3.15] python symlink problem2022-04-25T16:04:45ZHenrik Riomar[3.15] python symlink problemThe python symlink does not work as expected in new ~"v3.15" installations. Old installations of ~"v3.15" that has just been upgraded to the current status is fine.
Upgraded
```
$ ls -l /usr/bin/*python*
lrwxrwxrwx 1 root root ...The python symlink does not work as expected in new ~"v3.15" installations. Old installations of ~"v3.15" that has just been upgraded to the current status is fine.
Upgraded
```
$ ls -l /usr/bin/*python*
lrwxrwxrwx 1 root root 9 Jan 2 13:00 /usr/bin/python3 -> python3.9
-rwxr-xr-x 1 root root 13976 Nov 24 22:15 /usr/bin/python3.9
```
But if installing python3 today, this is the result
```
$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 7 Apr 20 13:56 /usr/bin/python -> python3
-rwxr-xr-x 1 root root 13976 Nov 24 22:15 /usr/bin/python3.9
$ python
/bin/ash: python: not found
$ python3
/bin/ash: python3: not found
$ apk policy python3
python3 policy:
3.9.7-r4:
lib/apk/db/installed
http://nl.alpinelinux.org/alpine/v3.15/main
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/13697evince 42.0 is built without pdf support2022-04-15T02:28:43ZSören Tempelevince 42.0 is built without pdf supportSince 6eb23885857e00d97c53dfbd3a81d00fc3469ee9 evince is no longer able to open PDFs since it is built without PDF support (i.e. you can't open PDFs with it) due to a library version mismatch. From [the buildlog](https://build.alpinelinu...Since 6eb23885857e00d97c53dfbd3a81d00fc3469ee9 evince is no longer able to open PDFs since it is built without PDF support (i.e. you can't open PDFs with it) due to a library version mismatch. From [the buildlog](https://build.alpinelinux.org/buildlogs/build-edge-x86_64/community/evince/evince-42.0-r0.log):
```
meson.build:416: WARNING: PDF support is disabled since poppler-glib version >= 22.02.0 or libxml-2.0 version >= 2.5.0 not found
```
I think we either need to upgrade poppler-glib (which will require rebuilds) or downgrade evince again.3.16.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/13694luac 5.4.4 on edge segfaults/sigills with more than one file2022-04-14T23:52:38ZGhost Userluac 5.4.4 on edge segfaults/sigills with more than one filereproduction:
```
/bin/cat feedparser/dateparser.lua
return 2
/bin/cat feedparser/url.lua
return 1
luac5.4 -o test.lua feedparser/url.lua feedparser/dateparser.lua
fish: Job 1, 'luac5.4 -o test.lua feedparser/…' terminated by signal ...reproduction:
```
/bin/cat feedparser/dateparser.lua
return 2
/bin/cat feedparser/url.lua
return 1
luac5.4 -o test.lua feedparser/url.lua feedparser/dateparser.lua
fish: Job 1, 'luac5.4 -o test.lua feedparser/…' terminated by signal SIGSEGV (Address boundary error)
luac5.4 -o test.lua feedparser/url.lua
luac5.4 -o test.lua feedparser/dateparser.lua
```
this works fine on 5.4.33.16.0Sören TempelSören Tempel