From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: snapshots (archive files) are too big ... Why?
Date: Sun, 24 Jan 2016 17:55:00 -0000 [thread overview]
Message-ID: <20160124101251.GC13479@calimero.vinschen.de> (raw)
In-Reply-To: <878u3gxde8.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Jan 23 21:13, Achim Gratz wrote:
> Corinna Vinschen writes:
> > I found out why this happens, I just don't know why it only occurs since
> > 2015-07-20.
>
> Looks like this patch
>
> http://pkgs.fedoraproject.org/cgit/rpms/tar.git/commit/?id=132f2c79628ff5f11bb7d41c5c34f94228d63c54
>
> and the following two fixups would be a likely source of that change in
> behaviour and it was probably the following package update that threw
> the script off course.
Looks like you nailed it. It seems these patches have gone upstream in
the first place, there just hasn't been a new tar version released yet.
Eric, any chance you could include these patches in a new tar release as
well to catch up with Fedora (or nudge the tar maintainers to release
1.29)?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-24 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:35 Houder
2016-01-23 17:35 ` Andrey Repin
2016-01-23 18:10 ` Andrey Repin
2016-01-23 19:25 ` Houder
2016-01-23 20:13 ` Corinna Vinschen
2016-01-23 20:18 ` Houder
2016-01-23 21:56 ` Corinna Vinschen
2016-01-23 23:31 ` Houder
2016-01-24 10:12 ` Achim Gratz
2016-01-24 10:28 ` Houder
2016-01-24 1:22 ` Achim Gratz
2016-01-24 17:55 ` Corinna Vinschen [this message]
2016-01-24 18:36 ` 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=20160124101251.GC13479@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).