public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Broken file in ALL cygwin mirrors report! socat-debuginfo
Date: Sat, 20 Oct 2018 16:58:00 -0000	[thread overview]
Message-ID: <d70e3a43-72de-f898-83be-7d1cd1bc1990@gmail.com> (raw)
In-Reply-To: <4485ee8acd5ce4977bf370345f6f6718@smtp-cloud9.xs4all.net>

Am 20.10.2018 um 18:03 schrieb Houder:
> On Sat, 20 Oct 2018 16:59:16, Marco Atzeri wrote:
> [snip]
> ..
>
>> However setup requires an empty compressed tar file.
>> there are several empty tar of size "32" byte in the
>> repository
>>
>> for 64 bit
>>
>> $ grep ^install setup.ini | grep " 32 " | wc -l
>> 300
>
> tar file?
>
> ... uhm, just as an additional note to your post:
>
> 64-@@ grep ^install: setup.ini | grep " 108 " | wc -l
> 1065
> (real tar files (empty), compressed using xz)
>
> If the empty "tar file" is created like this:
>
> 64-@@ touch empty.tar (an empty file, but not a tarball!)
> 64-@@ xz empty.tar
>
> one will get files of size 32 bytes ...
>
> However:
>
> 64-@@ tar cJf empty.tar.xz --files-from=/dev/null
>        (or: tar cJfT empty.tar.bz2 /dev/null)
>
> one will get files of size 108 bytes (of real tar files).
>
> The latter ones will properly untar, but not the files of size 32.
>
> (yes, in both cases, no files will be produced)
>
> Regards,
> Henri
>

I know, it is the uncompress phase that complains on empty
file. tar and setup accept both versions

Regards
Marco




---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-10-20 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 16:31 hno
2018-10-19 16:45 ` Marco Atzeri
2018-10-20 14:03   ` Andrew Schulman
2018-10-20 14:59     ` Marco Atzeri
2018-10-20 16:03       ` Houder
2018-10-20 16:58         ` Marco Atzeri [this message]
2018-10-20 17:07         ` 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=d70e3a43-72de-f898-83be-7d1cd1bc1990@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).