Package Details: libfprint-tod-git 1.94.7+tod1-1

Git Clone URL: https://aur.archlinux.org/libfprint-tod-git.git (read-only, click to copy)
Package Base: libfprint-tod-git
Description: Library for fingerprint readers - TOD version
Upstream URL: https://fprint.freedesktop.org/
Licenses: LGPL
Groups: fprint
Conflicts: libfprint
Provides: libfprint, libfprint-2-tod.so, libfprint-2.so, libfprint-tod
Submitter: vagaerg
Maintainer: nezu
Last Packager: nezu
Votes: 14
Popularity: 0.35
First Submitted: 2020-06-21 03:02 (UTC)
Last Updated: 2024-09-06 10:38 (UTC)

Dependencies (13)

Required by (8)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

nezu commented on 2024-09-13 11:32 (UTC)

versioned package: https://aur.archlinux.org/packages/libfprint-tod

Grothesk commented on 2024-09-09 19:20 (UTC)

I can make a separate package for releases if you want.

I'd love to see a released based package! :-)

nezu commented on 2024-09-09 14:05 (UTC)

But shouldn't it point to releases instead?

No, this is a VCS package. I can make a separate package for releases if you want.

Also, this package currently builds what functionally is v1.94.8 but git describe doesn't catch it because the v1.94.8+tod1 tag is not part of the tod branch for some reason. see here.

Grothesk commented on 2024-09-07 07:00 (UTC)

But shouldn't it point to releases instead?

https://gitlab.freedesktop.org/3v1n0/libfprint/-/releases/v1.94.8+tod1

nezu commented on 2024-09-06 23:31 (UTC)

@Grothesk this is a VCS package, it's not pinned to a particular version. The version listed here doesn't really matter as it's always gonna build against the latest git commit and determine the actual version durring the build. At the time of writing git describe returns 1.94.7+tod1.r46.g5d0de75 for the tod branch so that's what I used. (perhaps this branch hasn't been updated yet?)

Grothesk commented on 2024-09-06 22:45 (UTC)

@nezu libfprint-tod-git 1.94.7+tod1-1 is running fine. But why didn't you commit a 1.94.8-1 based version?

Just wondering... Thanks for taking care of libfprint-tod-git!

nezu commented on 2024-09-06 10:18 (UTC)

New maintainer here, fixed

elvisman113 commented on 2024-08-16 14:09 (UTC)

I can confirm that glib2-devel is a required make dependency (reported by @DvdGC). I got this error before installing glib2-devel manually:

libfprint/libfprint/meson.build:177:17: ERROR: Dependency 'glib-2.0' tool variable 'glib_mkenums' contains erroneous value: '/usr/bin/glib-mkenums'

This is a distributor issue -- please report it to your glib-2.0 provider.

DvdGC commented on 2024-07-24 09:48 (UTC)

There seems to be a missing dependency to glib2-devel as it checks for glib-mkenums at installation. This has been updated on extra/libfprint

DanySK commented on 2024-05-30 10:06 (UTC)

Is there maybe a missing build dependency?

+ exec meson setup --prefix /usr --libexecdir lib --sbindir bin --buildtype plain --auto-features enabled --wrap-mode nodownload -D b_pie=true -D python.bytecompile=1 libfprint build
Traceback (most recent call last):
  File "/usr/bin/meson", line 5, in <module>
    from mesonbuild.mesonmain import main
ModuleNotFoundError: No module named 'mesonbuild'

1 2 3 4 5 Next › Last »