Repository navigation
Keep a working libfprint fork during fingerprint setup - #12945
chessing234 wants to merge 1 commit into
Conversation
bec9890 to
f5480ef
Compare
|
Verified: No important actionable issue found in the scoped review of
The PR requests Review informationTest scope: Source inspection and isolated baseline/head runs of the real setup script with synthetic package metadata and stubbed privileged commands. No real package transaction, service restart, fingerprint enrollment, hardware behavior, or PAM changes were tested. Community review: Independent automated community review, unaffiliated with the Omarchy team, intended to help prepare PRs for their review. Automated AI review: Astra Medium initial inspection and synthesis, independent Opus 5.5 High and GPT 6 Sol Xhigh technical reviews, followed by verification of public claims against targeted evidence and a fresh Astra Medium editorial check. |
|
folding into #12110 — keep-working-fork is already on that branch. |
Summary
pacman -Qqprovides (libfprint/libfprint-2/libfprint-git) so community forks are not treated as missing.libfprint-gitwhen nothing usable is present (or only stocklibfprint); never--ask 4replace a provides-satisfying fork.fprintdafter a package change so enroll/verify use the on-disk library, not a stale mapped.so.Closes #11899
Test plan
./test/shell.d/fingerprint-package-test.shlibfprint-gitlibfprint→ replaced withlibfprint-gitlibfprint/libfprint-2→ left alonelibfprint-git→ no pacman touch