From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libpcap: update to 1.10.3.
Date: Sat, 21 Jan 2023 22:34:18 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41785@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages libpcap-1.10.3
https://github.com/void-linux/void-packages/pull/41785
libpcap: update to 1.10.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Local build testing
SUMMARY
pkg:libpcap host:x86_64 target:x86_64 cross:n result:OK
pkg:libpcap host:x86_64-musl target:x86_64-musl cross:n result:OK
pkg:libpcap host:i686 target:i686 cross:n result:OK
pkg:libpcap host:x86_64 target:aarch64-musl cross:y result:OK
pkg:libpcap host:x86_64 target:aarch64 cross:y result:OK
pkg:libpcap host:x86_64 target:armv7l-musl cross:y result:OK
pkg:libpcap host:x86_64 target:armv7l cross:y result:OK
pkg:libpcap host:x86_64 target:armv6l-musl cross:y result:OK
pkg:libpcap host:x86_64 target:armv6l cross:y result:OK
A patch file from https://github.com/void-linux/void-packages/pull/41785.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libpcap-1.10.3-41785.patch --]
[-- Type: text/x-diff, Size: 1100 bytes --]
From 2134cee6b5cb12347265d59285d747858e34cda9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 21 Jan 2023 21:27:36 +0000
Subject: [PATCH] libpcap: update to 1.10.3.
---
srcpkgs/libpcap/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libpcap/template b/srcpkgs/libpcap/template
index a6e4843d7990..4cecc49fe559 100644
--- a/srcpkgs/libpcap/template
+++ b/srcpkgs/libpcap/template
@@ -1,6 +1,6 @@
# Template file for 'libpcap'
pkgname=libpcap
-version=1.10.1
+version=1.10.3
revision=1
build_style=gnu-configure
configure_args="--enable-ipv6 --with-libnl --with-pcap=linux
@@ -14,7 +14,7 @@ license="BSD-3-Clause"
homepage="https://www.tcpdump.org/"
changelog="https://www.tcpdump.org/libpcap-changes.txt"
distfiles="https://www.tcpdump.org/release/${pkgname}-${version}.tar.gz"
-checksum=ed285f4accaf05344f90975757b3dbfe772ba41d1c401c2648b7fa45b711bdd4
+checksum=2a8885c403516cf7b0933ed4b14d6caa30e02052489ebd414dc75ac52e7559e6
build_options="bluetooth dbus usb"
build_options_default="usb"
next reply other threads:[~2023-01-21 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 21:34 motorto [this message]
2023-01-22 12:12 ` [PR PATCH] [Merged]: " leahneukirchen
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-41785@inbox.vuxu.org \
--to=motorto@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).