From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] tar: Update to version 1.35-1
Date: Wed, 20 Sep 2023 19:01:15 +0200 [thread overview]
Message-ID: <20230920170116.67611-4-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230920170116.67611-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
- IPFire-3.x
- Update from version 1.34-1 to 1.35-1
- Changelog
1.35
This is mainly a bug-fixing release.
Noteworthy changes in this release:
* Fail when building GNU tar, if the platform supports 64-bit time_t
but the build uses only 32-bit time_t.
* Leave the devmajor and devminor fields empty (rather than zero) for
non-special files, as this is more compatible with traditional tar.
Bug fixes
** Fix interaction of --update with --wildcards.
** When extracting archives into an empty directory, do not create
hard links to files outside that directory.
** Handle partial reads from regular files.
** Warn "file changed as we read it" less often.
Formerly, tar warned if the file's size or ctime changed.
However, this generated a false positive if tar read a file
while another process hard-linked to it, changing its ctime.
Now, tar warns if the file's size, mtime, user ID, group ID,
or mode changes. Although neither heuristic is perfect,
the new one should work better in practice.
** Fix --ignore-failed-read to ignore file-changed read errors
as far as exit status is concerned. You can now suppress file-changed
issues entirely with --ignore-failed-read --warning=no-file-changed.
** Fix --remove-files to not remove a file that changed while we read it.
** Fix --atime-preserve=replace to not fail if there was no need to replace,
either because we did not read the file, or the atime did not change.
** Fix race when creating a parent directory while another process is
also doing so.
** Fix handling of prefix keywords not followed by "." in pax headers.
** Fix handling of out-of-range sparse entries in pax headers.
** Fix handling of --transform='s/s/@/2'.
** Fix treatment of options ending in / in files-from list.
** Fix crash on 'tar --checkpoint-action exec=\"'.
** Fix low-memory crash when reading incremental dumps.
** Fix --exclude-vcs-ignores memory allocation misuse.
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
tar/tar.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tar/tar.nm b/tar/tar.nm
index 5403df401..403e88145 100644
--- a/tar/tar.nm
+++ b/tar/tar.nm
@@ -4,7 +4,7 @@
###############################################################################
name = tar
-version = 1.34
+version = 1.35
release = 1
groups = System/Packaging
--
2.42.0
next prev parent reply other threads:[~2023-09-20 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 17:01 [PATCH] screen: Update to version 4.9.1 Adolf Belka
2023-09-20 17:01 ` [PATCH] smartmontools: Update to version 7.4-1 Adolf Belka
2023-09-20 17:01 ` [PATCH] squashfs-tools: Update to version 4.6.1-1 Adolf Belka
2023-09-20 17:01 ` Adolf Belka [this message]
2023-09-20 17:01 ` [PATCH] tcpdump: Update to version 4.99.4-1 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=20230920170116.67611-4-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