Github messages for voidlinux
 help / color / mirror / Atom feed
From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] arp-scan: update to 1.10.0
Date: Wed, 15 Mar 2023 14:35:15 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42785@inbox.vuxu.org> (raw)

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

There is a new pull request by filiprojek against master on the void-packages repository

https://github.com/filiprojek/void-packages arp-scan
https://github.com/void-linux/void-packages/pull/42785

arp-scan: update to 1.10.0
Tagging the maintainer @faulesocke 

#### 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)
- I built this PR locally for these architectures:
  - x86_64-musl



A patch file from https://github.com/void-linux/void-packages/pull/42785.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-arp-scan-42785.patch --]
[-- Type: text/x-diff, Size: 1056 bytes --]

From b796bbdeb05ca63aa21bf19c3edf0fa0ba692de5 Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Wed, 15 Mar 2023 14:16:23 +0100
Subject: [PATCH] arp-scan: update to 1.10.0

---
 srcpkgs/arp-scan/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/arp-scan/template b/srcpkgs/arp-scan/template
index 1e0ce64a074e..0396215304b7 100644
--- a/srcpkgs/arp-scan/template
+++ b/srcpkgs/arp-scan/template
@@ -1,6 +1,6 @@
 # Template file for 'arp-scan'
 pkgname=arp-scan
-version=1.9.7
+version=1.10.0
 revision=1
 build_style=gnu-configure
 hostmakedepends="automake"
@@ -10,7 +10,7 @@ maintainer="Urs Schulz <voidpkgs@ursschulz.de>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/royhills/arp-scan"
 distfiles="https://github.com/royhills/${pkgname}/archive/${version}/${pkgname}-${version}.tar.gz"
-checksum=e03c36e4933c655bd0e4a841272554a347cd0136faf42c4a6564059e0761c039
+checksum=204b13487158b8e46bf6dd207757a52621148fdd1d2467ebd104de17493bab25
 
 pre_configure() {
 	autoreconf --install

             reply	other threads:[~2023-03-15 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 13:35 filiprojek [this message]
2023-03-15 20:20 ` [PR REVIEW] " paper42
2023-03-15 20:20 ` paper42
2023-03-16 14:01 ` [PR PATCH] [Updated] " filiprojek
2023-03-16 14:43 ` [PR REVIEW] " paper42
2023-03-16 15:29 ` filiprojek
2023-03-16 15:34 ` paper42
2023-03-18  6:31 ` [PR PATCH] [Merged]: " paper42
  -- strict thread matches above, loose matches on Subject: below --
2023-02-16 10:40 [PR PATCH] " Eloitor

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42785@inbox.vuxu.org \
    --to=filiprojek@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).