Update to 1.16.0

f2fs-tools-1.8.0-bigendian.patch

@@ -1,11 +0,0 @@
-diff -up f2fs-tools-1.4.0/include/f2fs_fs.h.orig f2fs-tools-1.4.0/include/f2fs_fs.h
---- f2fs-tools-1.4.0/include/f2fs_fs.h.orig	2015-01-03 09:45:23.000000000 +0100
-+++ f2fs-tools-1.4.0/include/f2fs_fs.h	2015-01-03 09:45:20.000000000 +0100
-@@ -34,6 +34,7 @@ typedef unsigned long	pgoff_t;
- #define cpu_to_le32(x)	((__u32)(x))
- #define cpu_to_le64(x)	((__u64)(x))
- #elif __BYTE_ORDER == __BIG_ENDIAN
-+#include <byteswap.h>
- #define le16_to_cpu(x)	bswap_16(x)
- #define le32_to_cpu(x)	bswap_32(x)
- #define le64_to_cpu(x)	bswap_64(x)

f2fs-tools.spec

@@ -1,11 +1,10 @@
 Name:                f2fs-tools
-Version:             1.14.0
+Version:             1.16.0
 Release:             1
 Summary:             Tools for Flash-Friendly File System (F2FS)
 License:             GPLv2+
 URL:                 http://sourceforge.net/projects/f2fs-tools/
 Source0:             http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/snapshot/%{name}-%{version}.tar.gz
-Patch0:              f2fs-tools-1.8.0-bigendian.patch
 BuildRequires:       autoconf automake uuid-devel libuuid-devel libtool libselinux-devel libblkid-devel make
 
 %description
@@ -18,8 +17,7 @@ Requires:            %{name} = %{version}-%{release}
 f2fs is a file system desigend for flash devices
 
 %prep
-%setup -q
-%patch0 -p1 -b .bigendian
+%autosetup -p1
 sed -i 's/AC_PROG_LIBTOOL/LT_INIT/' configure.ac
 
 %build
@@ -45,9 +43,8 @@ find %{buildroot} -type f -name "*.la" -delete
 %{_sbindir}/resize.f2fs
 %{_sbindir}/sload.f2fs
 %{_sbindir}/f2fs_io
-%{_sbindir}/f2fstat
 %{_sbindir}/f2fscrypt
-%{_sbindir}/sg_write_buffer
+%{_sbindir}/f2fslabel
 %{_libdir}/*.so.*
 %{_mandir}/man8/*f2*.gz
 
@@ -56,6 +53,9 @@ find %{buildroot} -type f -name "*.la" -delete
 %{_libdir}/*.so
 
 %changelog
+* Fri Sep 15 2023 yaoxin <yao_xin001@hoperun.com> - 1.16.0-1
+- Update to 1.16.0
+
 * Thu Mar 04 2021 wangyue <wangyue92@huawei.com> - 1.14.0-1
 - Update to 1.14.0 to fix CVE-2020-6106 and CVE-2020-6104 and CVE-2020-6107 and CVE-2020-6108 and CVE-2020-6105