From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: inside /bin/tar: cannot change mode
Date: Thu, 25 May 2023 01:52:55 -0600 [thread overview]
Message-ID: <e7f8d797-3d76-be8c-c9ad-7c97b696e4af@Shaw.ca> (raw)
In-Reply-To: <A666F534-16CB-47FE-A6A9-A9DFDE47E642@Denis-Excoffier.org>
On 2023-05-24 12:18, Denis Excoffier via Cygwin wrote:
> I have an error (about symlinks it seems) that i have never met in years: Cannot change mode.
> Apart from this message (and return code != 0), the ’tar extract’ is ok.
> % uname -a
> CYGWIN_NT-10.0-17763 {edited} 3.5.0-0.295.g3bee68248fc8.x86_64 2023-05-01 17:58 UTC x86_64 Cygwin
> % cd /tmp; rm -rf mytest mytest.tar
> % mkdir mytest
> % ln -s b mytest/a
> % /bin/tar cf /tmp/mytest.tar mytest
> % /bin/tar tvf /tmp/mytest.tar
> drwxr-xr-x {edited}/{edited} 0 2023-05-24 13:12 mytest/
> lrwxrwxrwx {edited}/{edited} 0 2023-05-24 13:12 mytest/a -> b
> % rm -rf mytest
> % /bin/tar xf /tmp/mytest.tar
> /bin/tar: mytest/a: Cannot change mode to rwxr-xr-x: Not a directory
> /bin/tar: Exiting with failure status due to previous errors
> % echo $status
> 2
> %
> /tmp is under ntfs filesystem, all packages are up to date (e.g. /bin/tar --version is 1.34).
I recently got this during a package update build, when it decided to tar a
build directory, which contained only symlinks to files in the src directory,
which the tar did not include, which would have created many dangling symlinks.
I fixed the issue by adding -h, --dereference to give chf and tar real files.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-05-25 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:18 Denis Excoffier
2023-05-25 7:52 ` Brian Inglis [this message]
2023-05-26 4:52 ` Denis Excoffier
2023-05-26 6:27 ` Brian Inglis
2023-05-28 4:21 ` Brian Inglis
2023-05-29 8:13 ` Denis Excoffier
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=e7f8d797-3d76-be8c-c9ad-7c97b696e4af@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).