Package Details: fprintd-vfs_proprietary 0.8.1-1

Git Clone URL: https://aur.archlinux.org/fprintd-vfs_proprietary.git (read-only)
Package Base: fprintd-vfs_proprietary
Description: D-Bus service to access fingerprint readers, modified for the vfs_proprietary plugin
Upstream URL: https://www.freedesktop.org/wiki/Software/fprint/fprintd
Licenses: GPL
Groups: fprint
Conflicts: fprintd
Submitter: xavery
Maintainer: xavery
Last Packager: xavery
Votes: 2
Popularity: 0.195312
First Submitted: 2019-01-27 16:41
Last Updated: 2019-01-27 16:41

Latest Comments

1 2 Next › Last »

mx333 commented on 2019-06-28 15:55

@xavery: I deleted the source packages "libfprint-vfs_proprietary-git" and "fprintd-vfs_proprietary" in /home/mx/.cache/pacaur and then installed them again and it worked!!! Thank you.

mx333 commented on 2019-06-26 17:29

@xavery: I have all dependencies. Only one is missing: "libfprint-vfs_propietary-git" because I cannot install it (see my comment there). The error still exists like this:

Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/.

libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. doc/Makefile.am:32: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd ==> Beginne pkgver()... ==> Quellen sind fertig. :: failed to verify integrity or prepare libfprint-vfs_proprietary-git package

xavery commented on 2019-06-26 16:36

@mx333 : The only thing that can fail in pkgver is running git. Do you have git installed? Please install all makedepends of this package before continuing.

mx333 commented on 2019-06-26 16:30

@xavery: or is it due to the missing "libfprint-vfs_proprietary-git"? - i have also there problems when installing.

mx333 commented on 2019-06-26 16:19

@xavery: ok, I installed it and the result is this below. There is still something missing:

Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/.

libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:10: installing './compile' configure.ac:10: installing './config.guess' configure.ac:10: installing './config.sub' configure.ac:2: installing './install-sh' configure.ac:2: installing './missing' doc/Makefile.am:32: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') pam/Makefile.am: installing './depcomp' ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd ==> Beginne pkgver()... ==> Quellen sind fertig. :: failed to verify integrity or prepare libfprint-vfs_proprietary-git package

xavery commented on 2019-06-26 16:12

@mx333 : Same deal, intltoolize is provided by the intltool package, which is a makedepend. Please make sure that intltool is installed.

mx333 commented on 2019-06-26 16:06

I use Manjaro (KDE) and get a similar problem:


==> Beginne prepare()... patching file data/fprintd.service.in ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd Copying file po/Makefile.in.in

Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/.

./autogen.sh: Zeile 12: intltoolize: Kommando nicht gefunden. ==> FEHLER: Ein Fehler geschah in prepare(). Breche ab... :: failed to verify integrity or prepare libfprint-vfs_proprietary-git package :: failed to verify integrity or prepare fprintd-vfs_proprietary package


xavery commented on 2019-06-09 15:40

@SysGhost : there have been no changes to the upstream fprintd package in the meantime, with last changes being made on 18 November 2018 (https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/fprintd), which is before this package was even created.

I cannot reproduce the error, which is due to gtkdocize missing on your system. This is weird, since the gtkdocize program is available in the gtk-doc package, which is listed as a make dependency and thus must be installed if you want to build this package.

Removing out-of-date flag.

SysGhost commented on 2019-06-07 10:25

PKGBUILD file need changes according to upstream changes.

Cloning into 'fprintd'... done. Switched to a new branch 'makepkg' ==> Starting prepare()... patching file data/fprintd.service.in ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd ~/.cache/pacaur/fprintd-vfs_proprietary/src/fprintd Copying file po/Makefile.in.in

Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/.

./autogen.sh: line 11: gtkdocize: command not found ==> ERROR: A failure occurred in prepare(). Aborting... :: failed to verify integrity or prepare fprintd-vfs_proprietary package

xavery commented on 2019-05-21 18:36

@cheeseypi : Sorry, can't reproduce. The errors look really weird, though - Arch doesn't have x86_64-linux-gnu subfolders in its /usr/lib. Something like that is done by Debian AFAIR, so perhaps the configure script somehow was led into thinking it's running on Debian? Or maybe a third-party package modified some pkg-config files which describe the build flags and library files used by ImageMagick? I really have no idea.