Re: cpio - covscan issues

> On Thu, 08 Apr 2021 13:37:13 +0200, Kamil Dudka said: > > On Thursday, April 8, 2021 12:33:11 PM CEST Ondrej Dubaj wrote: > > On Thu, Apr 8, 2021 at 12:02 PM Kamil Dudka wrote: > > > On Thursday, April 8, 2021 9:47:05 AM CEST Ondrej Dubaj wrote: > > > > Hello, > > > > > > > > proposing pat

Re: Improvement of man pages of TAR

> On Mon, 14 Feb 2022 19:36:22 -0800, Paul Eggert said: > > On 2/13/22 08:11, Antonio Diaz Diaz wrote: > > Helge Kreutzmann wrote: > >> Man page: tar.1 > >> Issue:    archive --> archive itself > >> > >> "%s: file is the archive; not dumped" > > > > FWIW, as a non-native English reader but so

Re: Revisiting "file changed as we read it", with a proposed patch

> On Thu, 2 Jun 2022 17:06:32 -0700, Paul Eggert said: > > 1. If the mtime or size changes, doesn't this necessarily mean that > ctime changes? In other words, isn't tar's current test for size growing > redundant? This test was added in commit > c455373e5b7fc3037ad9e4204ba6c6aac2faa10f dat

Re: [GNU tar 1.28] testsuite: 5 6 7 8 9 12 15 20 33 40 41 42 47 57 60 63 64 65 66 68 71 73 75 76 85 87 89 90 94 failed

> On Sun, 09 Oct 2022 15:23:14 +0200, Christian Schoenebeck said: > > On Sonntag, 9. Oktober 2022 00:47:41 CEST Paul Eggert wrote: > > Looks like you're using a shell that invokes 'tar' and passes the > > fully-qualified file name as argv[0]. You might try using a shell that > > doesn't do tha

Re: tar is creating corrupt archives when soft links are present

> On Thu, 1 Dec 2022 16:14:42 -0500, Timothe Litt said: > > The hard link problem reproduces with this (note the two soft links turning > into a soft and a hard(!) - according to tar: > > # ( cd / && ls -li bin/awk bin/bash && tar -cf - bin/awk bin/bash | tar -tvf > - ) > 22683669 lrwxrwxrw

Possible bug in paxutils rmt_lseek__

Is there a bug in http://git.savannah.gnu.org/cgit/paxutils.git/commit/?id=d50ea31268250eea8166d62326deb4386cb65cf9 if off_t is 32-bit and intmax_t is 64-bit? It can be like that on 32-bit x86 Solaris 10. E.g. the code below prints L0 305419896 L0 1311768465173141112 ---

Re: Potential Null pointer dereference in tar 1.35

> On Thu, 21 Sep 2023 09:33:57 -0700, Paul Eggert said: > > Could you please look at the current sources? That part of 'tar' has > changed significantly since 1.35, and I don't see a bug in the latest > version. If the bug's still there, please let us know. The latest version looks correct

Re: prefer local files to network connections

> On Tue, 30 Jan 2024 19:09:45 +0100, Sergey Poznyakoff said: > > > I suggest that tar check if a file exists before trying to make a > > network connection. This would eliminate the need for --force-local in > > (I expect) most cases. As in: > > Nice idea. I'll implement it. Is there a pot

Re: tar hangs on dangling symlink when extracting with --wildcards

> On Mon, 27 May 2024 13:43:12 -0500, Tristan Miller said: > > Oh, looks like you're probably right about this. It's only the tar > packaged by openSUSE that has this problem; tar compiled from source > emits the error message you described and does not hang. I will report > this issue to

Re: [PATCH 2/2] Fix off-by-one error.

> On Mon, 04 Nov 2024 18:13:38 -0800, Collin Funk said: > > Patch 2 fixes an off-by-one error that can be seen with address > sanitizer. > diff --git a/src/common.h b/src/common.h > index df87478c..c5df79f6 100644 > --- a/src/common.h > +++ b/src/common.h > @@ -699,7 +699,7 @@ char *timetostr