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] lsof: Update to version 4.99.4
Date: Wed, 20 Nov 2024 22:49:03 +0100	[thread overview]
Message-ID: <20241120214909.2717383-1-adolf.belka@ipfire.org> (raw)

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

- Update from version 4.99.3 to 4.99.4
- Update of rootfile not required
- Changelog
    4.99.4
	fix version parser for clang (lsof-org#305) (#306)
	In lsof manapge: mention /etc/services for -P option (#309)
	[freebsd] don't use kf_sock_inpcb on modern versions. In
	  FreeBSD 14 and after the generic internet protocol control
	  block and protocol specific (TCP) control block are the same
	  pointer.  The latter embeds the former. The kf_sock_inpcb is
	  planned for removal in FreeBSD 15.
	[freebsd] Recognize FreeBSD 15
	Fix typos in docs (#314)
	[linux] Do not embed kernel version in CFLAGS (#314)
	[linux] Linux 6.9 changed the pidfs appearence in procfs. Try
	  to maintain original output in lsof (#317)
	[linux] closefrom_shim: Add optimized fallback for platforms
	  without closefrom or close_range (#316)
	lib/misc.c: fix build against -std=c23 (`void (*)()`) changed
	  the meaning) (#327)

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/lsof | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/lsof b/lfs/lsof
index 5dbce5022..b22d5e0fd 100644
--- a/lfs/lsof
+++ b/lfs/lsof
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2024  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 4.99.3
+VER        = 4.99.4
 
 THISAPP    = lsof-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 71049bd2c3b6788260d9970e8c6828128999b5040fb23cee0e288ee7e353e5e0510b8b1e5a5275158f1ff37f18066a36766a80b56d24ff57be1f3243910482e7
+$(DL_FILE)_BLAKE2 = 43e97874779797733433c0942f47dd5bebdaf5ef12153ede91b472c044d9ca63a03aee38c0d5a939b3c3bc7b40321dac5d241da39ca108f1ca3355c6571bc253
 
 install : $(TARGET)
 
-- 
2.47.0


             reply	other threads:[~2024-11-20 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 21:49 Adolf Belka [this message]
2024-11-20 21:49 ` [PATCH] man: Update to version 2.13.0 Adolf Belka
2024-11-20 21:49 ` [PATCH] memtest: Update to version 7.20 Adolf Belka
2024-11-20 21:49 ` [PATCH] meson: Update to version 1.6.0 Adolf Belka
2024-11-20 21:49 ` [PATCH] oath-toolkit: Update to version 2.6.12 Adolf Belka
2024-11-20 21:49 ` [PATCH] openldap: Update to version 2.6.8 Adolf Belka
2024-11-20 21:49 ` [PATCH] openssl: Update to version 3.4.0 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=20241120214909.2717383-1-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