Package Details: pam_usb-git 0.8.2_r500.g7a785de-4

Git Clone URL: https://aur.archlinux.org/pam_usb-git.git (read-only, click to copy)
Package Base: pam_usb-git
Description: Hardware authentication for Linux using ordinary flash media (USB & Card based).
Upstream URL: https://github.com/mcdope/pam_usb
Licenses: GPL2
Conflicts: pam_usb
Provides: pam_usb
Submitter: IslandC0der
Maintainer: IslandC0der
Last Packager: IslandC0der
Votes: 0
Popularity: 0.000000
First Submitted: 2022-08-14 22:20 (UTC)
Last Updated: 2022-08-16 21:45 (UTC)

Latest Comments

IslandC0der commented on 2022-08-22 22:45 (UTC) (edited on 2022-08-22 22:45 (UTC) by IslandC0der)

See, that's the problem right there... What's /usr/local/bin/makepkg? Whatever it is, it can't be the real makepkg binary (as that gets installed to /usr/bin/makepkg).

On the github discussion I linked a couple comments back, someone was sharing a makepkg wrapper (which caused other people the same issue as yours), with instructions to save it to that same "/usr/local" path.

My best guess is you installed some AUR package that included that broken wrapper, and now it gets executed whenever you call makepkg; you can check this with pacman -Qo /usr/local/bin/makepkg.

In the meantime, please do try to run the "real" makepkg executable, just to confirm that there's no other issues.

HalJordan commented on 2022-08-19 12:16 (UTC)

Just of note, other PKGBUILDs work just fine.

hal_j@home ~/.cache/yay/pam_usb-git (git)-[master] % /usr/local/bin/makepkg
/home/hal_j/.cache/yay/pam_usb-git/PKGBUILD: line 8: CARCH: unbound variable

I do notice that others are using "${CARCH}" and not "($CARCH)".

IslandC0der commented on 2022-08-19 01:01 (UTC)

Now that is strange... What if you call it explicitly as /usr/bin/makepkg?

HalJordan commented on 2022-08-18 12:06 (UTC)

Whoops, wrong dir, but it's happening with both:

hal_j@home ~/.cache/yay/pam_usb-git (git)-[master] % makepkg
/home/hal_j/.cache/yay/pam_usb-git/PKGBUILD: line 8: CARCH: unbound variable

HalJordan commented on 2022-08-18 12:04 (UTC)

Same output:

hal_j@home ~/.cache/yay/pam_usb (git)-[master] % makepkg
/home/hal_j/.cache/yay/pam_usb/PKGBUILD: line 9: CARCH: unbound variable

IslandC0der commented on 2022-08-17 15:49 (UTC)

@HalJordan Hi, that sounds like an issue with your yay configuration, possibly something is sourcing the PKGBUILD without sourcing makepkg.conf (see https://github.com/Jguer/yay/issues/336#issuecomment-1101699818)

Can you confirm that the problem goes away when you run makepkg manually?

HalJordan commented on 2022-08-17 13:38 (UTC)

I'm getting this when I try to build it:

/home/hal_j/.cache/yay/pam_usb-git/PKGBUILD: line 8: CARCH: unbound variable

And yet, it is set in my makepkg.conf:

hal_j@home ~/ % grep CARCH /etc/makepkg.conf
CARCH="x86_64"

IslandC0der commented on 2022-08-16 19:26 (UTC)

@dissonant Hi, I submitted pam_usb-git to provide the latest commit, whereas pam_usb provides the latest stable release, even though both are based off of git (as opposed to having a pam_usb-bin package, which would distribute a pre-compiled version).

I also based this PKGBUILD off of mcdope's one, with a few tweaks and improvements. If you have any further changes you would like to make, please show me your PKGBUILD and I'd be happy to add you as a co-maintainer :)

dissonant commented on 2022-08-15 12:55 (UTC)

@IslandC0der I've made some updates to the pam_usb PKGBUILD to base it off of https://github.com/mcdope/pam_usb

If possible could you re-add me as a maintainer/co-maintainer for that package (I am the original maintainer) and I will make the update. Alternatively you could create a merge request for pam_usb-git and pam_usb as there are no binary builds and both are based off of git