From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] nfs: Update to version 2.6.3
Date: Tue, 02 May 2023 19:53:19 +0200 [thread overview]
Message-ID: <20230502175321.3769644-6-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230502175321.3769644-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
- Update from version 2.6.2 to 2.6.3
- Update of rootfile
- Changelog is available in sourceforge at the following url
https://sourceforge.net/projects/nfs/files/nfs-utils/2.6.3/
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
config/rootfiles/packages/nfs | 3 +--
lfs/nfs | 6 +++---
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/config/rootfiles/packages/nfs b/config/rootfiles/packages/nfs
index ff53abec9..e4c3c5219 100644
--- a/config/rootfiles/packages/nfs
+++ b/config/rootfiles/packages/nfs
@@ -24,13 +24,12 @@ usr/lib/libnfsidmap/static.so
#usr/lib/libnfsidmap/umich_ldap.a
#usr/lib/libnfsidmap/umich_ldap.la
usr/lib/libnfsidmap/umich_ldap.so
-#usr/lib/modprobe.d
-#usr/lib/modprobe.d/50-nfs.conf
#usr/lib/pkgconfig/libnfsidmap.pc
#usr/lib/udev/rules.d/99-nfs.rules
#usr/libexec/nfsrahead
#usr/sbin/blkmapd
usr/sbin/exportfs
+usr/sbin/fsidd
usr/sbin/mountstats
usr/sbin/nfsconf
usr/sbin/nfsdcld
diff --git a/lfs/nfs b/lfs/nfs
index 877b9985e..4df6efa6f 100644
--- a/lfs/nfs
+++ b/lfs/nfs
@@ -26,7 +26,7 @@ include Config
SUMMARY = Support Utilities for Kernel nfsd
-VER = 2.6.2
+VER = 2.6.3
THISAPP = nfs-utils-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = nfs
-PAK_VER = 19
+PAK_VER = 20
DEPS = rpcbind
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = ac5aeec051f10e7cd9593d21ecd07eddc87fd6d98e5aaa0db5c6af5ec223c05d856a877469a340c68364bbb317ec2ee3cfe79b7f9ff444028c8f851838f59853
+$(DL_FILE)_BLAKE2 = 1aafa7d49006a62e862a592e30c4f9ba762d6c1973cacd7b89709706cc69617aae8d23000f78841f3a09bf81140222904976536114f3fb78f6230defb039ae9b
install : $(TARGET)
--
2.40.1
next prev 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 ` [PATCH] libpcap: Update to version 1.10.4 Adolf Belka
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 ` Adolf Belka [this message]
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-6-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