Adélie Linux issueshttps://git.adelielinux.org/groups/adelie/-/issues2022-01-27T16:16:18Zhttps://git.adelielinux.org/adelie/docs/-/issues/320Admin Handbook - Configuration - Setup Keyboard2022-01-27T16:16:18ZBjörn StrömbergAdmin Handbook - Configuration - Setup Keyboardthe admin handbook pointed me to setting XKBLAYOUT in /etc/default/keyboard.
which does not work, after some lurking in the issue tracker i found adelie/horizon#323
horizon sets the keyboard layout in /etc/conf.d/keymaps
pretty much e...the admin handbook pointed me to setting XKBLAYOUT in /etc/default/keyboard.
which does not work, after some lurking in the issue tracker i found adelie/horizon#323
horizon sets the keyboard layout in /etc/conf.d/keymaps
pretty much everything is configured via /etc/conf.d on a raw console install it seems so far from the config files, docs should reference this cleanly.https://git.adelielinux.org/adelie/docs/-/issues/319UEFI and Adelie / Alpine2022-05-17T17:03:29ZBjörn StrömbergUEFI and Adelie / Alpineso after a lot of trouble with the 1.0-RC2 image, just to get an installed system i had to revert back to ArchLinux style manual install..
anyway to make a long story short, there [Quick-Start-Guide Bootloader](https://git.adelielinux.o...so after a lot of trouble with the 1.0-RC2 image, just to get an installed system i had to revert back to ArchLinux style manual install..
anyway to make a long story short, there [Quick-Start-Guide Bootloader](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#bootloader-non-macintosh) is no Bootloader entry for UEFI Bootloading.
so we need to add a few things to this page..<br>
Add:<br>
**Before Mounts we need to install some stuff on the temporary-live-system**
- apk add efibootmgr grub-efi
- modprobe efivarfs (should been loaded by apk install but just in case..)
- run efibootmgr to check if it can list the EFI Bootlist.. (says 'UEFI variables are not supported on this machine.' if anything is wrong.. or list the info if all is good.)
[Modify Mounts](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#mounts)<br>
**Before Chroot into new install, we do the regular stuff, mount needed filesystems..**
- mount -B /dev /target/dev
- mount -t proc none /target/proc
- mount -t sysfs none /target/sys
- mount -t efivarfs none /target/sys/firmware/efi/efivars **[only needed if UEFI]**
In the bootloader cluster of items [Mac, Non-Mac]<br> add BIOS/UEFI to Non-Mac<br>
[Modify Bootloader (non-Macintosh)](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#bootloader-non-macintosh)<br>
before:
#### Bootloader (non-Macintosh)
* Set up the bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware.
```shell
apk add grub grub-bios
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --boot-directory=/boot /dev/sda
```
after:
#### Bootloader BIOS (non-Macintosh)
* Set up the BIOS Bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware. or UEFI Hardware
```shell
apk add grub grub-bios
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --boot-directory=/boot /dev/sda
```
#### Bootloader UEFI (non-Macintosh)
* Set up the UEFI Bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware. or BIOS Hardware
```shell
apk add grub grub-efi
grub-mkconfig -o /boot/grub/grub.cfg
mkdir /efi
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
```
there still might be a few gremlins here, but i add this now so i can remember what i did.
initially got 3 UEFI systems to test UEFI installs on so as time progresses i might have time to create the updates myself.https://git.adelielinux.org/adelie/gcompat/-/issues/347Question: Running Discord2022-02-01T15:21:26ZBo-Ru JuQuestion: Running Discord# Description
I tried running the official binary from Discord today with gcompat installed on musl Void Linux, but the output of the Discord binary was simply `Segmentation fault`. There seems to be no issues similar to this on glibc di...# Description
I tried running the official binary from Discord today with gcompat installed on musl Void Linux, but the output of the Discord binary was simply `Segmentation fault`. There seems to be no issues similar to this on glibc distributions, and I have all the required dependencies installed. Therefore, I tried running `ldd <path to Discord>`, and the following is the output:
```
/lib64/ld-linux-x86-64.so.2 (0x7f29cf68b000)
libffmpeg.so => ./Discord/libffmpeg.so (0x7f29c6ad5000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7f29cf68b000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f29cf68b000)
libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x7f29c6a7b000)
libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x7f29c6947000)
libxshmfence.so.1 => /lib/libxshmfence.so.1 (0x7f29c6744000)
libgio-2.0.so.0 => /lib/libgio-2.0.so.0 (0x7f29c655e000)
libnss3.so => /lib/libnss3.so (0x7f29c6423000)
libnssutil3.so => /lib/libnssutil3.so (0x7f29c63f0000)
libsmime3.so => /lib/libsmime3.so (0x7f29c63c5000)
libnspr4.so => /lib/libnspr4.so (0x7f29c637b000)
libatk-1.0.so.0 => /lib/libatk-1.0.so.0 (0x7f29c6352000)
libatk-bridge-2.0.so.0 => /lib/libatk-bridge-2.0.so.0 (0x7f29c631c000)
libdbus-1.so.3 => /lib/libdbus-1.so.3 (0x7f29c62c9000)
libdrm.so.2 => /lib/libdrm.so.2 (0x7f29c62b3000)
libgdk_pixbuf-2.0.so.0 => /lib/libgdk_pixbuf-2.0.so.0 (0x7f29c6285000)
libgtk-3.so.0 => /lib/libgtk-3.so.0 (0x7f29c5a8a000)
libgdk-3.so.0 => /lib/libgdk-3.so.0 (0x7f29c5989000)
libpango-1.0.so.0 => /lib/libpango-1.0.so.0 (0x7f29c5923000)
libcairo.so.2 => /lib/libcairo.so.2 (0x7f29c57ed000)
libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f29cf68b000)
libX11.so.6 => /lib/libX11.so.6 (0x7f29c56aa000)
libXcomposite.so.1 => /lib/libXcomposite.so.1 (0x7f29c56a5000)
libXdamage.so.1 => /lib/libXdamage.so.1 (0x7f29c56a0000)
libXext.so.6 => /lib/libXext.so.6 (0x7f29c568b000)
libXfixes.so.3 => /lib/libXfixes.so.3 (0x7f29c5682000)
libXrandr.so.2 => /lib/libXrandr.so.2 (0x7f29c5675000)
libexpat.so.1 => /lib/libexpat.so.1 (0x7f29c5644000)
libxcb.so.1 => /lib/libxcb.so.1 (0x7f29c561a000)
libxkbcommon.so.0 => /lib/libxkbcommon.so.0 (0x7f29c55d2000)
libgbm.so.1 => /lib/libgbm.so.1 (0x7f29c55c2000)
libasound.so.2 => /lib/libasound.so.2 (0x7f29c54bb000)
libatspi.so.0 => /lib/libatspi.so.0 (0x7f29c5480000)
libcups.so.2 => /lib/libcups.so.2 (0x7f29c53e5000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x7f29c53cb000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f29cf68b000)
ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x7f29c53c4000)
libffi.so.7 => /lib/libffi.so.7 (0x7f29c53b8000)
libpcre.so.1 => /lib/libpcre.so.1 (0x7f29c533c000)
libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x7f29c5336000)
libz.so.1 => /lib/libz.so.1 (0x7f29c531c000)
libmount.so.1 => /lib/libmount.so.1 (0x7f29c52be000)
libplc4.so => /lib/libplc4.so (0x7f29c52b7000)
libplds4.so => /lib/libplds4.so (0x7f29c52b1000)
libintl.so.8 => /lib/libintl.so.8 (0x7f29c52a3000)
libpng16.so.16 => /lib/libpng16.so.16 (0x7f29c526e000)
libjpeg.so.8 => /lib/libjpeg.so.8 (0x7f29c51dc000)
libpangocairo-1.0.so.0 => /lib/libpangocairo-1.0.so.0 (0x7f29c51cb000)
libharfbuzz.so.0 => /lib/libharfbuzz.so.0 (0x7f29c50f3000)
libpangoft2-1.0.so.0 => /lib/libpangoft2-1.0.so.0 (0x7f29c50d9000)
libfontconfig.so.1 => /lib/libfontconfig.so.1 (0x7f29c5093000)
libfribidi.so.0 => /lib/libfribidi.so.0 (0x7f29c5073000)
libcairo-gobject.so.2 => /lib/libcairo-gobject.so.2 (0x7f29c5067000)
libepoxy.so.0 => /lib/libepoxy.so.0 (0x7f29c4f36000)
libXi.so.6 => /lib/libXi.so.6 (0x7f29c4f24000)
libwayland-client.so.0 => /lib/libwayland-client.so.0 (0x7f29c4f14000)
libwayland-cursor.so.0 => /lib/libwayland-cursor.so.0 (0x7f29c4f0b000)
libwayland-egl.so.1 => /lib/libwayland-egl.so.1 (0x7f29c4f06000)
libXcursor.so.1 => /lib/libXcursor.so.1 (0x7f29c4ef9000)
libXinerama.so.1 => /lib/libXinerama.so.1 (0x7f29c4cf6000)
libthai.so.0 => /lib/libthai.so.0 (0x7f29c4ceb000)
libpixman-1.so.0 => /lib/libpixman-1.so.0 (0x7f29c4c44000)
libfreetype.so.6 => /lib/libfreetype.so.6 (0x7f29c4b92000)
libEGL.so.1 => /lib/libEGL.so.1 (0x7f29c4b80000)
libxcb-shm.so.0 => /lib/libxcb-shm.so.0 (0x7f29c4b7b000)
libxcb-render.so.0 => /lib/libxcb-render.so.0 (0x7f29c4b6c000)
libXrender.so.1 => /lib/libXrender.so.1 (0x7f29c4962000)
libGL.so.1 => /lib/libGL.so.1 (0x7f29c4886000)
libXau.so.6 => /lib/libXau.so.6 (0x7f29c4881000)
libXdmcp.so.6 => /lib/libXdmcp.so.6 (0x7f29c4879000)
libwayland-server.so.0 => /lib/libwayland-server.so.0 (0x7f29c4863000)
libstdc++.so.6 => /lib/libstdc++.so.6 (0x7f29c45d5000)
libavahi-common.so.3 => /lib/libavahi-common.so.3 (0x7f29c45c7000)
libavahi-client.so.3 => /lib/libavahi-client.so.3 (0x7f29c45b3000)
libgnutls.so.30 => /lib/libgnutls.so.30 (0x7f29c43ac000)
libblkid.so.1 => /lib/libblkid.so.1 (0x7f29c4358000)
libgraphite2.so.3 => /lib/libgraphite2.so.3 (0x7f29c432e000)
libuuid.so.1 => /lib/libuuid.so.1 (0x7f29c4325000)
libdatrie.so.1 => /lib/libdatrie.so.1 (0x7f29c431b000)
libbz2.so.1 => /lib/libbz2.so.1 (0x7f29c4308000)
libGLdispatch.so.0 => /lib/libGLdispatch.so.0 (0x7f29c4219000)
libGLX.so.0 => /lib/libGLX.so.0 (0x7f29c4207000)
libp11-kit.so.0 => /lib/libp11-kit.so.0 (0x7f29c40dc000)
libidn2.so.0 => /lib/libidn2.so.0 (0x7f29c40b8000)
libunistring.so.2 => /lib/libunistring.so.2 (0x7f29c3d36000)
libtasn1.so.6 => /lib/libtasn1.so.6 (0x7f29c3d20000)
libnettle.so.8 => /lib/libnettle.so.8 (0x7f29c3cd8000)
libhogweed.so.6 => /lib/libhogweed.so.6 (0x7f29c3c8f000)
libgmp.so.10 => /lib/libgmp.so.10 (0x7f29c3c12000)
Error relocating ./Discord/libffmpeg.so: __mbrlen: symbol not found
Error relocating ./Discord/libffmpeg.so: strtoll_l: symbol not found
Error relocating ./Discord/libffmpeg.so: strtoull_l: symbol not found
Error relocating ./Discord/Discord: __register_atfork: symbol not found
Error relocating ./Discord/Discord: __memset_chk: symbol not found
Error relocating ./Discord/Discord: __snprintf_chk: symbol not found
Error relocating ./Discord/Discord: __sprintf_chk: symbol not found
Error relocating ./Discord/Discord: __memcpy_chk: symbol not found
Error relocating ./Discord/Discord: __fprintf_chk: symbol not found
Error relocating ./Discord/Discord: __memmove_chk: symbol not found
Error relocating ./Discord/Discord: gnu_get_libc_version: symbol not found
Error relocating ./Discord/Discord: __fdelt_chk: symbol not found
Error relocating ./Discord/Discord: __vsnprintf_chk: symbol not found
Error relocating ./Discord/Discord: __sbrk: symbol not found
Error relocating ./Discord/Discord: __res_nclose: symbol not found
Error relocating ./Discord/Discord: __res_ninit: symbol not found
Error relocating ./Discord/Discord: __vfprintf_chk: symbol not found
Error relocating ./Discord/Discord: __longjmp_chk: symbol not found
Error relocating ./Discord/Discord: backtrace: symbol not found
Error relocating ./Discord/Discord: __strncat_chk: symbol not found
Error relocating ./Discord/Discord: __sched_cpualloc: symbol not found
Error relocating ./Discord/Discord: __sched_cpufree: symbol not found
Error relocating ./Discord/Discord: random_r: symbol not found
Error relocating ./Discord/Discord: initstate_r: symbol not found
Error relocating ./Discord/Discord: __mbrlen: symbol not found
Error relocating ./Discord/Discord: strtoll_l: symbol not found
Error relocating ./Discord/Discord: strtoull_l: symbol not found
Error relocating ./Discord/Discord: __longjmp_chk: symbol not found
Error relocating ./Discord/Discord: __libc_stack_end: symbol not found
```
The part of errors contains glibc related errors, so I guessed that the issue might be caused by gcompat.
The `gnu_get_libc_version: symbol not found` error message seems strange to me because there's this in the README:
> The value of `GLIBC_FAKE_VERSION` will be returned as the result of `gnu_get_libc_version`. The current default is "2.8".
Is this something related to broken installation or is it that the functionalities are not yet implemented?
# Additional Information
## `uname -a`:
```
Linux voidlinux 5.15.16_1 #1 SMP Thu Jan 20 17:19:29 UTC 2022 x86_64 GNU/Linux
```
## `xbps-query gcompat`:
```
architecture: x86_64-musl
build-options: libucontext
changelog: https://code.foxkit.us/adelie/gcompat/-/raw/current/CHANGELOG.rst
filename-sha256: f9c14671fa23b3bc3d12bfbcffb84a047011a87370e955d5f8f8c87bed626ebb
filename-size: 33KB
homepage: https://code.foxkit.us/adelie/gcompat
install-date: 2022-01-26 16:40 CST
installed_size: 90KB
license: ISC
maintainer: Érico Nogueira <ericonr@disroot.org>
metafile-sha256: e82fc6861807621eb1f793004e3e989cf978bc0d186b2590c7c155b75393ddcd
pkgname: gcompat
pkgver: gcompat-1.0.0_2
repository: https://alpha.de.repo.voidlinux.org/current/musl
run_depends:
libucontext>=1.0_1
musl-obstack>=1.2.1_1
musl>=1.1.21_1
shlib-provides:
libgcompat.so.0
shlib-requires:
libucontext.so.1
libobstack.so.1
libc.so
short_desc: Compatibility layer to allow running glibc binaries on musl systems
source-revisions: gcompat:25f75fa302
state: installed
```https://git.adelielinux.org/adelie/packages/-/issues/448user/libevent: FTTFS: FAIL test/regress_bufferevent.c:278: lock: lock error[L...2023-03-23T14:27:04ZZach van Rijnuser/libevent: FTTFS: FAIL test/regress_bufferevent.c:278: lock: lock error[Lost connection!]Found on x86_64 and aarch64.
```
make[3]: Entering directory '/root/packages/user/libevent/src/libevent-2.1.12-stable'
./test/test.sh -b EPOLL
./test/test.sh -b SELECT
Running tests:
EPOLL
Running tests:
SELECT
test-eof: test-eof: O...Found on x86_64 and aarch64.
```
make[3]: Entering directory '/root/packages/user/libevent/src/libevent-2.1.12-stable'
./test/test.sh -b EPOLL
./test/test.sh -b SELECT
Running tests:
EPOLL
Running tests:
SELECT
test-eof: test-eof: OKAY
test-closed: OKAY
test-closed: OKAY
test-weof: [warn] event_base_new_with_config: no event mechanism available
OKAY
test-weof: OKAY
test-time: OKAY
test-time: OKAY
test-changelist: OKAY
test-fdleak: OKAY
test-changelist: OKAY
test-dumpevents: OKAY (output not checked)
regress: OKAY
test-fdleak: OKAY
test-dumpevents: OKAY (output not checked)
regress: OKAY
regress_debug: OKAY
regress_debug: bufferevent/bufferevent_pair_release_lock:
FAIL test/regress_bufferevent.c:278: lock: lock error[Lost connection!]
[bufferevent_pair_release_lock FAILED]
bufferevent/bufferevent_pair_release_lock:
FAIL test/regress_bufferevent.c:278: lock: lock error[Lost connection!]
[bufferevent_pair_release_lock FAILED]
1/343 TESTS FAILED. (48 skipped)
FAILED
make[3]: *** [Makefile:3114: test_runner_select] Error 1
make[3]: *** Waiting for unfinished jobs....
1/352 TESTS FAILED. (39 skipped)
FAILED
make[3]: *** [Makefile:3112: test_runner_epoll] Error 1
make[3]: Leaving directory '/root/packages/user/libevent/src/libevent-2.1.12-stable'
make[2]: *** [Makefile:2516: check-TESTS] Error 2
make[2]: Leaving directory '/root/packages/user/libevent/src/libevent-2.1.12-stable'
make[1]: *** [Makefile:2791: check-am] Error 2
make[1]: Leaving directory '/root/packages/user/libevent/src/libevent-2.1.12-stable'
make: *** [Makefile:2793: check] Error 2
```
Full log is here: [20220110-00_53_45.019845553_abiword.log](/uploads/f5c2e3b5acd384a0a4f90f0bed25b82f/20220110-00_53_45.019845553_abiword.log)https://git.adelielinux.org/adelie/packages/-/issues/439system/gcc: warning: "LINK_EH_SPEC" redefined2022-01-08T17:18:04ZZach van Rijnsystem/gcc: warning: "LINK_EH_SPEC" redefinedFound on ppc64. Need to review the current patch set.
```
In file included from tm.h:31,
from insn-automata.c:8:
/root/packages/system/gcc/src/gcc-8.5.0/gcc/config/rs6000/sysv4.h:818: warning: "LINK_EH_SPEC" redefined
...Found on ppc64. Need to review the current patch set.
```
In file included from tm.h:31,
from insn-automata.c:8:
/root/packages/system/gcc/src/gcc-8.5.0/gcc/config/rs6000/sysv4.h:818: warning: "LINK_EH_SPEC" redefined
# define LINK_EH_SPEC "%{!static|static-pie:--eh-frame-hdr} "
In file included from tm.h:29,
from insn-automata.c:8:
/root/packages/system/gcc/src/gcc-8.5.0/gcc/config/gnu-user.h:134: note: this is the location of the previous definition
#define LINK_EH_SPEC "%{!static|" PIE_SPEC ":--eh-frame-hdr} "
```https://git.adelielinux.org/adelie/packages/-/issues/434user/vala: multiple test failures (tests do not even build/run)2022-01-08T07:43:37ZZach van Rijnuser/vala: multiple test failures (tests do not even build/run)[vala.txt](/uploads/ff9624c4c8e820cd274a1095e1292daa/vala.txt)[vala.txt](/uploads/ff9624c4c8e820cd274a1095e1292daa/vala.txt)https://git.adelielinux.org/adelie/packages/-/issues/420experimental/elfutils: multiple test failures on pmmx and x86_642023-10-30T15:47:54ZZach van Rijnexperimental/elfutils: multiple test failures on pmmx and x86_64Likely on x86_64 too.
Note that this package is new and not yet pushed to any repository. Documenting here anyway.
Note further that Alpine does not run any tests on this package.
```
...
==============================================...Likely on x86_64 too.
Note that this package is new and not yet pushed to any repository. Documenting here anyway.
Note further that Alpine does not run any tests on this package.
```
...
============================================================================
Testsuite summary for elfutils 0.185
============================================================================
# TOTAL: 226
# PASS: 211
# SKIP: 5
# XFAIL: 0
# FAIL: 10
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to https://sourceware.org/bugzilla
============================================================================
make[3]: *** [Makefile:2487: test-suite.log] Error 1
make[2]: *** [Makefile:2595: check-TESTS] Error 2
make[1]: *** [Makefile:4251: check-am] Error 2
make: *** [Makefile:532: check-recursive] Error 1
```
Here are the failures:
```
FAIL: run-large-elf-file.sh
FAIL: run-strip-strmerge.sh
FAIL: run-disasm-x86-64.sh
FAIL: run-backtrace-native.sh
FAIL: run-backtrace-native-core.sh
FAIL: run-stack-d-test.sh
FAIL: run-stack-i-test.sh
FAIL: run-stack-demangled-test.sh
FAIL: run-deleted.sh
FAIL: run-compress-test.sh
```
As for why:
[run-backtrace-native.sh.log](/uploads/a4e4eafe93e8c9faadd27723e9579987/run-backtrace-native.sh.log)
[run-backtrace-native-core.sh.log](/uploads/f4804826322d1eef5debdbdece2c96f9/run-backtrace-native-core.sh.log)
[run-compress-test.sh.log](/uploads/cf0af93dfba679e2467643d5d70f4d29/run-compress-test.sh.log)
[run-deleted.sh.log](/uploads/8e0f36603cd47609f0afd7a8743e8a12/run-deleted.sh.log)
[run-disasm-x86-64.sh.log](/uploads/4f09bd28d96fcf0ee93993f2a502504f/run-disasm-x86-64.sh.log)
[run-large-elf-file.sh.log](/uploads/ef85b4378422f1b68f6f3ac38b0ffff5/run-large-elf-file.sh.log)
[run-stack-demangled-test.sh.log](/uploads/0f60e2a330a3a013675a9f2640387138/run-stack-demangled-test.sh.log)
[run-stack-d-test.sh.log](/uploads/d348f0d00823d3418521a94ad6e471ec/run-stack-d-test.sh.log)
[run-stack-i-test.sh.log](/uploads/46d88ef8b2dfda53c03fe5194a3a1108/run-stack-i-test.sh.log)
[run-strip-strmerge.sh.log](/uploads/f896df48f8eb25d8fc6cd2b0fb2f30d4/run-strip-strmerge.sh.log)https://git.adelielinux.org/adelie/abuild/-/issues/1abuild: the upgrade option should probably ensure --latest2022-01-04T20:39:06ZZach van Rijnabuild: the upgrade option should probably ensure --latestIn some cases, using e.g. `abuild -R` or `abuild -u` will build and install (`apk add`) dependencies but this action may not have any effect for later-built packages.
Consider adding `--latest` to the `apk add` portion of the implementa...In some cases, using e.g. `abuild -R` or `abuild -u` will build and install (`apk add`) dependencies but this action may not have any effect for later-built packages.
Consider adding `--latest` to the `apk add` portion of the implementation within the `abuild` installation feature(s).
The equivalent behavior is that of `apk upgrade --available`.https://git.adelielinux.org/adelie/packages/-/issues/406system/patch (possibly others): remove autotools from checkdepends2023-01-05T19:27:26ZZach van Rijnsystem/patch (possibly others): remove autotools from checkdependsSee this discussion: !639
We need to discuss whether we want all packages to be built the same or not, regardless of whether `!check` is provided.See this discussion: !639
We need to discuss whether we want all packages to be built the same or not, regardless of whether `!check` is provided.https://git.adelielinux.org/adelie/site-ng/-/issues/5Logo is not always rendered sharply2021-11-11T19:21:17ZZach van RijnLogo is not always rendered sharplyNeeds triage. Some formats, sizes, browsers, etc. of the logo appear a bit blurry. I know we can do better.Needs triage. Some formats, sizes, browsers, etc. of the logo appear a bit blurry. I know we can do better.https://git.adelielinux.org/adelie/horizon/-/issues/326"Custom" installation option doesn't install X11 when a DE is selected [1.0rc2]2023-10-17T01:42:25ZTiago Silva"Custom" installation option doesn't install X11 when a DE is selected [1.0rc2]I think I'm interpreting this correctly.
I chose a Custom Install in Horizon, with the options:
- Desktop Environments
- KDE
- Documentation
- Internet Software
Horizon finished the install and I booted into the new system: never reac...I think I'm interpreting this correctly.
I chose a Custom Install in Horizon, with the options:
- Desktop Environments
- KDE
- Documentation
- Internet Software
Horizon finished the install and I booted into the new system: never reached GUI, VTY 7 only had a blinking cursor
Opened another VTY and tried `$ startx` and `# startx`: "not found"
Tried again with the same options and this time saved the installfile and opened it to check what's being installed:
!["Custom" installfile](/uploads/61fc2c642977c0f6b649354339276e0b/AdelieKDE-2021-09-16-00-49-01.png)
Installed a "Standard" configuration and opened the installfile to compare:
!["Standard" installfile](/uploads/f4ddbcc50cf0c58a589050ee48f700e0/AdelieKDE-2021-09-16-00-20-30.png)
`X11` and `sddm` packages are being installed on "Standard" but are missing on "Custom"
Shouldn't the selection of any item from "Desktop Environments" or "Windows Managers" automatically add X11 (and probably sddm as well, to manage the DE)?0.9.9https://git.adelielinux.org/adelie/horizon/-/issues/324"Compact" installation option fails (maybe while installing consolefonts) [1....2023-10-17T01:46:46ZTiago Silva"Compact" installation option fails (maybe while installing consolefonts) [1.0rc2]The mentioned installation option fails consistently.
Hardware is VirtualBox, Linux-64bit (Other), 1GB RAM, BIOS.
Can't extract text file of installation logs, so I hope you don't mind the attached screenshots:
![Horizon script error #1]...The mentioned installation option fails consistently.
Hardware is VirtualBox, Linux-64bit (Other), 1GB RAM, BIOS.
Can't extract text file of installation logs, so I hope you don't mind the attached screenshots:
![Horizon script error #1](/uploads/6c3eee1897669ba1bdb4b2ef413be188/VirtualBox_Adelie_LXQt_12_09_2021_20_10_19.png)
![Horizon script error #2](/uploads/2c8f7b78fbe527e1a7b268243605d861/VirtualBox_Adelie_LXQt_12_09_2021_20_10_58.png)
![Horizon script fatal error](/uploads/cf4a9e6213a4904453838984e1cb9cd6/VirtualBox_Adelie_LXQt_12_09_2021_20_11_06.png)
![horizon script options (```installfile```)](/uploads/0fcb6891511898a2371075814851e88b/VirtualBox_Adelie_LXQt_12_09_2021_20_13_57.png)0.9.9https://git.adelielinux.org/adelie/horizon/-/issues/323"Standard" and "Mobile" installation options do not honor keyboard layout cho...2023-10-17T01:46:06ZTiago Silva"Standard" and "Mobile" installation options do not honor keyboard layout chosen in Horizon [1.0rc2]That's basically it. I chose "pt" layout on HorizonUI, and the KDE on the hard disk has "en-us" installed, and "pt-pt" still has to be added manually in KDE's settings afterwards.
Other installation variants couldn't be tested.That's basically it. I chose "pt" layout on HorizonUI, and the KDE on the hard disk has "en-us" installed, and "pt-pt" still has to be added manually in KDE's settings afterwards.
Other installation variants couldn't be tested.0.9.9A. WilcoxA. Wilcoxhttps://git.adelielinux.org/adelie/horizon/-/issues/322Horizon doesn't validate IPv4 settings on Manual Network configuration [1.0rc2]2023-10-17T01:45:47ZTiago SilvaHorizon doesn't validate IPv4 settings on Manual Network configuration [1.0rc2]I can put any value I want, and Horizon will let me proceed, not validating the fields or trying to configure an interface and then ping the chosen DNS server and/or Adélie's repos as a sanity check.
I have configured:
- IP: **225.999.99...I can put any value I want, and Horizon will let me proceed, not validating the fields or trying to configure an interface and then ping the chosen DNS server and/or Adélie's repos as a sanity check.
I have configured:
- IP: **225.999.999.222**
- Netmask: 255.255.255.0 /24 (default)
- Gateway: **255.255.255.111**
- DNS: 9.9.9.9 (default)
And Horizon just let me hit ```Continue (F8)``` without signaling any error.
- There is no 999 in dotted-decimal IPv4 addresses
- The IP is in the multicast address range (even if the other address bytes were valid).
- The gateway isn't on the same network as the IP
- The gateway is in Class E address space1.0-RELEASEhttps://git.adelielinux.org/adelie/blog-ng/-/issues/8Recent Posts/Comments text is too long2021-07-22T19:21:23ZZach van RijnRecent Posts/Comments text is too longNot sure the best approach to this; will adding bullets be sufficient? Truncate titles? Remove usernames or titles?![Screenshot_from_2021-07-22_14-20-10](/uploads/e57b3655f778753b5e11b2e4bba9178a/Screenshot_from_2021-07-22_14-20-10.png)Not sure the best approach to this; will adding bullets be sufficient? Truncate titles? Remove usernames or titles?![Screenshot_from_2021-07-22_14-20-10](/uploads/e57b3655f778753b5e11b2e4bba9178a/Screenshot_from_2021-07-22_14-20-10.png)https://git.adelielinux.org/adelie/blog-ng/-/issues/4Improve post metadata listings2021-07-22T13:32:21ZZach van RijnImprove post metadata listingsOn the Blog homepage, subtitles/metadata such as `3 Comments / Release Announcements / By awilfox` are unwieldy.
I don't think we need to show how many comments there are, or at least not in this way.
Maybe something like: `Release Ann...On the Blog homepage, subtitles/metadata such as `3 Comments / Release Announcements / By awilfox` are unwieldy.
I don't think we need to show how many comments there are, or at least not in this way.
Maybe something like: `Release Announcements` in a slick font, then right-aligned `by awilfox`, and somewhere else `3 Comments`?
Proposals welcome.https://git.adelielinux.org/adelie/blog-ng/-/issues/3TODO: continue to borrow elements from site theme2021-07-22T12:36:32ZZach van RijnTODO: continue to borrow elements from site themeUse `blog-sidebar-right.html` and `single-post-2.html` for inspiration. Of course, remove the huge images from these pages.Use `blog-sidebar-right.html` and `single-post-2.html` for inspiration. Of course, remove the huge images from these pages.https://git.adelielinux.org/adelie/site-ng/-/issues/3Site is unnecessarily large (JS and CSS)2021-07-13T16:06:35ZZach van RijnSite is unnecessarily large (JS and CSS)Much of the JS and CSS is unnecessary (due to the site being derived from a template).
Shake out unnecessary code and assets.Much of the JS and CSS is unnecessary (due to the site being derived from a template).
Shake out unnecessary code and assets.https://git.adelielinux.org/adelie/horizon/-/issues/319Network Setup is Required for Installation2023-10-17T01:49:14ZAsh NolanNetwork Setup is Required for InstallationWhen installing Adélie via Live CD the `Network Setup` screen greys out the option to skip network setup with the explanation:
> Networking cannot be skipped because a network connection is required to install packages.
This presents a ...When installing Adélie via Live CD the `Network Setup` screen greys out the option to skip network setup with the explanation:
> Networking cannot be skipped because a network connection is required to install packages.
This presents a problem for users without access to internet connectivity including those without an available internet connection or those who choose to perform network setup after install.
Discovered on version `Horizon Qt UI 0.9.0`.2.0https://git.adelielinux.org/adelie/gcompat/-/issues/342Alpine&Dotnet&Grpc: __strftime_l and __strdup : symbols not found2021-06-08T13:09:47ZPavel BotovAlpine&Dotnet&Grpc: __strftime_l and __strdup : symbols not foundI have to build docker container based on Alpine to run dotnet microservice with gRPC network framework.
For previous versions of Alpine (3.6...3.12) I've used various workarounds like: libc6-compat from Alpine repository and custom glib...I have to build docker container based on Alpine to run dotnet microservice with gRPC network framework.
For previous versions of Alpine (3.6...3.12) I've used various workarounds like: libc6-compat from Alpine repository and custom glibc from sgerrand.
But current Alpine 3.13 uses musl 1.2.2, witch is not compatible with last workaround. So, I'm trying gcompat...
`# apk add --no-cache gcompat`
...
`# ldd /root/.nuget/packages/grpc.core/2.38.0/runtimes/linux-x64/native/libgrpc_csharp_ext.x64.so`
`/lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
libdl.so.2 => /lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
librt.so.1 => /lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
libpthread.so.0 => /lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
libm.so.6 => /lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7fc6bb281000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc6bb267000)
libc.so.6 => /lib/ld-musl-x86_64.so.1 (0x7fc6bbc74000)
ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x7fc6bb261000)
Error relocating /root/.nuget/packages/grpc.core/2.38.0/runtimes/linux-x64/native/libgrpc_csharp_ext.x64.so: __strdup: symbol not found`
...
`# ldd /root/.nuget/packages/grpc.tools/2.38.0/tools/linux_x64/protoc`
`/lib64/ld-linux-x86-64.so.2 (0x7f8947a3d000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f8947a3d000)
libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f8947a3d000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f8947a3d000)
ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x7f8947a37000)
Error relocating /root/.nuget/packages/grpc.tools/2.38.0/tools/linux_x64/protoc: __strftime_l: symbol not found`
Is it a bug of gcompat?