Re: mail headers not set (cf question re tar)

On 24/09/2022 02:37, jr wrote: On Thursday, 22 September 2022 at 16:30:05 UTC+1, Max Nikulin wrote: ... Debian mail list archive has a rare mhonarc configuration that adds reply to list action (usually only reply to sender is available) and these mailto: links contain proper In-Reply-To value

Re: question re tar

On Fri, 23 Sep 2022 19:18:35 -0400 The Wanderer wrote: > I think the question was about a way/place/method to manually add such > headers from within Gmail, so that they can be present even when > replying to a message from within the digest, so that replies can be > made correctly while

Re: question re tar

On 2022-09-23 at 16:24, Thomas Schmitt wrote: > Hi, > > jr wrote: > >> I [...] cannot find an obvious (any!) place where headers could be set [...] >> I [...] hope that someone can/will supply Gmail specific instructions > > The normal way to participate is to subscribe your mail address at >

Re: question re tar

Hi, jr wrote: > I [...] cannot find an obvious (any!) place where headers could be set [...] > I [...] hope that someone can/will supply Gmail specific instructions The normal way to participate is to subscribe your mail address at https://lists.debian.org/debian-user/ or by sending a mail to

mail headers not set (cf question re tar)

hi, a single reply re the mail headers issue. On Thursday, 22 September 2022 at 09:20:06 UTC+1, Thomas Schmitt wrote: > ... > Your mails lack headers like "In-Reply-To:" or "References:", ... On Thursday, 22 September 2022 at 09:30:05 UTC+1, Tixy wrote: > ... > For a lot (most?) of us, your

Re: question re tar

On 22/09/2022 14:00, jr wrote: On Wednesday, 21 September 2022 at 17:20:05 UTC+1, Markus Schönhaber wrote: Could you please stop using a mail client that starts a new thread with every message you send? Please use something instead that really creates a reply when you are replying to someone

Re: question re tar

On Thu, 22 Sep 2022 08:00:34 +0100 jr wrote: > ouch. I read the digest, That could be your problem. If you would subscribe as a regular user, rather than to the digests (or in addition to) and reply to those messages, you might solve the problem. -- Does anybody read signatures any more?

Re: question re tar

