fprintd 1.90 matches for the new api-v2 and libfprint-1.90.1 which is already in portage (fprintd 0.90 matches for api-v1 and libfprint-1.0 in portage) please note that fprintd 1.90 also includes a module pam_fprintd Reproducible: Always
Created attachment 632374 [details] ebuild for new version ebuild for new version (uses meson) I patched out building the testing things as they need aditional packages. maybe we need an useflag for that. I install pam_fprintd from this package, maybe we need an useflag for doing this and not clash with sys-aut/pam_fprint
Created attachment 632376 [details, diff] FILES patch to disable build of tests
Hi, I finally got this to build, but I got the following message after the building fprint (apologies if I'm not following proper commenting formatting): // Post build message * Messages for package sys-auth/fprintd-1.90.1: * Package: sys-auth/fprintd-1.90.1 * Repository: localrepo * USE: abi_x86_64 amd64 elibc_glibc kernel_linux pam systemd userland_GNU * FEATURES: ccache network-sandbox preserve-libs sandbox userpriv usersandbox * Applying disable_tests.patch ... * Final size of build directory: 3056 KiB (2.9 MiB) * Final size of installed tree: 732 KiB * The ebuild is installing to one or more unexpected paths: * * /usr/" * * Please fix the ebuild to use correct FHS/Gentoo policy paths // Running fprintd-enroll I got the following error: // Running fprintd-enroll TARDIS1968 /var/tmp/portage # fprintd-enroll list_devices failed: Unit fprintd.service not found. // I found the systemd service file at /usr/\"/lib/systemd/system\"/fprintd.service I'm not sure how to write a patch, but may I suggest the following edit to the ebuild at line 45? // fprint-1.90.1-r1.ebuild @ line 45 --- $(use systemd && echo '-Dsystemd_system_unit_dir="'$systemddir'"' ) \ +++ $(use systemd && echo '-Dsystemd_system_unit_dir='$systemddir'' ) \ // That edit cleaned up the post build error, and placed the systemd service file is in the correct path at /usr/lib/systemd/system/fprintd.service. Sadly, my fingerprint reader still isn't recognized, but that is a different matter, which I suspect is related to libfprint and my ELAN fingerprint reader being too new. Thank you for this ebuild, as it finally allowed me to build fprintd.
Created attachment 643004 [details] new version of ebuild (from my github) fixed: wrong path expansion for systemd_unit_dir pam_fprintd needs systemd so change DEPENDS accordingly.
*** This bug has been marked as a duplicate of bug 700282 ***
