Package Details: howdy 2.3.1-1

Git Clone URL: https://aur.archlinux.org/howdy.git (read-only)
Package Base: howdy
Description: Windows Hello for Linux
Upstream URL: https://github.com/boltgolt/howdy
Keywords: hello howdy windows-hello
Licenses: MIT
Submitter: kelleymcches
Maintainer: kelleymcches (boltgolt)
Last Packager: kelleymcches
Votes: 2
Popularity: 0.059034
First Submitted: 2018-06-25 05:25
Last Updated: 2018-09-25 01:21

Latest Comments

donpicoro commented on 2018-12-02 17:26

Interesting... I did try removing those 3 lines

diff --git a/PKGBUILD b/PKGBUILD
index 1835294..e466245 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,10 +46,10 @@ prepare() {
        patch -p1 < ../pam-python-1.0.6-fedora.patch
        patch -p1 < ../pam-python-1.0.6-gcc8.patch

-       # Doing some fixes for pam-python so that it can compile
-       sudo pkgfile -u
-       sudo pkgfile /usr/include/sys/cdefs.h core/glibc
-       cd ..
+       ## Doing some fixes for pam-python so that it can compile
+       #sudo pkgfile -u
+       #sudo pkgfile /usr/include/sys/cdefs.h core/glibc
+       #cd ..
 }
 build() {
        # Building pam-python

and it compiles without a hitch. Care to try it?

kelleymcches commented on 2018-11-25 06:33

I had to use pkgfile to make the build succeed. This is my first PKGBUILD and if you know of a way to do it without sudo or just not do it, please let me know. The build WILL fail though if you remove that line, you can try it and see

donpicoro commented on 2018-11-21 10:36

Hi, I am confused.... What's the intention behind the line: [sudo] pkgfile /usr/include/sys/cdefs.h core/glibc?

1) I have a tight user to compile AUR package and it is not a sudoers one. is sudo really needed? I understand pkgfile -u but not this second line.

2) I really do not know what does the second part (core/glibc) do? The output is nothing!

3) Would it matter if I just remove that line? What is it's purpose? if the idea is to verify the presence of the /usr/include/sys/cdefs.h file... isn't it enough to demand glibc as a dependence? Isn't this one of those dependencies that are assumed to exist as it belongs to the base group?

JoaoMachado commented on 2018-11-21 03:53

command: pakku -Sy howdy

JoaoMachado commented on 2018-11-21 03:52

FIXED, I was using Pamac GUI to install the the Howdy package, so I tried pakku from the CLI and that worked. I did not try to use pamac from the CLI... FYI

JoaoMachado commented on 2018-11-21 03:35

Trying to build in Manjaro I get the following;

==> Starting prepare()... Cloning into 'dlib_clone'... patching file src/pam_python.c Hunk #1 succeeded at 39 (offset 7 lines). Hunk #2 succeeded at 1526 (offset 29 lines). patching file src/pam_python.c Hunk #1 succeeded at 2227 (offset 53 lines). patching file src/Makefile Hunk #1 succeeded at 1 with fuzz 1. sudo: no tty present and no askpass program specified ==> ERROR: A failure occurred in prepare(). Aborting...

boltgolt commented on 2018-10-11 07:12

This is a leftover from the debian build, where some distros like ubuntu 16.04 have broken python-dlib packages and which cause the installation to fail. I don't have an arch instance to test the installation, so feel free to propose changes.

Taijian commented on 2018-10-10 13:58

Is there a reason why you are silently installing dlib inside this PKGBUILD instead of using either dlib or python-dlib-cuda from the AUR as depends? That would IMHO be 'cleaner' and avoid issues with improper config flags for dlib, as those packages handle them on the fly based on cpu flags, instead of using defaults as you do here.

kelleymcches commented on 2018-06-27 11:03

As a temporary fix until I have the chance to fix it, you can remove the pip installation of click and pillow in the PKGBUILD. You can also uninstall those packages and reinstall them with the PKGBUILD as Howdy needs the versions listed in the PKGBUILD.

Edit: It shouldn't be an issue anymore with the newest PKGBUILD

huiser commented on 2018-06-27 07:50

Installation fails, conflict with packages python-pillow and python-click. Examples: howdy: /usr/lib/python3.6/site-packages/PIL/version.py exists in filesystem (owned by python-pillow) howdy: /usr/lib/python3.6/site-packages/click/init.py exists in filesystem (owned by python-click)