e79a9fbda897c088c6067c2ea75aeee00a3d00d7
3
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
eee77d5a38 |
voxtype-bin: update to 1.1.0 (#640)
* voxtype-bin: update to 1.1.0 Ship the signed 1.1.0 release assets, baseline and ARM binaries, and the complete Quickshell and OSD style trees. Add OpenVINO optional dependencies from #526 and select the baseline binary automatically on pre-AVX2 hosts. * voxtype-bin: bump pkgrel past the published 1.1.0-1 voxtype-bin 1.1.0-1 is already published to edge, rc and stable from master's upstream sync. This branch changes that package's contents (baseline binary, OSD styles and recipes, the install hook, OpenVINO optdepends) without changing its version, so publish.yml would call it already published and skip it, and publish-artifact refuses different bytes under an existing filename. pacman would not offer it as an upgrade either. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * voxtype-bin: list accelerator optdepends for x86_64 only makepkg appends optdepends_$CARCH to optdepends rather than replacing it, so optdepends_aarch64 did not drop the Vulkan, CUDA, ROCm and MIGraphX entries on aarch64: it listed all sixteen shared ones and then eleven of them a second time. The accelerator runtimes move to optdepends_x86_64 beside the OpenVINO ones, and the aarch64 array goes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * voxtype-bin: move pre-AVX2 hosts to the baseline build on upgrade The baseline pick in _set_default_backend only runs when no backend was saved, which is a fresh install. Every release before 1.1.0 gave a CPU without AVX2 voxtype-avx2, and pre_upgrade saves that path, so post_upgrade restored the build the host cannot run and the machines the baseline binary exists for never reached it. A saved AVX2 or AVX-512 build whose instruction set the CPU lacks is now picked again; GPU and ONNX choices are left alone. tests/voxtype-bin-install.sh covers the fresh-install pick and the upgrade cases, and runs with the other self-tests. It borrows the hook's fixed /tmp/.voxtype-backend-upgrade, so it refuses to start when anything is already there, a dangling symlink included: CI runs it as root, and writing through a planted link would land outside the test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex XHigh <noreply@openai.com> * tests: keep voxtype-bin-install's upgrade state out of /tmp The test borrowed the hook's /tmp/.voxtype-backend-upgrade and checked it was free only once, so a real voxtype-bin upgrade writing its state during the run could have that state overwritten or deleted, and the hook would then lose the user's backend. The test now redefines the sourced _preserve_or_set_backend with the path moved into its own directory, and fails outright if the hook stops using that path rather than passing without reading it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex XHigh <noreply@openai.com> * tests: never parse voxtype-bin-install's temp path as code The redefined _preserve_or_set_backend went through eval with the mktemp path pasted in, so a TMPDIR holding shell syntax -- a directory named $HOME, or $(...) -- was expanded or run when the function was called. It now carries a reference to $SAVED, which expands to the path only at run time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex XHigh <noreply@openai.com> --------- Co-authored-by: Spencer Bull <spencer@omarchy.org> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex XHigh <noreply@openai.com> |
||
|
|
fbfbda4eca |
Package Omawake 0.0.3 and Omaspeak 0.0.3 with service-removal cleanup hooks (#503)
* Package Omawake 0.0.3 and Omaspeak 0.0.2 Bump both -bin packages to the model-support roadmap delivery: Omawake 0.0.3: - W02-W05 setup/activation/cache gates audited and closed - W07 pinned catalog URL health checks and import diagnostics - W08 Moonshine Small/Medium benchmarked; both deferred (Tiny default) - W09 Spanish wake profile (multilingual Whisper Base INT8, es) - W10 connection-owned playback pauses (HoldPause) Omaspeak 0.0.2: - S09 Kokoro 82M: Kokoro-capable packaged provider (supertonic;kokoro_tts) with espeak-ng-data.bin shipped beside the executable, 54 named voices - S10 catalog URL checks, Spanish speech profile, consistent status shape - S07 streaming deferred at the current pin Upstream: omawake v0.0.3, omaspeak v0.0.2 (aarch64 + x86_64 verified on promaxgb10-d666 CUDA and local NPU installs). * omaspeak-bin: install espeak-ng-data.bin beside the packaged library * omaspeak-bin: bump to 0.0.3-rc.1 (catalog-managed eSpeak data) - The tarball no longer ships espeak-ng-data.bin: the Kokoro catalog row pins the data package as a model asset (downloaded/verified/installed into the model directory with the GGUF), so the core package ships no model data at all. - Both arch checksums taken from the v0.0.3-rc.1 SHA256SUMS.txt. * omaspeak-bin: finalize at 0.0.3 * Stop setup-created Oma services before pacman removes their binaries * Drop stale release-verification fixtures from the branch These were swept in by git add -A during the version bumps: packaged copies of old releases (0.0.1 tarballs and extracted trees, ~80 MB) belong to the local verification workflow, not to the package repo. The consolidated upstream PR should carry only the package changes, hooks and the removal regression suite. * Update removal-test fixture versions to the packaged finals * Ask systemd to reset only an Oma unit that actually failed The removal helper reset the failed state of every unit it stopped, but systemd accepts ResetFailed for a unit that is in the failed state alone. For any other state it answers that the unit is not loaded and exits non-zero, and because the helper runs under errexit while the hook aborts on failure, a healthy unit then aborted the whole transaction: (2/2) Stop and remove omaspeak user services before package removal Failed to reset failed state of unit omaspeak.service: Unit omaspeak.service not loaded. :: Could not clean up omaspeak for jacob; removal aborted. That is the ordinary case, as the packaged service ships disabled and an enabled one is commonly stopped rather than failed. Read the active state after the stop and ask for the reset only where it applies, so a failed unit still loses its failed state along with its rate and restart counters while a clean unit no longer fails the removal. A reset that a reachable manager still refuses stays fatal. Model the rule in the removal suite, where reset-failed now follows the active state the way a real manager does, and cover both outcomes: an inactive unit must not be asked for, a failed one must be reset between the stop and the disable, and a refused reset must still fail the hook. * Keep removal cleanup faithful to how systemd reads configuration Both defects from the review of e025111 sat in the shared package-remove helper, so both packages were affected the same way. An offline user's drop-in was recognised by grep '^ExecStart=', while the configuration parser throws away the whitespace around an assignment (parse_line() strips the line and both halves of the assignment). A drop-in naming a development build as ExecStart = ExecStart = /home/alice/build/omawake daemon therefore went unmatched, and the helper cleared away the generated base unit beside with its enablement links, right behind a service that was never meant to be the package's. Match an assignment the way the parser accepts one. The gate that decides whether a unit file is the generated one stays strict on purpose: only the exact generated shape is ever deleted. systemctl show-environment also prints every value the way a shell would read it, through shell_maybe_quote(SHELL_ESCAPE_POSIX), so an XDG_CONFIG_HOME with a space arrives as $'/home/alice/custom config'. The XDG_CONFIG_HOME=/* case saw neither form and kept the home's .config directory quietly, leaving the unit in the directory the manager really reads pointing at the removed binary. Decode that quoting character by character, without letting the text become shell syntax, and refuse a value that is neither a plain path nor a closed $'...' quote rather than delete what would have to be guessed at. A value that is not an absolute path stays the fallback it is in systemd itself. The fixtures now hand the helper the very text a manager prints, quoted by a mirror of that printer, and cover a quoted path with a space, an apostrophe and a backslash, an unreadable quoted value, a relative one, and each spacing of an offline override. Verified with the removal suite, 15 tests; the eight new assertions fail against the helper as it was. The other suites were not run here, as they reach for the network. pkgrel 3 -> 4 and the helper's checksum, in both recipes. Reported-by: spencerbull * Decode systemd control escapes during service removal systemctl C-escapes control bytes in show-environment output. Rejecting those valid values aborted package removal for every user, even when the affected account had no Oma service. Decode the printer’s named and octal escapes without evaluating shell syntax or stripping trailing newlines, and cover the real printer format in the fixtures. Co-Authored-By: GPT-6 XHigh <noreply@openai.com> --------- Co-authored-by: Spencer Bull <spencer@omarchy.org> Co-authored-by: GPT-6 XHigh <noreply@openai.com> |
||
|
|
8f45850b7d |
Package Dell XPS touchpad haptics (#86)
* feature: Add Dell haptic touchpad control, update default intensity * fix: polish Dell haptic touchpad package Use an MIT license file for the packaged scripts and prefer the active loginctl user in the install hook so the initial intensity setup targets the live desktop session instead of an arbitrary regular account. * fix: clean up Dell haptic touchpad package metadata Drop the bundled license file and align the package metadata so the package contents still build cleanly after the maintainer update. * fix: correct Dell haptic touchpad package URL Point the package metadata at the canonical omarchy-pkgs repository so users see the source location maintained under the omacom-io project. * feature: package Dell XPS haptics as standalone service * fix: tighten Dell haptics package setup |