public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] libpcap: Update to version 1.10.4
Date: Tue, 02 May 2023 19:53:16 +0200	[thread overview]
Message-ID: <20230502175321.3769644-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230502175321.3769644-1-adolf.belka@ipfire.org>

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

- Update from version 1.10.3 to 1.10.4
- Update of rootfile
- Changelog
	  Summary for 1.10.4 libpcap release
	    Source code:
	      Fix spaces before tabs in indentation.
	    rpcap:
	      Fix name of launchd service.
	    Documentation:
	      Document use of rpcapd with systemd, launchd, inetd, and xinetd.
	    Building and testing:
	      Require at least pkg-config 0.17.0, as we use --static.
	      Get rid of the remains of gnuc.h.
	      Require at least autoconf 2.69.
	      Update config.{guess,sub}, timestamps 2023-01-01,2023-01-21.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/rootfiles/common/libpcap | 3 +--
 lfs/libpcap                     | 4 ++--
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/config/rootfiles/common/libpcap b/config/rootfiles/common/libpcap
index 2371b4601..43c9140ea 100644
--- a/config/rootfiles/common/libpcap
+++ b/config/rootfiles/common/libpcap
@@ -2,7 +2,6 @@
 #usr/include/pcap
 #usr/include/pcap-bpf.h
 #usr/include/pcap-namedb.h
-#usr/include/pcap-util.h
 #usr/include/pcap.h
 #usr/include/pcap/bluetooth.h
 #usr/include/pcap/bpf.h
@@ -22,7 +21,7 @@
 #usr/lib/libpcap.a
 usr/lib/libpcap.so
 usr/lib/libpcap.so.1
-usr/lib/libpcap.so.1.10.3
+usr/lib/libpcap.so.1.10.4
 #usr/lib/pkgconfig/libpcap.pc
 #usr/share/man/man1/pcap-config.1
 #usr/share/man/man3/pcap.3pcap
diff --git a/lfs/libpcap b/lfs/libpcap
index 3f1de9b5a..0dfe562bf 100644
--- a/lfs/libpcap
+++ b/lfs/libpcap
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.10.3
+VER        = 1.10.4
 
 THISAPP    = libpcap-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -42,7 +42,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 3614042f7d8cd5a25221f52d2ed09f9f44643cdc0901ff21041ddb7ba85193c667036f7d989c8b59e6e205d630e062da46533110914dd287013a9ff80b31e97f
+$(DL_FILE)_BLAKE2 = 05a7eafc1e1817f7844008db89d8fb10cd2525c22f7ee6c9e3d582b14229412f38ccced5e9d80a96dd459ef9eab12eccb5c1dd4978ddc9f66267469212005e4c
 
 install : $(TARGET)
 
-- 
2.40.1


  parent reply	other threads:[~2023-05-02 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 17:53 [PATCH] harfbuzz: Update to version 7.2.0 Adolf Belka
2023-05-02 17:53 ` [PATCH] iproute2: Update to version 6.3.0 Adolf Belka
2023-05-02 17:53 ` Adolf Belka [this message]
2023-05-02 17:53 ` [PATCH] libxml2: Update to version 2.11.1 Adolf Belka
2023-05-02 17:53 ` [PATCH] lvm2: Update to version 2.03.21 Adolf Belka
2023-05-09  7:51   ` Arne Fitzenreiter
2023-05-09  8:01     ` Michael Tremer
2023-05-09  8:25       ` Adolf Belka
2023-05-09  9:13         ` Michael Tremer
2023-05-02 17:53 ` [PATCH] nfs: Update to version 2.6.3 Adolf Belka
2023-05-02 17:53 ` [PATCH] opus: Update to version 1.4 Adolf Belka
2023-05-02 17:53 ` [PATCH] zstd: Update to version 1.5.5 Adolf Belka

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=20230502175321.3769644-3-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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