Package Details: aircrack-ng-git 20190211.8562674a-1

Git Clone URL: (read-only)
Package Base: aircrack-ng-git
Description: WiFi security auditing tools suite
Upstream URL:
Keywords: aircrack aircrack-ng airgraph airgraph-ng airmon airmon-ng airodump airodump-ng
Licenses: GPL2
Conflicts: aircrack-ng, aircrack-ng-scripts
Provides: aircrack-ng, aircrack-ng-scripts
Replaces: aircrack-ng-scripts, aircrack-ng-svn
Submitter: Miegl
Maintainer: Miegl
Last Packager: Miegl
Votes: 121
Popularity: 0.001600
First Submitted: 2018-04-04 18:44
Last Updated: 2019-02-13 22:13

Required by (15)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

Miegl commented on 2019-02-13 22:14

ipha: sorry, latest PKGBUILD should work fine.

ipha commented on 2019-02-13 21:21

Latest update isn't happy about installing files to /usr/sbin

aircrack-ng-git: /usr/sbin exists in filesystem (owned by filesystem)

oberon2007 commented on 2018-09-20 07:06

Could you please add aircrack-ng-scripts to provides array? Thanks.

Miegl commented on 2018-05-20 21:26

codyps: make arguments work correctly for me, but I'm fine with ./configure arguments too. Thanks.

codyps commented on 2018-05-20 17:49

Here's a patch which fixes this by switching to use ./configure arguments.

It seems the make args weren't taking affect in all cases (probably some make rule I'm not familiar with).

codyps commented on 2018-05-20 17:33

Running aircrack-ng fails with

F: Failed to spawn binary: No such file or directory

Strace says:

execve("/usr/local/libexec/aircrack-ng/aircrack-ng--avx", ["/usr/local/libexec/aircrack-ng/a"...], 0x5637f48122c0 /* 1 var */) = -1 ENOENT (No such file or directory)

So it seems that /usr/local is being used somewhere in the build that it shouldn't be.

Miegl commented on 2018-04-22 19:47

vesath: Yeah you are right, thanks!

vesath commented on 2018-04-22 18:24

Miegl: Your pkgver() function is not monotonic. Currently the AUR version is 1.2.rc5.r13.gce4e9c3c-1 but I did a rebuild a few days ago and got 1.2.r28.g94fe3e02-1. However vercmp considers the latter older than the former.

My suggestion with git packages is to use the following pkgver() function, which ensures that it is increasing:

pkgver() {
    cd "${srcdir}/${_pkgname}"
    git log -1 --format='%cd.%h' --date=short | tr -d -

vesath commented on 2018-04-06 20:05

No worries, Miegl, you'll do just fine. And if myself or others have any suggestions for improving the package we'll just share them with you. Cheers.

Miegl commented on 2018-04-06 19:53

@vesath Thank you! I was kinda worried about dependencies being wrong, thanks for clearing that up for me.

As far as maintainership goes, I'm OK with you being the maintainer as I clearly don't have enough experience.