Package: unl0kr Version: 1.0.0+dfsg-1 Severity: minor Dear Maintainer,
unl0kr is meant to replace osk-sdl, which is no longer actively developed. However, migrating from the latter involves a number of manual steps which are error-prone and can render the system unusable if not executed properly. 1. unl0kr and osk-sdl can both be present on the system at the same time; this implies both will be built into the initramfs, even though only osk-sdl will actually be used. 2. after uninstalling osk-sdl, the crypttab either still points to its keyscript or doesn't include a keyscript option at all (which is the expected behaviour if osk-sdl was the only software of this type on the system) 3. in any case, it's up to the user to edit the crypttab to use the unl0kr keyscript; I believe it can be solved with small changes to calamares-settings- mobian for new image installs, but existing ones will have trouble migrating to unl0kr If both software were still being developed this would probably be fine, but I expect we'll want to get rid of osk-sdl in the future, and so providing an automated migration path would be needed. Regards, Arnaud -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-rt-amd64 (SMP w/64 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unl0kr depends on: ii libc6 2.37-7 ii libinih1 57-1 ii libinput10 1.23.0-2 ii libudev1 254.1-2 ii libxkbcommon0 1.5.0-1 unl0kr recommends no packages. unl0kr suggests no packages.