On Thu, 2022-09-22 at 08:00 +0100, jr wrote: [...] > > [a reply that isn't one] > > > > Could you please stop using a mail client that starts a new thread with > > every message you send? > > Please use something instead that really creates a reply when you are > > replying to someone (i. e.

Re: question re tar

Hi, jr wrote: > I see a single thread only. cannot see "a new thread [started] with > every message", sorry. Your mails lack headers like "In-Reply-To:" or "References:", which should tell the Message Id of the mail to which you answer resp. some or all IDs of the thread. (My "References:" only

Re: question re tar

On Wednesday, 21 September 2022 at 17:10:05 UTC+1, Greg Wooledge wrote: > On Wed, Sep 21, 2022 at 04:29:07PM +0100, jr wrote: > > $ locate /jr/ | > > > grep -v -e /.cache/ -e /tmp/ | > > > > that is (one way) how the "ACTUAL CONTENTS" are arrived at. > That listing almost certainly includes

Re: question re tar

On Wed, Sep 21, 2022 at 04:29:07PM +0100, jr wrote: On Wednesday, 21 September 2022 at 13:10:05 UTC+1, Greg Wooledge wrote: On Wed, Sep 21, 2022 at 12:31:58PM +0100, jr wrote: > ... > "What's in the file" > > file names, one per line. (and, before you ask, '\n' terminated lines) This is not

Re: question re tar

21.09.22, 17:29 +0200, jr wrote: [a reply that isn't one] Could you please stop using a mail client that starts a new thread with every message you send? Please use something instead that really creates a reply when you are replying to someone (i. e. something that sets the

Re: question re tar

On Wed, Sep 21, 2022 at 04:29:07PM +0100, jr wrote: > $ locate /jr/ | > > grep -v -e /.cache/ -e /tmp/ | > > sed -e 's#/home/jr/##' > > that is (one way) how the "ACTUAL CONTENTS" are arrived at. That listing almost certainly includes subdirectory names. Hence your issues. You're feeding

Re: question re tar

On Wednesday, 21 September 2022 at 13:10:05 UTC+1, Greg Wooledge wrote: > On Wed, Sep 21, 2022 at 12:31:58PM +0100, jr wrote: > > ... > > "What's in the file" > > > > file names, one per line. (and, before you ask, '\n' terminated lines) > This is not helpful. We want to see the ACTUAL CONTENTS so

Re: question re tar

On Wed, Sep 21, 2022 at 12:31:58PM +0100, jr wrote: > > > $ tar -cvWf $arcname $fnames > > > > > > where $fnames initially was a list in a variable (this is preparing a > > > shell script), then I switched to storing in those in a file and > > > $ tar -cvWf $arcname $(cat $fname_list_file) > >

Re: question re tar

hi, On Wednesday, 21 September 2022 at 01:40:05 UTC+1, Greg Wooledge wrote: > On Tue, Sep 20, 2022 at 10:19:50PM +0100, jr wrote: > > On Tuesday, 20 September 2022 at 12:30:05 UTC+1, Greg Wooledge wrote: > > > ... > > > With this new information, it occurs to me that perhaps the OP did > > >

Re: question re tar

On Tue, Sep 20, 2022 at 10:19:50PM +0100, jr wrote: > hi, > > On Tuesday, 20 September 2022 at 12:30:05 UTC+1, Greg Wooledge wrote: > > ... > > With this new information, it occurs to me that perhaps the OP did > > something like this: ... > > unicorn:/tmp/x$ find . | tar cv --files-from=- -f

Re: question re tar

hi, On Tuesday, 20 September 2022 at 12:30:05 UTC+1, Greg Wooledge wrote: > ... > With this new information, it occurs to me that perhaps the OP did > something like this: ... > unicorn:/tmp/x$ find . | tar cv --files-from=- -f ../foo.tar I prefer 'locate' to 'find'. an no guessing involved,

Re: question re tar

> It seems some files are present multiple times in your list. > > echo text >file.txt > tar cvWf test.tar file.txt file.txt > tar tvf test.tar Sorry, I deleted this message, and then had a thought a few minutes later, so I'm quoting text from the mailing list archive. With this new

Re: question re tar

Hi, Max Nikulin wrote: > It seems some files are present multiple times in your list. > tar cvWf test.tar file.txt file.txt Well if it is that easy to create the situation, i can test what happens on restoring the tarball: $ tar cvf test.tar x x x x $ rm x rm: remove regular file ‘x’?

Re: question re tar

On 19/09/2022 02:37, jr wrote: when I saw the links and started investigating, I tried cat for the names, ie $ tar -cvWf $arcname $(cat $fnames) adding one or two file names on the command line works as expected, supplying names from list and or file produces those links. It seems some

Re: question re tar

On Monday, 19 September 2022 at 10:10:05 UTC+1, Thomas Schmitt wrote: > ... > But you could create a small ext filesystem in a file, mount it and make > experiments with it. oh, that's an excellent suggestion. thanks. will do that in the coming days. > > the "machine" is a VM, pre-installed by

Re: question re tar

On Mon, Sep 19, 2022 at 08:24:08AM +0100, jr wrote: > _thank you_. another question, if you don't mind: what will happen > if I extract such an archive on a "normal" computer with ext3/4 > filesystems? (don't want to .. experiment with this) Since none of us can reproduce your archive, only you

Re: question re tar

Hi, i wrote: > > test/hardlinks/hardlink_x link to u/test/hardlinks/x This comes when i edit my experiment output to remove unnecessary local information. I forgot to remove that last "u/". jr wrote: > what will happen > if I extract such an archive on a "normal" computer with ext3/4 >

Re: question re tar

hi, On Sun, 18 Sept 2022 at 21:39, Thomas Schmitt wrote: > Will Mengarini wrote: > > Note that the file-type character "h" (the leftmost character in your > > second line of output) isn't documented ... > The 'h' probably comes from {...} > which converts tar file type LNKTYPE to 'h'. thanks.

Re: question re tar

Hi, Will Mengarini wrote: > Note that the file-type character "h" (the leftmost character in your > second line of output) isn't documented in > , The 'h' probably comes from

Re: question re tar

* jr [22-09/18=Su 12:59 +0100]: > When I create an archive with '-cvWf' I'm used to finding only the files > specified, but every time I use 'tar' on this Debian, there is a "link" for > each and every file. Why? eg: > -rw--- jr/jr 256 2022-06-1 22:10 .config/pulse/cookie > hrw---

Re: question re tar

hi, > What kind of file system are the files sitting on? btrfs. the system is the pre-installed (on Chromebooks) Debian VM. > What are the *exact* tar commands that you used, to create the archive, > and to get that partial listing that you gave? initially from a shell script, assembling a

Re: question re tar

On Sun, 18 Sep 2022 12:59:21 +0100 jr wrote: > I hope someone can help me to make 'tar' "behave" as expected. tia. > > when I create an archive with '-cvWf' I'm used to finding only the > files specified, but every time I use 'tar' on this Debian, there is > a "link" for each and every file.

Re: question re tar

On Sun, Sep 18, 2022 at 12:59:21PM +0100, jr wrote: > when I create an archive with '-cvWf' I'm used to finding only the files > specified, but every time I use 'tar' on this Debian, there is a "link" for > each and every file. why? eg: > -rw--- jr/jr 256 2022-06-1 22:10

question re tar

hi, I hope someone can help me to make 'tar' "behave" as expected. tia. when I create an archive with '-cvWf' I'm used to finding only the files specified, but every time I use 'tar' on this Debian, there is a "link" for each and every file. why? eg: -rw--- jr/jr 256 2022-06-1 22:10