Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: aircrack-ng: update to 1.7.
Date: Mon, 11 Jul 2022 09:53:30 +0200	[thread overview]
Message-ID: <20220711075330.6xjpfVPhNj3YHlsVZfCI2WLHY4HiRRcBASWo8O4ry90@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37956@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

There's a merged pull request on the void-packages repository

aircrack-ng: update to 1.7.
https://github.com/void-linux/void-packages/pull/37956

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (`x86_64`-`glibc`)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [x] x86_64-musl

#### Additional Notes
This patch rolls in all changes (AND supersedes!) as discussed in PR #34452. The extra scripts mentioned in that PR require non-cross builds (use of Python).

On an aside, there are some dependency issues with `libhwloc-devel` package that could be improved in the future. Namely, that `-devel` package requires extra packages for the `pkg-config` file to work. All of these extra dependencies are NOT included by the `-devel` package, nor the `libhwloc` package. It is only the main package `hwloc` that includes some, but still not all.

      parent reply	other threads:[~2022-07-11  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 22:53 [PR PATCH] " jbenden
2022-07-10  4:49 ` classabbyamp
2022-07-10 20:15 ` [PR PATCH] [Updated] " jbenden
2022-07-10 20:20 ` jbenden
2022-07-11  7:53 ` classabbyamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220711075330.6xjpfVPhNj3YHlsVZfCI2WLHY4HiRRcBASWo8O4ry90@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).