Sorry, i'm not think about it, because every time used dark mode on phone🫣
"piper-tts-bin (AUR, maintainer gerliczkowalczuk) cannot be built by anyone right now. makepkg stops at source verification on a clean clone, before anything is compiled: $ git clone https://aur.archlinux.org/piper-tts-bin.git && cd piper-tts-bin $ makepkg -f ==> Verifying source file integrity with sha256sums... piper-tts.sh ... FAILED ==> ERROR: One or more files did not pass the validity check! The stale entry is the package's own wrapper script, not the upstream tarball: PKGBUILD:20 sha256sums=('a3e5c9429c36df01391a6296bfe6037e2a9040082f42a6907406c55986ec32a1') actual sha256sum piper-tts.sh 79fef77f228423f8f6f54fe1be7d726c96b2c9f1ac849a9386fdd85886463aa9 piper-tts.sh piper-tts.sh is the three-line wrapper added in commit 002f382: #!/bin/sh export LD_LIBRARY_PATH="/opt/piper-tts:${LD_LIBRARY_PATH}" exec /opt/piper-tts/piper "$@" The remote source is fine: piper_linux_x86_64.tar.gz from the 2023.11.14-2 release hashes to a50cb45f355b7af1f6d758c1b360717877ba0a398cc8cbe6d2a7a3a26e225992, which matches sha256sums_x86_64 exactly. Fix: run updpkgsums (or replace the literal with 79fef77f...) and bump pkgrel to 3, so users who already have -2 in their AUR cache pick up the corrected recipe. With that single line corrected the package builds, installs and works: piper-tts --help answers, ldd /opt/piper-tts/piper reports no missing libraries, and synthesis with ru_RU-irina-medium produced a 2.4 s WAV at a real-time factor of 0.136. I cannot post this as an AUR comment: registration is closed and I do not have an account. If someone here could file an orphan/update request or ping the maintainer, that would be appreciated. Thanks. https://github.com/Mystical89"; вт, 3 нояб. 2026 г., 09:31 Ralf Mardorf <[email protected]>: > On Tue, 2026-11-03 at 00:39 +0300, Ruslan Sivak wrote: > > If someone here could file an orphan/update request or ping the > > maintainer, that would be appreciated. > > HTML alone isn't enough, the text must be white on a slightly darker > white background so that the email is unreadable to the human eye. > > https://wiki.archlinux.org/title/General_guidelines#Plain_text > > The intended reader must therefore first make the email readable, only > to then discover that the OP is asking them to do something in the AUR > for them, without providing a direct link to it. >
