alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2023-10-30T22:23:47Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15415community/vectorscan - invalid opcode libhs.so.5.4.82023-10-30T22:23:47Zpini-ghcommunity/vectorscan - invalid opcode libhs.so.5.4.8Hi,
Using the package community/rspamd on Alpine Linux v3.17 I encountered this error occurring in the Vectorscan library:
```
Oct 23 15:17:26 serveur1 kernel: traps: rspamd[910444] trap invalid opcode ip:7ff4028482a1 sp:7fff7d0a13d0 er...Hi,
Using the package community/rspamd on Alpine Linux v3.17 I encountered this error occurring in the Vectorscan library:
```
Oct 23 15:17:26 serveur1 kernel: traps: rspamd[910444] trap invalid opcode ip:7ff4028482a1 sp:7fff7d0a13d0 error:0 in libhs.so.5.4.8[7ff402847000+40a000]
```
Processor:
```
model name : Intel(R) Atom(TM) CPU N2800 @ 1.86GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat
```
Does Alpine Linux support this CPU?
Thanks in advance.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15414main/bash: /etc/profile breaks PATH settings in Docker/OCI containers2024-03-11T10:39:55ZHadmut Danischmain/bash: /etc/profile breaks PATH settings in Docker/OCI containersHi,
when using bash in a alpine based docker/OCI image, the PATH variable is overridden/broken, if set in the image meta info.
It is common that environment variables, including PATH, are set via the ENV command in Dockerfiles. Their ...Hi,
when using bash in a alpine based docker/OCI image, the PATH variable is overridden/broken, if set in the image meta info.
It is common that environment variables, including PATH, are set via the ENV command in Dockerfiles. Their values are stored in the image meta data and can be viewed with podman image inspect IMAGENAME. When the container starts, these environment variables are automatically set and passed through.
bash, however, enforces overriding the PATH variable in /etc/profile with
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
thus overriding and destroying any set environments.
This breaks, e.g., the ruby containers, where
"PATH=/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
is set in the image meta data.
Gem Binaries, which are installed in /usr/local/bundle/bin are not found then by bash.
regardshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15413Package request: codelldb2023-11-01T16:30:17ZHoang NguyenPackage request: codelldb**Project**: https://github.com/vadimcn/codelldb
**Description**: debugger program for C/C++/Rust/Zig/...
**License**: MIT
It requires a custom lldb source (https://github.com/vadimcn/llvm-project/tree/codelldb/16.x) to be able to deb...**Project**: https://github.com/vadimcn/codelldb
**Description**: debugger program for C/C++/Rust/Zig/...
**License**: MIT
It requires a custom lldb source (https://github.com/vadimcn/llvm-project/tree/codelldb/16.x) to be able to debug Rust code. I don't use Rust so I'm fine with it being built against the llvm package in AlpineLinux's repo (if doable). Their build instruction looks rather horribly complicated.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15412community/firefox-119.0-r0: cannot find llvm-objdump on riscv642023-12-07T17:15:50ZKevin Daudtcommunity/firefox-119.0-r0: cannot find llvm-objdump on riscv64`firefox` fails to build on ~"arch:riscv64" with:
```plaintext
1:59.41 checking for llvm_profdata... not found
1:59.98 checking for llvm-objdump... not found
1:59.99 DEBUG: llvm_objdump: Looking for llvm-objdump
1:59.99 ERROR: Canno...`firefox` fails to build on ~"arch:riscv64" with:
```plaintext
1:59.41 checking for llvm_profdata... not found
1:59.98 checking for llvm-objdump... not found
1:59.99 DEBUG: llvm_objdump: Looking for llvm-objdump
1:59.99 ERROR: Cannot find llvm-objdump
Config object not found by mach.
*** Fix above errors and then restart with "./mach build"
```
See:
- https://build.alpinelinux.org/buildlogs//build-edge-riscv64/community/firefox/firefox-119.0-r0.logPatrycja Rosaalpine@ptrcnull.mePatrycja Rosaalpine@ptrcnull.mehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15411community/opencv-4.8.1-r0: linking error, unknown relocation (60) against sym...2023-10-28T11:40:31ZKevin Daudtcommunity/opencv-4.8.1-r0: linking error, unknown relocation (60) against symbol on riscv64`openvcv` fails to build on ~"arch:riscv64" with:
```
ninja: job failed: : && /usr/bin/clang++ -Os -fstack-clash-protection -Wformat -Werror=format-security -D_GLIBCXX_ASSERTIONS=1 -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS=1 -D_LIB...`openvcv` fails to build on ~"arch:riscv64" with:
```
ninja: job failed: : && /usr/bin/clang++ -Os -fstack-clash-protection -Wformat -Werror=format-security -D_GLIBCXX_ASSERTIONS=1 -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS=1 -D_LIBCPP_ENABLE_HARDENED_MODE=1 -g -g1 -Wl,--as-needed,-O1,--sort-common -fuse-ld=lld CMakeFiles/cmTC_e63de.dir/testCXXCompiler.cxx.o -o cmTC_e63de && :
ld.lld: error: /usr/lib/Scrt1.o:(.debug_rnglists+0x15): unknown relocation (60) against symbol .LFE0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x16): unknown relocation (60) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x16): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_rnglists+0x15): unknown relocation (61) against symbol .LFB0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x17): unknown relocation (60) against symbol .LVL2
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x17): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x1b): unknown relocation (60) against symbol .LVL2
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x1b): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x1c): unknown relocation (60) against symbol .LVL3
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x1c): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x22): unknown relocation (60) against symbol .LVL3
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x22): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x23): unknown relocation (60) against symbol .LFE0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x23): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x34): unknown relocation (60) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x34): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x35): unknown relocation (60) against symbol .LVL2
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x35): unknown relocation (61) against symbol .LVL0
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x3a): unknown relocation (60) against symbol .LVL2
ld.lld: error: /usr/lib/Scrt1.o:(.debug_loclists+0x3a): unknown relocation (61) against symbol .LVL0
ld.lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors)
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
```
See:
- https://build.alpinelinux.org/buildlogs//build-edge-riscv64/community/opencv/opencv-4.8.1-r0.logBart RibbersBart Ribbershttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15409The `video` group mixes permissions for video output and input devices2023-11-20T10:47:42ZHugo BarreraThe `video` group mixes permissions for video output and input devicesTLDR: when a user is made a member of the `video` group in order to have access to webcam devices, that user and all their processes also have unrestricted access to raw video output device nodes.
I have [reported this upstream to `eude...TLDR: when a user is made a member of the `video` group in order to have access to webcam devices, that user and all their processes also have unrestricted access to raw video output device nodes.
I have [reported this upstream to `eudev`](https://github.com/eudev-project/eudev/issues/268) too, but I wouldn't count on this being fixed soon.
Wayland compositors use something like `seatd` or `elogind` to access video output hardware and input devices (mouse, keyboards, etc). This means that they don't need access to the hardware device itself. The recommendation from upstream (e.g.: developers of compositors and tools like `seatd`) is that users don't need to be a member of the `video` group. This prevents other user processes from having unrestricted access to the video output device.
If a user account can't access the device nodes, then neither can the processes or sandboxes that this user spawn.
Currently on Alpine, the `video` group has two purposes:
- Granting access to video output devices (e.g.: `drm`).
- Granting access to video input devices such as webcams.
If I want an account to have access to a webcam, it also immediately gets access to the hardware rendering device (and can, for example, screen-record what other users are doing, screen-spoof, etc).
## Potential solution
I think that the correct fix for this is:
- Keep using the `video` group for video output devices (this minimises breakage for existing installations).
- Use the `camera` group for webcams and other video input devices.
This requires patching several `udev` rules, both from `eudev` itself and third party rules.
This is a breaking change, and should be announced as such (it requires user intervention in most scenarios which make use of this group). I think that this specific approach is the least-breaking one, since it won't break existing Alpine installations which actually do require direct access to video hardware.
Sadly, this might spawn a wave of "my webcam stopped working" questions on IRC.
Before sending out patches, I'd like to hear what others think about this. This issue affects both Alpine and upstream, so this might need to be a coordinated effort).https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/48initramfs-init: apkovl mount relocation: let userland know where apkovl file ...2023-11-30T10:47:12Zmacmpiinitramfs-init: apkovl mount relocation: let userland know where apkovl file finally landsinitramfs may relocate `apkovl` mount, and initial [`dmesg`](https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/master/initramfs-init.in#L664) message **indicating original apkovl file path** will then be obsoleted...making post-boot ...initramfs may relocate `apkovl` mount, and initial [`dmesg`](https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/master/initramfs-init.in#L664) message **indicating original apkovl file path** will then be obsoleted...making post-boot user determination of _which apkovl file had been used_ unreliable...\
Some better solution ought to be found (`/proc/apkovl` like entry or al).
Typical exemple, booting from a USB stick on Pi, `dmesg` will initially report `apkovl` loaded from `/media/sda1`, and then it will move to `/media/usb`...\
This causes issues to programs willing to refer to (definitive) `apkovl` file location.https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/47initramfs-init: don't mount boot partition in /media by default but in conven...2023-11-28T08:02:08Zmacmpiinitramfs-init: don't mount boot partition in /media by default but in conventional locationBooting base image (or `apkovl` without specific `fstab`) have boot partition appear within unconventional `/media`-related mountpoint.\
It would be more suitable to find it under `/boot`-related mountpoint.
Side note in case of apkovl ...Booting base image (or `apkovl` without specific `fstab`) have boot partition appear within unconventional `/media`-related mountpoint.\
It would be more suitable to find it under `/boot`-related mountpoint.
Side note in case of apkovl relocation https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/48https://gitlab.alpinelinux.org/alpine/aports/-/issues/15405Request for FB_TFT in arm2023-10-26T19:02:46Zpki791Request for FB_TFT in armHi.
I would like to habe the FB_TFT option enabled with at least the ILI9341 driver. I am using this display in some hobby projects, but it seems too difficult for me to rebuild the arm image with that enabled.Hi.
I would like to habe the FB_TFT option enabled with at least the ILI9341 driver. I am using this display in some hobby projects, but it seems too difficult for me to rebuild the arm image with that enabled.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15401main/openssh: (ssh-copy-id) expr: warning: '^ERROR: ': using '^' as the first...2023-10-25T18:11:11ZHugo Barreramain/openssh: (ssh-copy-id) expr: warning: '^ERROR: ': using '^' as the first characterWhen using `ssh-copy-id`, it leaks some error in the middle about a non-portable regular expression
```console
> /usr/bin/ssh-copy-id -i destiny.whynothugo.nl.pub hugo@192.168.21.151
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be ...When using `ssh-copy-id`, it leaks some error in the middle about a non-portable regular expression
```console
> /usr/bin/ssh-copy-id -i destiny.whynothugo.nl.pub hugo@192.168.21.151
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "destiny.whynothugo.nl.pub"
The authenticity of host '192.168.21.151 (192.168.21.151)' can't be established.
ED25519 key fingerprint is SHA256:vg2LPmwqz+3wGP266EqB7i76/qaeF4bKnEnRrTNHeI0.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? fingerprint
Please type 'yes', 'no' or the fingerprint: yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
expr: warning: '^ERROR: ': using '^' as the first character
of a basic regular expression is not portable; it is ignored
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
no such identity: /home/hugo/.ssh/keys/192.168.21.151: No such file or directory
hugo@192.168.21.151's password:
```
The executable in question here is a shell script. Line 237 seems to contain the regex in question:
if expr "$NEW_IDS" : "^ERROR: " >/dev/null ; then
Not entirely sure if we want to patch this locally. It might be best to report this upstream.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15399Request to upgrade main/nginx to version 1.25.x2023-10-25T19:52:50ZFengying ZhaoRequest to upgrade main/nginx to version 1.25.xhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15393so:libsodium.so.26 (no such package) required by: php82-sodium-8.2.11-r22023-10-28T19:45:50Zcelosauroso:libsodium.so.26 (no such package) required by: php82-sodium-8.2.11-r2The latest version `php82-sodium-8.2.11-r2` doesn't build and throw a missing dependency `so:libsodium.so.26`
In my dockerfile has the following command:
```
=> ERROR [3/8] RUN apk add --update --no-cache php82-fileinfo php82-sodium ...The latest version `php82-sodium-8.2.11-r2` doesn't build and throw a missing dependency `so:libsodium.so.26`
In my dockerfile has the following command:
```
=> ERROR [3/8] RUN apk add --update --no-cache php82-fileinfo php82-sodium 4.9s
------
> [3/8] RUN apk add --update --no-cache php82-fileinfo php82-sodium:
#0 0.801 fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz
#0 2.636 fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
#0 3.254 fetch https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
#0 3.909 fetch https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
#0 4.766 ERROR: unable to select packages:
#0 4.897 so:libsodium.so.26 (no such package):
#0 4.897 required by: php82-sodium-8.2.11-r2[so:libsodium.so.26]
------
failed to solve: process "/bin/sh -c apk add --update --no-cache php82-fileinfo php82-sodium" did not complete successfully: exit code: 2
```
```
/opt # cat /etc/*release*
3.17.3
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.17.3
PRETTY_NAME="Alpine Linux v3.17"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15392ufw errors when enabling2023-10-24T03:58:47ZJustinufw errors when enabling```
justin@oneplus-enchilada ~> sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
ERROR: problem running ufw-init
Warning: Extension conntrack revision 0 not supported, missing kernel module?
W...```
justin@oneplus-enchilada ~> sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
ERROR: problem running ufw-init
Warning: Extension conntrack revision 0 not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
iptables-restore v1.8.10 (nf_tables):
line 2: RULE_APPEND failed (No such file or directory): rule in chain ufw-track-output
line 3: RULE_APPEND failed (No such file or directory): rule in chain ufw-track-output
Warning: Extension conntrack revision 0 not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
Warning: Extension icmp revision 0 not supported, missing kernel module?
Warning: Extension udp revision 0 not supported, missing kernel module?
Warning: Extension addrtype revision 0 not supported, missing kernel module?
Warning: Extension addrtype is not supported, missing kernel module?
Warning: Extension addrtype is not supported, missing kernel module?
Warning: Extension limit revision 0 not supported, missing kernel module?
iptables-restore v1.8.10 (nf_tables):
line 25: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 26: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-output
line 27: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-forward
line 30: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 31: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 34: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 35: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 36: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 37: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 40: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-forward
line 41: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-forward
line 60: RULE_APPEND failed (No such file or di
Warning: Extension udp revision 0 not supported, missing kernel module?
Warning: Extension tcp revision 0 not supported, missing kernel module?
Warning: Extension addrtype revision 0 not supported, missing kernel module?
iptables-restore v1.8.10 (nf_tables):
line 27: RULE_APPEND failed (No such file or directory): rule in chain ufw-after-input
Warning: Extension tcp revision 0 not supported, missing kernel module?
Warning: Extension udp revision 0 not supported, missing kernel module?
Warning: Extension LOG revision 0 not supported, missing kernel module?
Warning: Extension limit revision 0 not supported, missing kernel module?
Warning: Extension conntrack revision 0 not supported, missing kernel module?
iptables-restore v1.8.10 (nf_tables):
line 25: RULE_APPEND failed (No such file or directory): rule in chain ufw-after-logging-input
line 26: RULE_APPEND failed (No such file or directory): rule in chain ufw-after-logging-forward
line 27: RULE_INSERT failed (No such file or directory): rule in chain ufw-logging-deny
line 28: RULE_APPEND failed (No such file or directory): rule in chain ufw-logging-deny
line 29: RULE_APPEND failed (No such file or directory): rule in chain ufw-logging-allow
Warning: Extension conntrack is not supported, missing kernel module?
ip6tables-restore v1.8.10 (nf_tables): Couldn't load match `conntrack':No such file or directory
Error occurred at line: 2
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
Warning: Extension rt revision 0 not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
ip6tables-restore v1.8.10 (nf_tables): Couldn't load match `conntrack':No such file or directory
Error occurred at line: 29
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
Warning: Extension udp revision 0 not supported, missing kernel module?
Warning: Extension tcp revision 0 not supported, missing kernel module?
Warning: Extension tcp revision 0 not supported, missing kernel module?
Warning: Extension udp revision 0 not supported, missing kernel module?
Warning: Extension LOG revision 0 not supported, missing kernel module?
Warning: Extension limit revision 0 not supported, missing kernel module?
Warning: Extension conntrack is not supported, missing kernel module?
ip6tables-restore v1.8.10 (nf_tables): Couldn't load match `conntrack':No such file or directory
Error occurred at line: 27
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/after.rules'
Problem running '/etc/ufw/user.rules'
Problem running '/etc/ufw/before6.rules'
Problem running '/etc/ufw/user6.rules'
```https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10950`apk del --purge` does not delete "apk-new" files2023-12-01T08:44:54Zqaqland`apk del --purge` does not delete "apk-new" filesI have this package with its config in `/etc`:
```
miniflux.conf
miniflux.conf.apk-new
```
Now delete this package:
```
$ doas apk del --purge miniflux
(1/3) Purging miniflux-openrc (2.0.44-r3)
(2/3) Purging miniflux-doc (2.0.44-r3)
(...I have this package with its config in `/etc`:
```
miniflux.conf
miniflux.conf.apk-new
```
Now delete this package:
```
$ doas apk del --purge miniflux
(1/3) Purging miniflux-openrc (2.0.44-r3)
(2/3) Purging miniflux-doc (2.0.44-r3)
(3/3) Purging miniflux (2.0.44-r3)
Executing busybox-1.36.1-r4.trigger
Executing mandoc-apropos-1.14.6-r8.trigger
OK: 6501 MiB in 1077 packages
```
But still have this file left
```
miniflux.conf.apk-new
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/15389main/alpine-ipxe-1.20.1-r1: Assembler messages: Error: operand size mismatch ...2023-10-27T05:19:05ZKevin Daudtmain/alpine-ipxe-1.20.1-r1: Assembler messages: Error: operand size mismatch for `push'main/alpine-ipxe fails to build on ~"arch:x86":
```
arch/x86/image/bootsector.c: Assembler messages:
arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push'
```
See:
- https://build.alpinelinux.org/buildlogs/build-3-19-...main/alpine-ipxe fails to build on ~"arch:x86":
```
arch/x86/image/bootsector.c: Assembler messages:
arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push'
```
See:
- https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/main/alpine-ipxe/alpine-ipxe-1.20.1-r1.log3.19.0Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15388main/zsh-5.9-r2: Test ./V14system.ztst failed: bad status 0, expected 32023-10-24T06:18:21ZKevin Daudtmain/zsh-5.9-r2: Test ./V14system.ztst failed: bad status 0, expected 3zsh has a test failure:
```
./V14system.ztst: starting.
Test ./V14system.ztst failed: bad status 0, expected 3 from:
unset chars REPLY
print -n a few words | sysread -i 0 -o 9 -c chars
ret=$?
print -- $chars x${REPLY}x
return ...zsh has a test failure:
```
./V14system.ztst: starting.
Test ./V14system.ztst failed: bad status 0, expected 3 from:
unset chars REPLY
print -n a few words | sysread -i 0 -o 9 -c chars
ret=$?
print -- $chars x${REPLY}x
return ret
Was testing: sysread write error
./V14system.ztst: test failed.
```
The test is apparently flaky since it eventually passes.
See:
- https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/main/zsh/zsh-5.9-r2.log3.19.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15386packages request ibus-typing-booster and hanspell-fr2023-11-01T16:32:39ZFlorian RICHERpackages request ibus-typing-booster and hanspell-frActually, i can't download ibus-typing-booster in my postmarketos (Alpine based) to help me write with typing-booster.Actually, i can't download ibus-typing-booster in my postmarketos (Alpine based) to help me write with typing-booster.https://gitlab.alpinelinux.org/alpine/aports/-/issues/15384main/hylafaxplus: incompatible with tiff 4.62024-03-24T17:03:55ZAndy Postnikovmain/hylafaxplus: incompatible with tiff 4.6https://sourceforge.net/p/hylafax/mailman/hylafax-users/thread/98726dcd-c00a-fd7a-8f75-88da70a54b84%40howardsilvan.com/https://sourceforge.net/p/hylafax/mailman/hylafax-users/thread/98726dcd-c00a-fd7a-8f75-88da70a54b84%40howardsilvan.com/Francesco ColistaFrancesco Colistahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15383main/lua-ossl: repair check2023-10-21T23:05:13ZAndy Postnikovmain/lua-ossl: repair checkATM it fails on 3.19 builders
- https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/main/lua-ossl/lua-ossl-20220711-r1.log
- https://build.alpinelinux.org/buildlogs/build-3-19-ppc64le/main/lua-ossl/lua-ossl-20220711-r1.logATM it fails on 3.19 builders
- https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/main/lua-ossl/lua-ossl-20220711-r1.log
- https://build.alpinelinux.org/buildlogs/build-3-19-ppc64le/main/lua-ossl/lua-ossl-20220711-r1.log3.19.0Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/15381scripts/bootstrap.sh failing to compile ada2023-11-04T15:29:31ZZack Siriscripts/bootstrap.sh failing to compile adaI'm trying to create a cross compiler for aarch64 from x86_64 host (aws instance). I'm using alpine 3.18 image. I'm getting this error
```
echo timestamp > s-d-target-hooks-def-h
build/genmodes > tmp-modes.cc
/bin/sh /home/builder/apor...I'm trying to create a cross compiler for aarch64 from x86_64 host (aws instance). I'm using alpine 3.18 image. I'm getting this error
```
echo timestamp > s-d-target-hooks-def-h
build/genmodes > tmp-modes.cc
/bin/sh /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/../move-if-change tmp-modes.cc insn-modes.cc
echo timestamp > s-modes
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/spark_xrefs.adb -o ada/spark_xrefs.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
/bin/sh /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/../move-if-change tmp-options.h options.h
echo timestamp > s-options-h
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/ali.adb -o ada/ali.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/alloc.ads -o ada/alloc.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/aspects.adb -o ada/aspects.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/atree.adb -o ada/atree.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/backend_utils.adb -o ada/backend_utils.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/butil.adb -o ada/butil.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/casing.adb -o ada/casing.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/checks.adb -o ada/checks.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/comperr.adb -o ada/comperr.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
mkdir -p ada/
gcc -c -Os -Wformat -g0 -Os -Wformat -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated -Iada -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada -Iada/libgnat -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/libgnat -Iada/gcc-interface -I/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface /home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/contracts.adb -o ada/contracts.o
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
gnat1: warning: command-line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for Ada
contracts.adb:4295:63: error: run-time library configuration error
contracts.adb:4295:63: error: file s-imgint.ads had semantic errors
contracts.adb:4295:63: error: entity "System.Img_Int.Image_Integer" not available
s-valuti.ads:382:41: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:384:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:386:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:391:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:394:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:399:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:404:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:410:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:415:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:420:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:425:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:431:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:437:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:443:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:449:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:455:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:461:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:466:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:473:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:475:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:479:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:484:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:490:14: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:611:15: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:617:15: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:619:15: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:623:15: error: aspect "Ghost" must apply to an object, package, subprogram or type
s-valuti.ads:625:15: error: aspect "Ghost" must apply to an object, package, subprogram or type
compilation abandoned
make[2]: *** [/home/builder/aports/main/gcc/src/gcc-13-20231014/gcc/ada/gcc-interface/Make-lang.in:165: ada/contracts.o] Error 1
make[2]: *** Waiting for unfinished jobs....
rm gfdl.pod gcc.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod cpp.pod gcov.pod lto-dump.pod
make[2]: Leaving directory '/home/builder/aports/main/gcc/src/build-cross-final/gcc'
make[1]: *** [Makefile:4620: all-gcc] Error 2
make[1]: Leaving directory '/home/builder/aports/main/gcc/src/build-cross-final'
make: *** [Makefile:1039: all] Error 2
>>> ERROR: gcc-aarch64: build failed
>>> gcc-aarch64: Uninstalling dependencies...
(1/25) Purging .makedepends-gcc-aarch64 (20231021.163010)
(2/25) Purging binutils-aarch64 (2.41-r0)
(3/25) Purging bison (3.8.2-r1)
(4/25) Purging flex (2.6.4-r5)
(5/25) Purging m4 (1.4.19-r3)
(6/25) Purging texinfo (7.0.3-r1)
(7/25) Purging gawk (5.2.2-r0)
(8/25) Purging zip (3.0-r12)
(9/25) Purging unzip (6.0-r14)
(10/25) Purging mpfr-dev (4.2.0_p12-r0)
(11/25) Purging mpc1-dev (1.3.1-r1)
(12/25) Purging zlib-dev (1.2.13-r1)
(13/25) Purging gcc-gnat (12.2.1_git20220924-r10)
(14/25) Purging libgnat-static (12.2.1_git20220924-r10)
(15/25) Purging libgnat (12.2.1_git20220924-r10)
(16/25) Purging linux-headers (6.3-r0)
(17/25) Purging isl-dev (0.26-r1)
(18/25) Purging gmp-dev (6.2.1-r3)
(19/25) Purging libgmpxx (6.2.1-r3)
(20/25) Purging libucontext-dev (1.2-r2)
(21/25) Purging libucontext (1.2-r2)
(22/25) Purging git-perl (2.40.1-r0)
(23/25) Purging perl-git (2.40.1-r0)
(24/25) Purging perl-error (0.17029-r1)
(25/25) Purging perl (5.36.1-r2)
Executing busybox-1.36.1-r4.trigger
OK: 318 MiB in 81 packages
(1/3) Purging .hostdepends-gcc-aarch64 (20231021.163016)
(2/3) Purging musl-dev (1.2.4_git20230717-r3)
(3/3) Purging musl (1.2.4_git20230717-r3)
OK: 0 MiB in 0 packages
```