public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] e2fsprogs: Update to 1.47.0
Date: Sun, 17 Sep 2023 13:55:53 +0000	[thread overview]
Message-ID: <20230917135554.185972-1-jonatan.schlag@ipfire.org> (raw)

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

The test suite now works

Fixes: #13228

Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
---
 e2fsprogs/e2fsprogs.nm | 18 +++---------------
 1 file changed, 3 insertions(+), 15 deletions(-)

diff --git a/e2fsprogs/e2fsprogs.nm b/e2fsprogs/e2fsprogs.nm
index 5041e8bd0..c66beb2b9 100644
--- a/e2fsprogs/e2fsprogs.nm
+++ b/e2fsprogs/e2fsprogs.nm
@@ -4,8 +4,8 @@
 ###############################################################################
 
 name       = e2fsprogs
-version    = 1.46.5
-release    = 2
+version    = 1.47.0
+release    = 1
 
 groups     = System/Filesystems
 url        = https://e2fsprogs.sourceforge.net/
@@ -56,20 +56,8 @@ build
 		# Create empty mtab file if it does not exist.
 		[ -e /etc/mtab ] || touch /etc/mtab
 
-		# Disable failing test to fallocate sparse files and big files on a blockmap fs.
-		#
-		# test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
-		# test_filesys: 13/4096 files (7.7% non-contiguous), 12422/65536 blocks
-		# Exit status is 1
-		#
-		# But the test fails because the Inode 12 and 13 have differnet permissions.
-		# ( 0644 instead of 0666 ).
-		# -Inode: 12   Type: regular    Mode:  0666   Flags: 0x0
-		# +Inode: 12   Type: regular    Mode:  0644   Flags: 0x0
-		rm -rvf tests/d_fallocate_blkmap
-
 		# Run testsuite.
-		cd build && make check || :
+		cd build && make check
 	end
 
 	install
-- 
2.39.2


             reply	other threads:[~2023-09-17 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 13:55 Jonatan Schlag [this message]
2023-09-17 13:55 ` [PATCH 2/2] file: Update to 5.45 Jonatan Schlag

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=20230917135554.185972-1-jonatan.schlag@ipfire.org \
    --to=jonatan.schlag@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