Give pinned libfprint-git an epoch and stop AUR sync

The pin to d79f157 rebuilt 1.94.10.r12.gd79f157-1.1, but those exact
filenames were already published, so promotion failed. And an untested
1.94.10.r220.g695663f build from master had already been released,
which sorts above the pinned version, so the pin could never reach
users anyway. epoch=1 makes the pinned build win the version
comparison and gives it promotable filenames; once published, the
commit-hash check skips further rebuilds.

Also disable AUR sync: the bot would otherwise regenerate the PKGBUILD
from AUR and wipe out both the pin and the epoch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

pkgbuilds/libfprint-git/.omarchy/package.json

@@ -1,4 +1,5 @@
 {
   "source": "aur",
+  "sync": false,
   "upstream_commit": "d225acd677e4a2af8f99698ea11386d8ad3af1bf"
 }

pkgbuilds/libfprint-git/PKGBUILD

@@ -12,6 +12,10 @@
 pkgname=libfprint-git
 pkgver=1.94.10.r12.gd79f157
 pkgrel=1.1
+# The repo already carries an untested 1.94.10.r220.g695663f build that sorts
+# above the pinned pkgver; the epoch makes the pinned build win the version
+# comparison and gives it a fresh filename that can be promoted.
+epoch=1
 pkgdesc="Library for fingerprint readers (libfprint master with FocalTech MOC updates)"
 url="https://fprint.freedesktop.org/"
 arch=(x86_64)