From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: tar 1.33 symlinks : Cannot change mode to...
Date: Sat, 30 Jan 2021 16:11:45 +0100 [thread overview]
Message-ID: <81d680ec-0d3f-805e-dc47-a7689651efb7@gmail.com> (raw)
In-Reply-To: <1af6716f-9c9f-0c73-c184-6a1af23960a6@yahoo.de>
On 30.01.2021 15:58, Michael Soegtrop via Cygwin wrote:
> Dear Cygwin Team,
>
> is there an update on this? Apparently tar is broken on Cygwin 32 since
> the latest update (it works fine on 64 bit Cygwin) and afaik there is no
> way to install specific package versions from the command line as would
> be possible via the Setup UI, so I can't easily roll back to the
> previous version of tar. IMHO this is a very severe issue - tar is
> ubiquitous.
>
> Best regards,
>
> Michael
have you tried the Cygwin snapshot as suggested in:
https://sourceware.org/pipermail/cygwin/2021-January/247418.html
Regards
Marco
next prev parent reply other threads:[~2021-01-30 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 19:57 Morgan King
2021-01-11 23:50 ` Ken Brown
2021-01-12 8:18 ` ASSI
2021-01-12 10:32 ` Marco Atzeri
2021-01-12 16:55 ` Ken Brown
2021-01-12 17:15 ` Corinna Vinschen
2021-01-12 17:49 ` Ken Brown
2021-01-12 18:16 ` Corinna Vinschen
2021-01-12 18:03 ` Achim Gratz
2021-01-30 14:58 ` Michael Soegtrop
2021-01-30 15:11 ` Marco Atzeri [this message]
2021-01-30 15:36 ` Michael Soegtrop
2021-01-30 16:57 ` Michael Soegtrop
2021-01-13 16:52 ` Ken Brown
2021-01-13 19:02 ` Corinna Vinschen
2021-01-13 21:07 ` Morgan King
2021-01-13 21:12 ` Ken Brown
2021-04-01 21:23 ` Vincent Rivière
-- strict thread matches above, loose matches on Subject: below --
2021-01-10 13:50 [ANNOUNCEMENT] Updated: tar-1.33-3 Achim Gratz
2021-01-11 15:27 ` tar 1.33 symlinks : Cannot change mode to Vincent Rivière
2021-01-11 17:54 ` Achim Gratz
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=81d680ec-0d3f-805e-dc47-a7689651efb7@gmail.com \
--to=marco.atzeri@gmail.com \
--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).